feat(seo): wire internal links between the 17 blog posts and the pages that sell

The blog was an island: zero post→page links to hosting/upgrade/support/courses,
and only one page→post link in the whole site. Posts ranked for nothing while the
old blog host ranked for our long-tail queries.

Posts → pages (26 new in-body contextual links across 17 posts):
each post now carries one or two links to the page that answers its reader's next
question — odoo-hosting-2027, odoo-community-upgrade, support, the workshops hub,
the n8n masterclass, and the plan pricing on index.html#pricing.

Pages → posts (7 pages, one contextual link each):
index.html (OCA section), odoo-hosting-2027, odoo-community-upgrade, support,
workshops/, odoo-n8n-masterclass/, odoo-erp-automation-bootcamp/ now link into the
post that fits their own subject. The clearest miss is fixed — the
community-vs-enterprise-cost post and the odoo-community-upgrade page now link
to each other.

Anchors wrap existing sentences where the text already said the thing; four short
linking sentences were added (index OCA section, support first-steps FAQ, masterclass
lessons, bootcamp included section). No new components, no related-posts widget,
in-body anchors only. English pages only; DE/ES untouched (translator follow-up).
This commit is contained in:
oliver committed 2026-10-29 15:15:00 +00:00
1 parent bfa7f595cc
commit e37acde30c
24 files changed
+40 -31

No files matched your search

+1
View File
@@ -645,6 +645,7 @@
<p>Where Odoo's own automation stops, and the website-side workarounds that get you further without writing a custom module.</p>
</li>
</ol>
<p class="bc-lead">For a worked example end to end, our post on <a href="/blog/posts/odoo-19-to-20-invoice-migration-with-n8n-and-mcp.html">migrating invoices between Odoo versions</a> shows the same idea with an n8n workflow and an MCP tool.</p>
</div>
</section>