Public Access
fix(seo): legal.html canonical, host-case normalisation, BlogPosting x15, blog body domain typo
Four follow-up defects found beyond the 2026-10-27 SEO audit (no copy changes): 1. legal.html canonical was https://ODOO4projects.com/legal — uppercase host AND a path that 404s. Now https://odoo4projects.com/legal.html. The file's og:url keeps its path /legal but its host is lowercased (path fix awaiting a decision). 2. The no-"4" domain typo in reader-visible <pre><code> body text of blog/posts/{guide-migrate-enterprise,speed-run-deploy,my-first-post}.html: odooprojects.com -> odoo4projects.com. Domain string only, no other wording. 3. Lowercase host in every machine-read value: the robots.txt Sitemap line, the homepage + de/ + es/ Organization JSON-LD url / contactPoint.url / offers[].url, legal.html og:url, and the four absolute self-URL hrefs in blog posts, odoo/support.html and email/trial-confirmation.html. Display text untouched (support@ODOO4projects.com stays as written). 4. One BlogPosting per blog post (15), every value taken from the page itself: headline = its <h1>, datePublished = its visible post-meta date, url = its own canonical, author/publisher = the Organization the site already publishes, image = its og:image where one exists (omitted on the 10 posts that have none). Empire ">950.00", FAQPage on support.html, the blog-chrome change and the bootcamp date conflict are untouched — decisions pending with the user.
This commit is contained in:
1 parent
28f04e13fe
commit
3c602d97be
22 files changed
+378
-28
No files matched your search
@@ -75,6 +75,30 @@
|
||||
.post-footer a { color: var(--primary); text-decoration: none; }
|
||||
.post-footer a:hover { text-decoration: underline; }
|
||||
</style>
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "BlogPosting",
|
||||
"headline": "Track the OCA Modules You Actually Use — Without Refreshing GitHub Every Day",
|
||||
"datePublished": "2026-10-24",
|
||||
"url": "https://odoo4projects.com/blog/posts/track-the-oca-modules-you-actually-use.html",
|
||||
"image": "https://image.office.odoo4projects.com/img/oca_module_status.png",
|
||||
"author": {
|
||||
"@type": "Organization",
|
||||
"name": "ODOO4projects",
|
||||
"url": "https://odoo4projects.com/"
|
||||
},
|
||||
"publisher": {
|
||||
"@type": "Organization",
|
||||
"name": "ODOO4projects",
|
||||
"url": "https://odoo4projects.com/",
|
||||
"logo": {
|
||||
"@type": "ImageObject",
|
||||
"url": "https://odoo4projects.com/images/logo.png"
|
||||
}
|
||||
}
|
||||
}
|
||||
</script>
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
@@ -126,7 +150,7 @@
|
||||
|
||||
<p>The list is ours, but it does not have to stay that way. If there is an OCA module you check every single release — a localisation, an accounting edge case, a field service helper — tell us and we will add it to the tracker so it gets checked alongside the rest.</p>
|
||||
|
||||
<p>You can find the live table on <a href="https://ODOO4projects.com">ODOO4projects.com</a>, or leave your favourite OCA module in the comments and we will take it from there.</p>
|
||||
<p>You can find the live table on <a href="https://odoo4projects.com">ODOO4projects.com</a>, or leave your favourite OCA module in the comments and we will take it from there.</p>
|
||||
</div>
|
||||
</article>
|
||||
<div class="post-footer">
|
||||
|
||||
Reference in new issue
Block a user