This commit is contained in:
oliver
2026-08-28 10:11:11 -03:00
parent f533ff8e36
commit 585951c8ce
1380 changed files with 1540268 additions and 0 deletions
+124
View File
@@ -0,0 +1,124 @@
# Content Cluster Plans — Odoo Expertos
> Pillar-spoke architecture for three topic clusters. Agents use this to build internal links and understand page hierarchy.
---
## Overview
| Cluster | Hub URL | Articles (ES) | Status |
|---|---|---|---:|
| Odoo Hosting | `/odoo-hosting/` | ~99 ES pages | Hub 200 ✓ |
| Odoo General | `/odoo/` | ~41 ES pages | Hub 200 ✓ |
| Odoo IA | `/odoo-ia/` | ~56 ES pages | Hub 200 ✓ |
Each cluster has 6 language versions. Hub pages for EN/FR/PT `/odoo-hosting/` currently **404** → rebuild required (W1).
---
## Cluster 1 — Odoo Hosting (`/odoo-hosting/`)
**Hub intent:** Informational → commercial investigation. Buyer researching Odoo hosting options.
**Pillar page keywords:** "hosting odoo", "mejor hosting odoo 2026", "odoo hosting comparativa"
### Tier 1 — High-value spokes (prioritize in content expansion)
These are AI-Opportunity pages from the audit with citability score ≥5:
| URL | Target keyword | Priority |
|---|---|---|
| `/odoo-hosting/odoo4projects-hosting-review-2026/` | "odoo4projects review 2026" | P1 |
| `/odoo-hosting/mejor-hosting-odoo-2026/` | "mejor hosting odoo 2026" | P1 |
| `/odoo-hosting/mejores-proveedores-hosting-odoo-2026/` | "mejores proveedores odoo" | P1 |
| `/odoo-hosting/comparativa-precios-odoo-2026/` | "comparativa precios odoo 2026" | P1 |
| `/odoo-hosting/cloudpepper-vs-odoo-sh-2026/` | "cloudpepper vs odoo.sh" | P1 |
| `/odoo-hosting/opiniones-hosting-odoo-2026/` | "opiniones hosting odoo" | P2 |
| `/odoo-hosting/odoo-vs-sap-hosting-2026/` | "odoo vs sap hosting" | P2 |
| `/odoo-hosting/alternativas-odoo-sh-2026/` | "alternativas odoo.sh" | P2 |
| `/odoo-hosting/odoo-community-vs-enterprise-hosting-2026/` | "odoo community vs enterprise" | P2 |
### Tier 2 — Thin-content rewrites (crawled-not-indexed)
| URL | Min words | Query intent |
|---|---|---|
| `/odoo-hosting/hosting-odoo-gratis-gratuito-2025/` | 1,600 | Free trial / top-of-funnel |
| `/odoo-hosting/servidor-dedicado-odoo-2026/` | 1,600 | Technical decision maker |
| `/odoo-hosting/managed-odoo-hosting-2026/` | 1,600 | Commercial investigation |
| `/odoo-hosting/odoo-docker-hosting-2026/` | 1,800 | DevOps / technical |
| `/odoo-hosting/hosting-odoo-mexico-2026/` | 1,600 | Geo-local (MX) |
| `/odoo-hosting/migracion-hosting-odoo-2026/` | 1,800 | Commercial investigation |
| `/odoo-hosting/vps-odoo-hosting-2026/` | 1,800 | Technical decision maker |
| `/odoo-hosting/odoo-vs-zoho-books-hosting-2025/` | 1,800 | Comparison (rewrite from fabricated) |
| `/odoo-hosting/odoo-gratis-vs-pago-diferencias-2025/` | 1,600 | Top-of-funnel |
| `/odoo-hosting/odoo-enterprise-hosting-2026/` | 1,800 | Commercial investigation (high value) |
### Internal linking requirements
- Hub `/odoo-hosting/` links to all Tier 1 + Tier 2 articles (paginated if needed)
- Each spoke links back to hub + ≥3 related spokes within the cluster
- All EN/DE/FR/PT/AR variants link to the ES canonical via hreflang, not cross-links
---
## Cluster 2 — Odoo General (`/odoo/`)
**Hub intent:** Informational. Researchers and evaluators exploring Odoo capabilities.
**Pillar page keywords:** "odoo erp", "odoo implementación", "odoo módulos"
### Tier 1 — Thin-content priority rewrites
| URL | Min words | Query |
|---|---|---|
| `/odoo/odoo-hosting-cloud-infraestructura-2025/` | 1,800 | "infraestructura odoo cloud" |
| `/odoo/odoo-compras-gestion-proveedores-2025/` | 1,800 | "odoo gestión de compras" |
| `/odoo/odoo-argentina-implementacion-local-2025/` | 1,600 | "odoo argentina implementación" |
### Spoke categories (hub must link to all)
- Odoo versions (17, 18) — `/odoo/odoo-17-*/`, `/odoo/odoo-18-*/`
- Modules by function (CRM, inventory, accounting, purchasing, HR, manufacturing)
- Geo implementations (Argentina, Mexico, Colombia, Spain, LATAM)
- Career/certification pages — `/odoo/odoo-*/` career articles
---
## Cluster 3 — Odoo IA (`/odoo-ia/`)
**Hub intent:** Informational → commercial. AI-curious buyers evaluating Odoo's AI capabilities.
**Pillar page keywords:** "odoo ia", "odoo inteligencia artificial", "odoo automatización"
### Tier 1 — AI-Opportunity pages
| URL | Fix needed | Query |
|---|---|---|
| `/odoo-ia/alternativas-odoo-ia-comparativas-2025/` | Remove fabricated loss narrative, add table, cite sources | "alternativas odoo ia" |
| `/odoo-ia/que-es-odoo-ia-guia-basica-2025/` | Expand from shallow intro to structured 1,800-word explainer | "qué es odoo ia" |
### Spoke categories
- AI features by module (chatbot, OCR, predictive reordering)
- Automation (RPA, n8n integration)
- AI hosting requirements
- Comparisons (Odoo IA vs alternatives)
---
## Cross-cluster internal link matrix
Every article that discusses hosting topics should link to the most relevant `/odoo-hosting/` spoke, and vice versa.
| From cluster | To cluster | Example link |
|---|---|---|
| Odoo General | Odoo Hosting | `/odoo/odoo-18-novedades/` → links to `/odoo-hosting/odoo-enterprise-hosting-2026/` |
| Odoo IA | Odoo Hosting | `/odoo-ia/odoo-ia-chatbot/` → links to `/odoo-hosting/managed-odoo-hosting-2026/` |
| Odoo Hosting | Odoo General | `/odoo-hosting/mejor-hosting-odoo-2026/` → links to `/odoo/odoo-18-novedades/` |
---
## Hub page template (for EN/FR/PT rebuilds — W1)
Missing hub pages `/en/odoo-hosting/`, `/fr/odoo-hosting/`, `/pt/odoo-hosting/` must mirror `/de/odoo-hosting/` (which returns 200). Minimum:
- H1 in target language
- 800+ words of genuine content (not Spanish)
- Full 7-entry hreflang block (es/en/de/fr/pt/ar/x-default)
- Links to all translated spoke articles within that language
- CollectionPage schema with translated strings + `inLanguage`
+121
View File
@@ -0,0 +1,121 @@
# Content Strategy — Odoo Expertos
**Date:** 2026-05-28
**Context:** Post-audit SEO restoration strategy. Site has ~72% of 1,210 pages excluded from Google's index. This strategy prioritizes fixing root causes over adding new pages.
---
## Strategic Priority Order
> Fix existing pages before creating new ones. Every new page on a low-trust domain is another crawl budget gamble.
### Phase 1 — Technical foundation (W1W6, W8W11)
Stop the bleeding. Remove signals that cause Google to distrust the domain.
1. Kill sitemap 404s and redirect URLs (W1)
2. Fix robots.txt structural errors (W2)
3. Fix schema dead domain + wrong org entity (W3)
4. Fix hreflang reciprocity (W4)
5. Fix title/meta stuffing + og:locale (W5)
6. Add static internal links; fix orphans (W6)
7. Homepage factual rewrite + H1 word-spacing (W8)
8. Fix known 404 pages (W9)
9. Performance: inline CSS size + D3 CDN (W10)
10. Security headers (W11)
### Phase 2 — Content consolidation (W7)
Remove or properly translate 400+ pages currently serving wrong-language content. This single workstream unblocks ~72% of the unindexed pages.
Decision tree per page:
1. **Translate properly** → keep with correct language, hreflang to ES
2. **Consolidate** → noindex + 301 → ES canonical; remove from sitemap
3. **Drop** → 301 → hub page; remove from sitemap
Default: ES canonical stays. Language variants only if genuinely translated.
### Phase 3 — Content deepening (post-W7)
Expand thin articles using the cluster plans in `cluster-plans.md`. Priority: Tier 1 AI-opportunity pages (citability score ≥5) before Tier 2 thin-content rewrites.
### Phase 4 — New content (only after Phase 1-3)
Net-new pages only when:
- The cluster has all Tier 1 spokes at ≥1,500 words with sources
- The hub is properly linking all spokes
- The language version being added is genuinely translated
---
## Content Quality Gates
Every published page must pass all gates before a sitemap entry is created:
| Gate | Threshold |
|---|---|
| Word count | ≥1,500 for articles; ≥800 for hub pages |
| Title length | ≤60 chars |
| Meta description | Unique corpus-wide; 140-160 chars |
| Language match | Content language = declared `lang` attribute |
| Author | "Equipo Odoo Expertos" or verified persona (no fabricated individuals) |
| Sourced claims | Every percentage/review-count claim has a source link |
| Internal links | ≥3 related articles + 1 parent hub |
| Schema | Article: headline + author + datePublished + dateModified + image |
| Hreflang | Full 7-entry block (where language variants exist) |
---
## Keyword Strategy by Language
### Spanish (primary)
**Intent distribution:** 60% informational, 30% commercial investigation, 10% navigational
- Primary terms: "hosting odoo", "implementación odoo", "odoo erp latam"
- Geo modifiers: Argentina, México, Colombia, España, Chile
- Version modifiers: "odoo 17", "odoo 18", "odoo 16"
### English
**Intent:** Technical + commercial investigation (EU/US buyers)
- Primary: "odoo hosting", "odoo implementation", "odoo erp consulting"
- Fix localized slugs: `/en/odoo-ai/` (not `/en/odoo-ia/`)
### German
**Intent:** B2B evaluation, DACH market
- Primary: "odoo hosting", "odoo implementierung", "odoo beratung"
- Fix: slugs like `/de/odoo-ki/` for AI content
### French
**Intent:** SMB decision-maker, Francophone Africa + France
- Primary: "hébergement odoo", "implémentation odoo"
- Build: hub pages `/fr/odoo-hosting/` (currently 404)
### Portuguese
**Intent:** Brazil + Portugal SMB
- Primary: "hospedagem odoo", "implementação odoo"
- Build: hub pages `/pt/odoo-hosting/` (currently 404)
### Arabic
**Intent:** MENA large enterprises
- Primary: "استضافة أودو", "تطبيق أودو"
- RTL implementation is correct — focus on content quality
---
## Anti-cannibalization Rules
1. **One canonical per topic.** Never create `/odoo-hosting/mejor-hosting-odoo-2025/` AND `/odoo-hosting/mejor-hosting-odoo-2026/` for the same target keyword without 301ing the old one.
2. **Language variants are NOT separate pages** for the same audience — they serve different language queries and must differ in language, not just slug.
3. **Year modifiers are OK** if content is genuinely updated (`2025``2026` with new data).
4. **Thin variants** (PT/FR with Spanish content) should 301 to ES, not stay live as separate pages.
---
## Measurement Plan
**Week 0 (baseline):** Current GSC export (done 2026-05-21).
**Week 2 post-deploy:** Submit sitemaps in GSC; "Validate Fix" on each coverage issue.
**Week 4-6 post-deploy:** Re-export GSC coverage. Target: <15% excluded.
**Month 3:** Organic traffic comparison (GSC Search Analytics).
**Leading indicators (on-site, immediate):**
- REVIEW.ps1 all-green
- Lighthouse mobile: LCP ≤2.5s / INP ≤200ms / CLS ≤0.1
- 0 pages with title >60 chars
- 0 corpus-wide duplicate meta descriptions
- Homepage screenshot: factual H1, no combat hype