4.9 KiB
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 (W1–W6, W8–W11)
Stop the bleeding. Remove signals that cause Google to distrust the domain.
- Kill sitemap 404s and redirect URLs (W1)
- Fix robots.txt structural errors (W2)
- Fix schema dead domain + wrong org entity (W3)
- Fix hreflang reciprocity (W4)
- Fix title/meta stuffing + og:locale (W5)
- Add static internal links; fix orphans (W6)
- Homepage factual rewrite + H1 word-spacing (W8)
- Fix known 404 pages (W9)
- Performance: inline CSS size + D3 CDN (W10)
- 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:
- Translate properly → keep with correct language, hreflang to ES
- Consolidate → noindex + 301 → ES canonical; remove from sitemap
- 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
- 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. - Language variants are NOT separate pages for the same audience — they serve different language queries and must differ in language, not just slug.
- Year modifiers are OK if content is genuinely updated (
2025→2026with new data). - 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