# Content Outline

**Post:** {POST_TITLE}
**Primary Keyword:** {PRIMARY_KEYWORD}
**Last Updated:** {LAST_UPDATED}

Create this outline from the skyscraper technique: document what top 10 competitors cover, then build an outline that covers everything + more + better format.

**Skyscraper principles:** Cover all topics/angles without redundancy. Each H2 must answer a distinct question or cover a distinct subtopic. See [SKYSCRAPER_TECHNIQUE_2026.md](../../SKYSCRAPER_TECHNIQUE_2026.md) Topic-Angle Coverage.

## Requirements

- **Word Count Target:** Set from `data/competitive-depth-analysis.md`. If unavailable (SISTRIX/Firecrawl failure), use **2,000–2,500 for lexikon** (not 1,800). For high-competition main topics, use 2,500–4,000. Validation requires outline target ≥ 80% of competitive-depth recommended minimum. See SISTRIX_FAILURE_FALLBACKS.md.
- **Primary keyword:** From `data/target-keywords.json`. **Related keywords:** From `data/keywords-sistrix.json` if available; integrate naturally.
- **Outline must cover:** All topics from competitive-depth-analysis.md content gaps; all H2s from top 10 competitors; PAA questions from `data/paa-questions.json` or `data/faq-research.json` (or SERP_ANALYSIS.md PAA section). Minimum 8 H2s (6 for inside-ordio).

### Section-brief completeness (required for Phase 4)

A **list of H2 titles only** (or one line per H2 with only a word-count estimate) is **not sufficient**. That was never the intended workflow: it skips planning for **H3s, lists, tables, and internal links**, and `generate-section-briefs.php` cannot invent a full editorial plan.

**Each H2 in “Main Sections” must include** (copy the block below per section):

| Field | Purpose |
|-------|--------|
| **Angle** | One of: Definition / How / **Comparison** / **Disambiguation** / Rules / Edge case / Practical / Conclusion — ensures no two H2s answer the same question. Use **Disambiguation** when SERP/office language mixes **different entity types** (e.g. software vendor vs. payroll process vs. professional service); use **Comparison** only when contrasting **same-type** concepts or explicit „Unterschied“ intent. |
| **Target words** | From total target ÷ H2 count; adjust if one section is the pillar. |
| **Evidence** | **Data-driven:** cite PAA (question text or id from `faq-research.json` / `paa-questions.json`), a related term from `keywords-sistrix.json` (`related_keywords` or batch metrics), GSC query (improvements), and/or competitor URL + heading from `competitor-analysis.json` / gap from `competitive-depth-analysis.md`. **Required for any H2 with Angle Comparison or Disambiguation** (non-placeholder line). If you cannot name PAA, competitor H2, or GSC — merge into another H2 or FAQ. |
| **Gap** | What the top competitor(s) miss or under-serve that this H2 covers (one line). |
| **Key points** | 3–6 bullets: facts, PAA phrases, competitor gaps, Ordio touchpoints. |
| **Formats** | Explicit: `Paragraphs` + at least one of `Table` / `ul` list / `ol` / `blog-note` / `caption` — state *where* (e.g. “comparison table: Begriff A vs B”). |
| **Planned H3s** | `H3: …` for each planned subsection, or `—` if the section is linear prose only. |
| **Internal links (planned)** | Lexikon slugs or product paths to weave in (first meaningful mention). |
| **Avoid** | What this H2 must *not* duplicate from other H2s. |

Optional: a **single “Section planning matrix”** table after the H2 list (columns: H2 | Angle | Formats | Planned H3s | Links) — faster for long outlines.

**Anti-pattern:** A separate `## Parsed H2 list` is fine as a **TOC**, but it must not replace the full Main Sections briefs above.

**Vendor / ecosystem Lexikon (z. B. Plattform-, Marken- oder Kanzlei-Ökosysteme):** Prefer an **Abgrenzung** heading and a table with an **„Ebene“** column (Anbieter / Prozess / Dienstleistung / Rolle) over a three-way **„vs.“** title that implies false symmetry. See [COMPARISON_AND_VS_SECTIONS_GUIDE.md](../../COMPARISON_AND_VS_SECTIONS_GUIDE.md).

## Data-Driven Checklist (fill from data files)

### PAA Coverage Matrix

From `data/paa-questions.json` or `data/faq-research.json`. For each PAA question, assign to H2 or FAQ:

**PAA–FAQ reservation strategy:** When PAA count ≥ 8, reserve 3–5 PAA for FAQs (not H2) to ensure supplemental FAQ pool. H2s cover main topics; FAQs capture long-tail, related, or alternative phrasings. Example: If "Was ist typisch für X?" maps to H2 "Merkmale", assign a different PAA to FAQ for variety.

| PAA Question | [ ] H2 | [ ] FAQ |
|--------------|--------|---------|
| (list from paa-questions.json) | | |

