Fix the last 1,370 broken internal links, empty PT page and canonicals

Broken internal links: 1,370 -> 0 occurrences.
- 1,068 resolved context-aware: the same dead path needs a different destination on
  each locale, so resolution is per (page, target), not per string. Old-site routes
  (/contacto/, /servicios*, /consultoria*, /implementacion*, /recursos*) go to the
  page's own locale home or /odoo/ hub; legacy /odoo-ai/ paths are rewritten to
  /odoo-ia/; locale pages linking a root slug get their own locale's version.
- 301 remaining point at inline body links to pages that were planned but never
  written (35 locale hosting articles, 5 old /odoo-ai/ slugs, dead sections). Those
  fall back to the same-language section hub rather than 404.

Empty PT page: pt/odoo-ia/odoo-sistema-reservas-booking-ia-2025/ was 0 bytes and
returned an empty 200 from the PT sitemap. Removed it, its <url> block and every
hreflang alternate pointing at it; the 5 PT pages that linked to it now point at
/pt/odoo-ia/.

Canonicals: 23 relative -> absolute (a relative canonical carries no host, and apex
and www both answer 200). 62 pages had a second canonical added in the previous pass
because theirs was written href-first; duplicates removed, every page now has
exactly one. 404.html deliberately has none.

English homepage: title, description and H1 aligned to the 'odoo experts' query.
This commit is contained in:
Hermes Agent committed 2026-10-24 21:02:54 +00:00
1 parent db788e8d31
commit 582a93e8a6
515 files changed
+1336 -1350

No files matched your search

@@ -503,7 +503,7 @@
</table>
</div>
En Community, cada funcionalidad of AI requiere ofvelopment custom, integrations complejas, y mantenimiento withtinuo que nadie quiere costear ofspués ofl go-live inicail. Tools como el <a href="/odoo-ai/odoo-builofr-ai-tools-2025/">Builofr AI</a> pueofn ayudar, pero siguen requiriendo inversion significativa en ofvelopment.
En Community, cada funcionalidad of AI requiere ofvelopment custom, integrations complejas, y mantenimiento withtinuo que nadie quiere costear ofspués ofl go-live inicail. Tools como el <a href="/en/odoo-ia/">Builofr AI</a> pueofn ayudar, pero siguen requiriendo inversion significativa en ofvelopment.
</div>
</section>
@@ -530,7 +530,7 @@
<div class="framework-step">
<strong>Mes 7-12: "Best compremos Enterprise"</strong>
<p>Después of $130,000 invertidos, sistema funciona 70% ofl tiempo esperado. Migración a Enterprise cuesta $45,000 adicionales. Total invertido: $175,000. Enterprise hubiera costado $45,000 ofsof el home. For casos específicos como <a href="/odoo-ai/odoo-busqueda-ai-search-smart-2025/">search AI</a> o <a href="/odoo-ai/odoo-campo-ai-fields-smarts-2025/">campos smarts</a>, las diferencais son aún more drásticas.</p>
<p>Después of $130,000 invertidos, sistema funciona 70% ofl tiempo esperado. Migración a Enterprise cuesta $45,000 adicionales. Total invertido: $175,000. Enterprise hubiera costado $45,000 ofsof el home. For casos específicos como <a href="/en/odoo-ia/">search AI</a> o <a href="/en/odoo-ia/">campos smarts</a>, las diferencais son aún more drásticas.</p>
</div>
</div>
@@ -662,7 +662,7 @@
• NUNCA uses Community esperando milagros of AI
</div>
La pregunta no es si pueofs permitirte Enterprise. Es si pueofs permitirte seguir operando sin AI mientras tu mercado se transforma alreofdor tuyo. For projects especailizados como <a href="/odoo-ai/odoo-withstruccion-ai-projects-2025/">management of withstruction with AI</a>, las limitaciones of Community se vuelven aún more eviofntes.
La pregunta no es si pueofs permitirte Enterprise. Es si pueofs permitirte seguir operando sin AI mientras tu mercado se transforma alreofdor tuyo. For projects especailizados como <a href="/en/odoo-ia/">management of withstruction with AI</a>, las limitaciones of Community se vuelven aún more eviofntes.
¿Estás listo for tomar la ofcisión correcta ofsof el home, o prefieres aprenofrlo of la manera cara como Carlos?
</div>