# Ratgeber Content Improvement Plan 2026 **Last Updated:** 2026-03-16 **Purpose:** Elevate ratgeber content to lexikon-level quality with data-driven, SEO/AEO/GEO best practices while remaining user-centric and Ordio-promoting. --- ## Executive Summary Ratgeber posts currently underperform vs lexikon in depth, structure, formatting, and data-driven rigor. This plan aligns ratgeber creation with lexikon standards and adds ratgeber-specific enhancements (comparison tables, pros/cons, software criteria). --- ## Gap Analysis: Ratgeber vs Lexikon | Dimension | Lexikon (Target) | Ratgeber (Current) | Gap | |-----------|------------------|--------------------|-----| | **Word count** | 1,900–2,500+ (100% competitive-depth) | 1,200–1,500 (often minimum) | Ratgeber aims for minimum; lexikon aims for suggested | | **H2 count** | 8–12+ | 8–9 | Parity | | **H3 usage** | Planned per section; 2+ sentences each | Often skipped or minimal | Ratgeber underuses H3s for target groups, criteria | | **Section briefs** | Target words per H2; key points; formats | Present but less detailed | Less rigor in section planning | | **Answer capsules** | 120–150 chars after question H2s (AEO/GEO) | Missing | No answer-first for featured snippets | | **Format patterns** | formula-block, blog-note--important | Rarely used | Ratgeber can use callouts for pricing, legal | | **Unique value** | Explicit in outline; validated | Mentioned but not enforced | Need stronger unique-value gate | | **PAA coverage** | Matrix in outline; 100% covered | Matrix present; sometimes gaps | Enforce 100% PAA coverage | | **E-E-A-T** | Examples, case studies, sources | Thin | Add real scenarios, data points | | **Internal links** | 10–15; pillar 3–5; tools 3–5 | 10–15; tools 1–2 | Ratgeber under-links to tools | | **FAQs** | 10–15; 40–80 words; Ordio in tool FAQs | 10–15; quality varies | Enforce Ordio in recommendation FAQs | --- ## Improvement Pillars ### 1. Data-Driven Approach - **Competitive depth:** Set outline target to **100%** of competitive-depth recommended (not 80% minimum). Use `validate-content-outline-quality.php --target-ratio=1.0`. - **PAA coverage:** Create `paa-questions-manual.json` when SISTRIX returns no/off-topic PAA. Run `collect-faq-research-data.php` after manual PAA. Document PAA→H2/FAQ mapping in outline. - **Competitor gaps:** Run `compare-content-to-competitors.php` **before finalizing**; address every gap. Do not publish with unresolved gaps. - **GSC integration:** When available, use GSC queries to inform H2/FAQ selection. Document in SERP_ANALYSIS.md. ### 2. SEO/AEO/GEO Best Practices - **Answer capsules:** For **question-style H2s** (e.g. "Was kostet Dienstplan-Software?", "Welche Dienstplan-Software für die Pflege?"), add a 120–150 character answer capsule immediately after the heading. Direct, scannable summary before expanding. Do **not** use answer-style leads under declarative H2s. - **Definition in first 20%:** Core definition (Was ist…?) within first 20% of content. - **Featured snippet formats:** Use tables for comparisons; `
    ` for steps; paragraph for definitions (40–60 words). - **Entity clarity:** Clear mentions of software names, legal terms (ArbZG, DSGVO), target groups. ### 3. Content Expansion & Depth - **Target:** Aim for **100% of competitive-depth** recommended. For main topics (e.g. "Dienstplan Software Vergleich"), consider 1,800–2,500 words if competitors exceed 1,500. - **H3 planning:** For target-group sections (Gastronomie, Pflege, Kleinbetriebe, Einzelhandel), use **H3 per group** when each has 2+ sentences. Improves TOC, scannability, PAA targeting. - **No thin sections:** Each H2 needs 2+ paragraphs or 1 paragraph + list/table. Run `validate-section-depth.php`; do not stop until PASS. - **Pros/cons where applicable:** For comparison posts, add pros/cons list or table for top 3–4 tools when it adds value. ### 4. Formatting & Styling - **Tables:** Use `table-breakout-wrapper`; plain `table`/`thead`/`th`/`td`; **no Tailwind** on table elements. Per [BLOG_TABLE_FORMAT.md](BLOG_TABLE_FORMAT.md). - **Callouts:** Use `
    ` for "Wichtig:", "Hinweis:" (e.g. pricing caveats, legal requirements). - **Lists:** Use `