### Competitor H2 Mapping

From `data/competitor-analysis.json`. Ensure our outline covers all H2s from top 10 competitors:

| Competitor | Their H2s | Our H2 / Section |
|------------|------------|-----------------|
| #1 | (list headings) | (our H2 covering this) |
| #2 | (list headings) | |
| #3 | (list headings) | |
| #4 | (list headings) | |
| #5 | (list headings) | |
| #6 | (list headings) | |
| #7 | (list headings) | |
| #8 | (list headings) | |
| #9 | (list headings) | |
| #10 | (list headings) | |

### GSC Query Alignment

From `data/performance-gsc.json` (top queries). Ensure outline addresses each:

| Top GSC Query | How Outline Addresses |
|---------------|----------------------|
| (query 1) | (H2 or FAQ) |
| (query 2) | |
| (query 3) | |
| (query 4) | |
| (query 5) | |

### Content Gap Checklist

From [data/competitive-depth-analysis.md](./data/competitive-depth-analysis.md). Check each gap:

- [ ] Missing topic 1
- [ ] Missing topic 2
- [ ] Weak topic 1
- [ ] Missing format (table/list/FAQ)

### Topic-Angle Matrix (No Redundancy)

Ensure each H2 covers a **distinct angle**. Run `check-outline-h2-overlap.php` before content creation.

| H2 | Angle (Definition/How/Comparison/Rules/Edge Case/Practical/Conclusion) | Distinct? |
|----|----------------------------------------------------------------------|-----------|
| H2 1 | (e.g. Definition) | [ ] |
| H2 2 | (e.g. How/Process) | [ ] |
| ... | | |

**Redundancy check:** No two H2s answer the same question. Definition appears once. Fazit summarizes—does not repeat intro verbatim.

### Unique Value

Skyscraper 2026 requires differentiation—not just replication. Check at least one:

- [ ] Original data or research (survey, calculation)
- [ ] Expert insights or Ordio-specific examples
- [ ] Better format than competitors (table, list, step-by-step)
- [ ] Fresher information (2026 stats, current law)
- [ ] Use case or scenario competitors don't cover

**Data sources to cite in the outline (for reviewers):** tie each checked item to evidence—e.g. “stats from `competitive-depth-analysis.md`”, “gap vs competitor #1 in `competitor-analysis.json`”, “PAA / GSC query from `performance-gsc.json` or `faq-research.json`”.

See [SKYSCRAPER_TECHNIQUE_2026.md](../../SKYSCRAPER_TECHNIQUE_2026.md) "Differentiation Over Duplication" and [KEYWORD_RESEARCH_WORKFLOW.md](../../KEYWORD_RESEARCH_WORKFLOW.md) for keyword ↔ section mapping.

## Structure

### Introduction

- **Pattern interrupt:** First sentence stops scrolling—bold claim, surprising stat, direct challenge, or provocative question. Avoid dictionary definitions, long backstories, generic SEO intros.
- Hook (first sentence)
- Context (what is the topic)
- Value proposition (what reader will learn)
- Primary keyword in first paragraph
- 2-3 paragraphs max

### Main Sections (H2)

Use question-style H2s where PAA/intent match (e.g. "Was ist ein Midijob?", "Ab wann gilt ein Midijob?"). Use declarative H2s when they support natural flow (e.g. "Rechtliche Grundlagen", "Fazit", comparison tables). Target 8–12 H2 sections for main topics.

**Outline structure should prioritize competitive analysis, SERP_ANALYSIS, and content gaps—not force questions everywhere. Narrative flow and user experience come first.**

**Section Brief (required for each H2):** Fill target words, key points, formats, and PAA before writing. Target words per section = total target ÷ H2 count. Run `generate-section-briefs.php` to auto-populate from data. See [CONTENT_CREATION_WORKFLOW_2026.md](../../CONTENT_CREATION_WORKFLOW_2026.md).

**H3 subsections (plan during outline):** For each H2, decide if H3s add value. Use H3 when: (1) section has 3+ distinct subtopics or items currently bold inline; (2) TOC jump links would help readers (PAA, featured-snippet potential); (3) Vor-/Nachteile, Formen/Arten, Tipps, Rechtliches with substantial content. Don't force—H2+paragraphs is valid for short or linear sections. **Word count alone does not determine H3 usage.** Use structure and TOC value. When H3s are used: optional intro paragraph between H2 and first H3. See [CONTENT_DEPTH_GUIDELINES.md](../../CONTENT_DEPTH_GUIDELINES.md) H3 examples; [TOC_BEST_PRACTICES.md](../../TOC_BEST_PRACTICES.md).

**H3 planning checklist (run for each H2 before writing):**
- [ ] 3+ distinct subtopics with 2+ sentences each? → Plan H3s
- [ ] Vor-/Nachteile, Formen/Arten, Tipps, Rechtliches with substantial content? → Plan H3s
- [ ] Step-by-step (4+ steps) with 2+ sentences per step? → Plan H3 per step
- [ ] **Numbered items (3+ items like "1. Title", "2. Title") with substantial content (2+ sentences each)?** → Convert to H3s: `<p><strong>1. Title</strong></p>` → `<h3>Title</h3>`
- [ ] **Bold inline items (3+ items like "**Meldepflichten:**", "**Gefährdungsbeurteilung:**", "**Kommunikation:**") with lists or 2+ sentences each?** → Convert to H3s: `<p><strong>Meldepflichten:</strong> ...</p>` → `<h3>Meldepflichten</h3><p>...</p>`. Common in HR-Guidance, Best Practices, Checklist sections.
- [ ] TOC value: Would H3s help readers jump to answers? (PAA, featured-snippet potential) → Plan H3s
- [ ] Section length as secondary signal? (>200 words and subdivision helps scannability) → Optional; not primary criterion
- [ ] 4+ brief items (1–2 sentences each)? → Use list, not H3s
- [ ] Document "Planned H3s" in section brief (or "—" if H2+paragraphs)

1. **H2: [Section title]**
   - **Angle:** Definition | How/Process | Comparison | Rules | Edge Case | Practical | Conclusion
   - **Target words:** ~X (from target ÷ H2 count)
   - **Key points:** (2–5 bullet points from PAA, competitor, content gaps)
   - **Formats:** Table | List | Paragraphs
   - **Examples:** (what to include)
   - **PAA covered:** (which PAA questions)
   - **Avoid:** (what NOT to repeat from other H2s—e.g. "Don't repeat definition from H2 1")
   - **Planned H3s:** (if 3+ subtopics, Formen/Arten, Vor-/Nachteile, Tipps, Rechtliches) H3: [Subsection] | H3: [Subsection] | ...

2. **H2: [Section title]**
   - **Angle:** (Definition | How | Comparison | Rules | Edge Case | Practical | Conclusion)
   - **Target words:** ~X
   - **Key points:**
   - **Formats:**
   - **Examples:**
   - **PAA covered:**
   - **Avoid:** (what NOT to repeat)
   - **Planned H3s:** H3: [Subsection] *(or "—" if H2+paragraphs)*

3. **H2: [Section title]**
   - ...

(Continue for all sections. Cover all competitor topics + gaps they miss.)

### FAQs

Target 5–15 FAQs. List questions from PAA, GSC queries that are NOT already covered by H2 sections. These go in the `faqs` array, NOT in content HTML.

**FAQs must NOT duplicate H2 questions.** Each FAQ should address a question NOT already covered by an H2 section. Prioritize supplemental FAQs from PAA/GSC that add unique angles. Run `php v2/scripts/blog/check-h2-faq-overlap.php --post=slug --category=category` before finalizing.

1. [Question 1]
2. [Question 2]
3. ...

### Conclusion

- Summary of key points
- Next steps or CTA (if appropriate)
- **Fazit (optional for Lexikon):** For Lexikon skyscraper posts, include H2 "Fazit" or "Zusammenfassung" (2–3 paragraphs) to summarize key points. Improves scannability and satisfies conclusion expectation from PRE_CONTENT_CHECKLIST.

### Valuable Elements to Preserve

- [ ] Calculators (Alpine.js)
- [ ] Videos (YouTube embeds)
- [ ] Essential images (with alt text)
- [ ] Tables
- [ ] Interactive elements

## Tables

When using tables: Use plain `table`/`thead`/`th`/`td`; wrap in `table-breakout-wrapper`. **Never** use Tailwind (`bg-gray-50`, `border-gray-200`) on table elements—see [BLOG_TABLE_FORMAT.md](../../BLOG_TABLE_FORMAT.md).

**Formulas / visual formats:** Do **not** use tables for formulas or calculations. Use `<div class="formula-block">` for **canonical** equations only; tag in this outline which H2s need formula-block vs. table vs. note—see [CONTENT_FORMAT_PATTERNS.md](../../CONTENT_FORMAT_PATTERNS.md) § *Visual format decision guide*.

**Do not copy Evidence rows, PAA ids, or SISTRIX/SERP shorthand verbatim into `content-draft.html` or live `content.html`.** Translate planning into reader-first prose; see [READER_FACING_COPY_GUARDRAILS.md](../../READER_FACING_COPY_GUARDRAILS.md).

## References

- [SERP_ANALYSIS.md](./SERP_ANALYSIS.md) – Competitor analysis
- `data/paa-questions.json` – PAA questions for H2/FAQ alignment
- [data/competitive-depth-analysis.md](./data/competitive-depth-analysis.md) – Competitor topics, word count target (if available; from analyze-competitor-content-depth.php)
- [BLOG_POST_IMPROVEMENT_PROCESS.md](../../BLOG_POST_IMPROVEMENT_PROCESS.md) – Full workflow