# Content Depth Guidelines 2026

**Last Updated:** 2026-04-04  
**Purpose:** Guidelines for determining content depth beyond word count, including when to expand vs stop

## Minimum vs Suggested Targets

**Aim for suggested; minimum is the fallback.** Content that consistently hits minimums will underperform vs competitors.


| Term          | Definition                                                                               |
| ------------- | ---------------------------------------------------------------------------------------- |
| **Minimum**   | Floor for validation (80% of competitive-depth recommended). Use for edge cases only.    |
| **Suggested** | Target to aim for (100% of competitive-depth recommended). Best competitive positioning. |


**Guidance:** Set outline target to 100% of competitive-depth recommended. Use 90% when topic is narrow or competition is low.

## Overview

Content depth is measured by **comprehensiveness, value, and competitive positioning** - not just word count. These guidelines help determine when to expand content and when to stop.

### Intro and body copy (people-first)

- **Situation and outcome first:** Open with who the article is for and what they take away. Do not use rhetorical “Warum ein eigener Artikel…?” / “Weil Suchanfragen…” or other **meta-SERP narration** in published `<p>` text — intent, cannibalization, and “why this URL exists” belong in `SERP_ANALYSIS.md`, `CONTENT_OUTLINE.md`, and `KEYWORD_DECISION.md`, not in the body.
- **Links in context:** Integrate internal links where the topic is discussed; avoid editorial first-person linking (“verlinken wir”, “verweisen wir gezielt”). See [INTERNAL_LINKING_WORKFLOW_2026.md](INTERNAL_LINKING_WORKFLOW_2026.md) and [PEOPLE_FIRST_INTRO_AND_LINKING.md](PEOPLE_FIRST_INTRO_AND_LINKING.md).
- **Optional check:** `python3 v2/scripts/blog/audit-meta-intro-language.py` (or `make audit-blog-meta-intros`) flags common anti-patterns in `docs/content/blog/posts/**/content.html`.

## Content Depth Metrics

### Beyond Word Count

Measure content depth by:

1. **Topic Coverage:**
  - Primary topic covered comprehensively
  - Related topics addressed
  - Edge cases and exceptions included
  - Common questions answered
2. **Value Indicators:**
  - Practical examples provided
  - Step-by-step guides included
  - Best practices shared
  - Troubleshooting section present
3. **Format Diversity:**
  - Tables for structured data
  - Lists for step-by-step or comparisons
  - Visual breaks (headings, images)
  - FAQs for common questions
  - **Emphasis:** Use `<strong>` sparingly in continuous prose for real importance—see [BLOG_STRONG_AND_EMPHASIS.md](BLOG_STRONG_AND_EMPHASIS.md). **List/table label patterns** (bold lead-ins in `<li>`, table cells, `blog-note` labels) are exempt from “low density” prose rules; do not remove those for artificial metrics.
4. **Authority Signals:**
  - Expert insights included
  - Original data or research
  - Real-world examples
  - Up-to-date information

### E-E-A-T Signals

Google evaluates content quality via E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). Strengthen each dimension:


| Signal                | How to Demonstrate                                                                  |
| --------------------- | ----------------------------------------------------------------------------------- |
| **Experience**        | First-hand examples, case studies, real scenarios ("In der Praxis…", "Beispiel: …") |
| **Expertise**         | Clear explanations, correct terminology, step-by-step guidance                      |
| **Authoritativeness** | Internal links to pillar pages, related posts; structured content                   |
| **Trustworthiness**   | Accurate information, transparent sources, up-to-date (year, legal references)      |


**Per-section check:** Does this section demonstrate experience or expertise? Is it trustworthy? See [CONTENT_CREATION_WORKFLOW_2026.md](CONTENT_CREATION_WORKFLOW_2026.md).

## Going Beyond Word Count

Best-in-class content prioritizes comprehensiveness and unique value over hitting a word count. Before finalizing, verify:

- **All PAA addressed** – Every PAA question from `paa-questions.json` or `faq-research.json` is covered by an H2 or FAQ
- **All competitor topics covered** – Content gaps from `competitive-depth-analysis.md` are addressed
- **Examples/tables where competitors have them** – If top competitors use tables or step-by-step lists, include equivalent or better
- **Definition in first 20%** – Core definition (Was ist…?) appears within the first 20% of content
- **No thin sections** – Each H2 has 2+ paragraphs or 1 paragraph + list/table
- **Unique value** – What we do better (format, depth, examples, freshness) is clear

**Word count is a guideline, not a ceiling.** Focus on completeness, examples, and user value.

### Depth vs. Width (2026)

**Depth (aim for):** Breaking down complex ideas with examples, step-by-step, tables, real use cases. Each section adds substantive value to the same topic.

**Width (avoid):** Adding unrelated subtopics to hit word count—e.g. "history of X," tangential digressions, generic filler. Dilutes value and hurts UX.

**Principle:** 5 excellent sections beat 15 mediocre ones. Quality over quantity.

**AEO/GEO answer-first:** For **question-style H2s only**, add a 120–150 character answer capsule immediately after the heading—direct, scannable summary before expanding. Supports featured snippets and answer engines. **Do not** use answer-style leads (e.g. "Ja, …", "Nein. …") under declarative H2s (e.g. "Rechtliche Anforderungen", "Excel vs. Software")—the first paragraph should flow from the header, not read as an answer to an unasked question.

**AEO capsules without repetitive labels:** The direct answer must be in the first `<p>` after a question H2, but **do not** paste the same bold lead-in (e.g. **„In Kürze:“**) under every section—it reads templated and hurts perceived quality. Prefer: answer in the first sentence without a label, or vary framing (**Kernaussage**, inline bold on one keyword, short list). **Rule of thumb:** at most **one** identical bold prefix like „In Kürze:“ per article unless there is a strong UX reason. Inventory: `make audit-blog-repetition` ([audit-blog-repetitive-phrasing.py](../../../v2/scripts/blog/audit-blog-repetitive-phrasing.py)); per-post check: `validate-aeo-capsule-diversity.php` (in `make blog-post-validate` / strict).

## Expand vs Stop

**Continuous Expansion Principle:** Do not stop until all validators pass and all gaps are addressed. Run validation after each content pass; if any fails, address gaps and re-run. See [CONTENT_EXPANSION_CONTINUITY.md](CONTENT_EXPANSION_CONTINUITY.md).

**Stop** only when all outline key points are covered, all PAA addressed, formats present, and section depth met. Run `validate-section-depth.php` and `validate-content-completeness.php`—both must pass.

**Expand** when specific gaps are identified:

- `validate-content-completeness.php` reports uncovered PAA, content gaps, or missing format recommendations
- `validate-section-depth.php` reports thin sections

**Stop** if adding would require fluff—better to have focused, valuable content than padded sections.

**Never** add filler to reach word count. Address specific gaps with substantive content. See [CONTENT_CREATION_WORKFLOW_2026.md](CONTENT_CREATION_WORKFLOW_2026.md).

## Depth Levels

### Minimum Depth

**Characteristics:**

- Covers topic basics
- Answers primary question
- Includes definition (within first 20%)
- Provides practical value
- **Word Count:** 1,200-1,500 words (low competition)

**When Appropriate:**

- Low competition keywords (< 30 difficulty)
- Simple topics that don't need extensive coverage
- Quick reference guides
- Definition posts for niche terms

### Competitive Depth

**Characteristics:**

- Matches top competitors
- Covers related topics
- Includes examples and use cases
- Addresses common questions
- **Word Count:** 1,800-2,500 words (medium competition)

**When Appropriate:**

- Medium competition keywords (30-50 difficulty)
- Main informational content
- How-to guides
- Most lexikon and ratgeber posts

### Comprehensive Depth

**Characteristics:**

- Exceeds competitors
- Includes unique value (data, insights, expert opinions)
- Covers edge cases and advanced topics
- Multiple content formats (tables, lists, visual breaks)
- **Word Count:** 2,500-4,000+ words (high competition)

**When Appropriate:**

- High competition keywords (50+ difficulty)
- Pillar content
- Skyscraper technique targets
- Comprehensive guides

### Main Topic Classification

**Main topics** are core employment/labor terms that users search for frequently and that competitors cover in depth. These should target **Comprehensive Depth** (2,500–4,000+ words) even when keyword difficulty is medium.

**Examples of main topics:**

- Midijob, Minijob, 450-Euro-Job
- Arbeitsbescheinigung, Arbeitszeugnis
- Zeiterfassung, Dienstplan, Schichtplanung
- Lohnabrechnung, Urlaubsanspruch

**Indicator:** If the topic has its own Wikipedia/Lexikon entry, multiple PAA questions, or high search volume across related queries, treat it as a main topic.

**Target:** 2,500–4,000+ words with 8–12 H2 sections, question-style headings, tables, examples, and step-by-step where applicable.

### H3 Subsections (Optional, Case-by-Case)

**Principle:** Use H3s only when they add clarity and improve scannability. Short or simple H2 sections may have paragraphs only—no H3 required. Headings support the reader, not decorate the page (Yoast, WebAIM).

**"Optional" means:** Not every section needs H3s—but when criteria are met, use them. Do not interpret "optional" as "prefer skipping." Plan H3s during the outline phase when criteria apply.

**Word count does not determine H3 usage.** Use structure, TOC value, and scannability on a case-by-case basis. Prioritize: subtopics, TOC/scannability, content type. Never add H3s just to hit a word-count target.

**Use H3 when (checklist, in priority order):**

1. **Structure:** Section has **3+ distinct subtopics** and each has **2+ sentences** of content (e.g. Formen with substantial definitions)
2. **TOC/Scannability:** Would H3s help readers jump to answers? (PAA question, featured-snippet potential, distinct clarifying question)
3. **Content type:** Section has **Vorteile/Nachteile** or **Formen/Arten** with multiple items—each H3 has substantial content (list or 2+ paragraphs)
4. Section has **Tipps/Checkliste** with 3+ items → use H3 per tip **only if** each tip has 2+ sentences. Otherwise use `<ul>` with bold lead-in and 2-3 sentences per item
5. Section has **Rechtliche Grundlagen** with multiple laws/regulations—each H3 has 2+ sentences, or merge brief items into one paragraph
6. **Bold inline items** under one H2 (e.g. "**Schichtarbeit:** ... **Kurzarbeit:** ...") → convert to H3s **only if** each has 2+ sentences; otherwise use list
7. **Optional secondary:** Section is long and subdivision improves scannability (length alone is not a primary criterion)

**Negative example (over-H3 usage):** The remote-work post initially had H3s for Formen (1 sentence each), Rechtliche Grundlagen (3× 1 sentence each), and Tipps (5× 1-2 sentences each). This created thin, repetitive sections. Per Semji: "Replace titles by bullet lists if more than 4 consecutive elements." Fix: Formen → list; first 3 Rechtliche → merged paragraph; Tipps → list; Vertragliche Regelungen (substantial) → kept as H3.

**List vs H3 Decision**

- **Use H3 when:** Item has 2+ paragraphs OR 3+ sentences of distinct content; section has 3 or fewer H3s; TOC jump links add value
- **Bold inline → H3:** When bold text introduces a distinct subtopic (question, clarification, comparison) with 2+ sentences of answer OR a list with 3+ items, consider H3 instead of bold inline. Evaluate: Would a TOC jump link help readers? Does it improve scannability? Does it fit the section flow? Apply contextually—use when it improves structure, not when it would feel forced.

**Common pattern requiring H3 conversion:** Sections like "Praktische HR-Guidance", "Best Practices", "Checkliste" often have multiple bold inline items (e.g., "**Meldepflichten:**", "**Gefährdungsbeurteilung:**", "**Kommunikation:**") each followed by a list or 2+ sentences. These should be H3s, not bold inline text. **Check during outline phase:** If an H2 has 3+ bold inline items with substantial content, plan H3s.

- **Use list when:** 4+ consecutive items; each item is 1-2 sentences; Semji rule: "replace titles by bullet lists if more than 4 consecutive elements"
- **"Title: description" pattern:** When 3+ consecutive blocks follow the pattern **Bold label:** content (e.g. comparisons like "MBO vs OKR vs Mitarbeitergespräch"), use `<ul><li><strong>Title:</strong> description</li></ul>`. For **category + sub-items** (e.g. HR with 4 examples), use bold label as paragraph then separate list: `<p><strong>HR:</strong></p><ul><li>...</li></ul>` – not nested lists. **Exception:** FAQ-style Q&A in main content (e.g. "Ist X Pflicht?", "Kann ich ablehnen?") may stay as separate paragraphs – list format can feel repetitive for legal Q&A; use judgment.
- **Minimum H3 depth:** Each H3 should have ≥2 sentences or a list/table. Single-sentence H3s → convert to list or expand
- **Structure variety:** Vary format across sections (H2+paragraphs, H2+list, H2+H3, H2+table). Avoid uniform "H3 per tip" when tips are brief

**When to use H3:**

- Section has distinct subtopics (e.g. "Rechtliche Grundlage" vs "Optionalität" under "Was ist die Probezeit?")
- TOC jump links would help readers (PAA question, featured-snippet potential)
- Step-by-step items, tips, or comparisons (e.g. "Einfaches vs. qualifiziertes Zeugnis")
- **Multiple items under one H2** that are currently bold inline (e.g. "Schichtarbeit", "Kurzarbeit", "Kündigung" in one section) → convert to H3s for TOC, scannability, and SEO
- Long section that benefits from subdivision (optional secondary signal; structure and value matter more than word count)

**When NOT to use H3:**

- Section is short or flows linearly
- Adding H3 would feel forced or artificial
- Paragraphs alone flow better and read more naturally

**When H3s are used:** Optional intro paragraph(s) between H2 and first H3 for smoother transition. Use only when content benefits; avoid cheesy transitions.

**H3 planning checklist (during outline):** For each H2, ask: (1) Does it have 3+ distinct subtopics or items? (2) Would H3s appear in TOC and help readers jump? (3) PAA or featured-snippet potential? If yes to (1) or (2), plan H3s. Do not use word count as primary criterion. Example: "Sonderfälle: Schichtarbeit, Kurzarbeit, Kündigung" → H3 per item; "Wie wird X berechnet?" with Formel + Was zählt + Beispiel → H3 per part.

**Concrete examples (Urlaubsentgelt):**

- **Wie wird Urlaubsentgelt berechnet?** → H3: Formel und Berechnungsgrundlage | Was zählt – und was nicht | Beispielrechnung
- **Urlaubsentgelt bei Teilzeit und Minijob** → H3: Urlaubsentgelt bei Teilzeit | Urlaubsentgelt bei Minijob
- **Sonderfälle: Schichtarbeit, Kurzarbeit, Kündigung** → H3: Schichtarbeit | Kurzarbeit | Kündigung | Provision und variable Bezüge
- **Versteuerung und Verjährung** → H3: Steuer und Sozialversicherung | Verjährung von Ansprüchen

**Concrete examples (Remote Work, after refinement):**

- **Was ist Remote Work?** → Intro paragraph + H3 for distinct clarifying question (3+ sentences; bold inline would miss TOC value) + closing paragraph
- **Remote Work vs. Homeoffice vs. Telearbeit – die Formen** → List with bold lead-in (each 1 sentence; table already summarizes) + **H3: Was ist der Unterschied zwischen Homeoffice und Remote Work?** (PAA question, 3 sentences—use H3 for featured snippet)
- **Remote Work – Vorteile und Nachteile** → H3: Vorteile für Mitarbeiter | Vorteile für Arbeitgeber | Nachteile (each has list or 2+ paragraphs)
- **Rechtliche Grundlagen für Remote Work** → Merged paragraph (ArbZG, ArbStättV, Zeiterfassung) + H3: Vertragliche Regelungen (substantial)
- **Remote Work in der Praxis – Tipps für HR** → List with bold lead-in (5 tips, 1-2 sentences each; per Semji)

**For long posts (>2,500 words):** Consider H3s where logical; H2+paragraphs is valid for many sections. Typical range 5–30 H3s total when sections warrant subdivision. See [BLOG_CONTENT_RESTRUCTURING_GUIDE.md](BLOG_CONTENT_RESTRUCTURING_GUIDE.md) for restructure vs expand guidance.

## Format Checklist (During Drafting)

Before finalizing each section, verify:

- **3+ consecutive "Bold label: description" blocks?** → Use `<ul><li><strong>Label:</strong> description</li></ul>` instead of separate paragraphs (e.g. Zeugnisse, Zertifikate, Ausbilderschein, Arbeitszeugnisse; Fachwissen, IT, Sprachen, Management, Technisch)
- **4+ items in one paragraph?** (e.g. "Konkrete Formate: Sprachkurse, IT-Schulungen, Seminare, Zertifikate...") → Convert to list with bold lead-ins
- **Question-style subtopics with 2+ sentences each?** (e.g. "Warum ist X wichtig?", "Welche X sind wichtig?") → Consider H3s for TOC jump links and PAA/featured-snippet potential
- **Inline (1)(2)(3) numbering?** → Use `<ol><li>…</li></ol>` instead

## Section Depth Standards (No Thin Sections)

**Principle:** Every H2 section must provide substantive value. No "half-assed" or placeholder sections.

### Minimum Section Depth

Each H2 section must have at least one of:

- **2+ substantive paragraphs** – Each paragraph answers the heading, adds context, or gives actionable guidance
- **1 paragraph + structured content** – List (4+ items), table, or step-by-step with explanation
- **Practical examples** – At least one concrete example or use case when the topic allows it

### What "Substantive" Means

- **Answers the question** – The heading promises something; the content delivers it
- **Adds context** – "Why" matters, not just "what"
- **Actionable** – Reader can act on the information (how to do X, how to avoid Y)
- **No redundancy** – Don't repeat the same point in different words

### Red Flags (Avoid)

- Single short paragraph with a bullet list and no explanation
- Generic advice without specifics ("Be thorough" without saying how)
- Sections that restate the intro or another section
- Bullet dumps without "so what" or "how"
- **"Tipps" or "Checkliste" sections:** Three bullet points under an H2 with no formatting – use H3 sub-headings per tip, or a proper `<ul>`/`<ol>` with substantial content per item (2–3 sentences each)

### Numbered Steps – Use Ordered Lists

When content presents sequential steps (e.g. "Praktische Schritte für HR", "So geht's", "5 Schritte zu X"), use `<ol>` – never inline numbering like (1), (2), (3) in a single paragraph.

**❌ BAD:**

- Single paragraph: "Schritte: (1) Erstes tun. (2) Zweites tun. (3) Drittes tun. Fazit-Satz."

**✅ GOOD:**

- `<ol><li>Erstes tun.</li><li>Zweites tun.</li><li>Drittes tun.</li></ol><p>Fazit-Satz.</p>`

**Rationale:** Ordered lists improve scannability, accessibility, and featured-snippet potential. Inline (1)(2)(3) in one paragraph is harder to scan and less semantic.

### "Tipps" / "Checkliste" Sections – Formatting Requirement

Sections with tips, checklists, or step-by-step advice must NOT be minimal list dumps:

**❌ BAD:**

- H2 "Tipps zur X" with 3 paragraphs, each starting with bold text – no structure, no hierarchy, feels like a dump

**✅ GOOD:**

- H2 + intro paragraph + **H3 per tip** (e.g. "1. Anlass direkt vermerken", "2. Nachträglich ergänzen") with 2–3 sentences each. H3s appear in TOC, give visual structure.
- OR: H2 + intro + `**<ol>` or `<ul>`** with list items that contain 2–3 sentences each (not one-liners)

**Rule:** Each tip/item must have enough content to stand alone. If it’s just a bold lead-in + one sentence, it’s too thin – expand or use H3 structure.

### Quality Check

Before publishing, ask for each section: *"Would a reader who landed here feel their question was fully answered?"* If not, add depth—examples, consequences, how-to, or clarification.

### Anti-Fluff

Every sentence must add unique value. Cut micro-fluff (e.g. "sehr", "wirklich", "aufgrund der Tatsache, dass" → "aufgrund"), vague claims, and redundant paragraphs. Front-load answers; use decisive tone. See [ANTI_FLUFF_CHECKLIST.md](ANTI_FLUFF_CHECKLIST.md).

### Fazit Requirement (Lexikon)

**Lexikon posts MUST end with an H2 Fazit (or Zusammenfassung)** summarizing key points without copying the intro. Use 2–3 sentences; may include Ordio product mention. The Fazit provides closure and reinforces takeaways. `validate-content-completeness.php` warns if Fazit is missing for lexikon posts.

### Cross-Section Redundancy Check

**Before finalizing content:**

- **Definition:** Appears once (intro or first H2); not repeated verbatim in other sections
- **Key facts:** Each fact stated once; if referenced elsewhere, use "Wie in [H2 X] beschrieben" or brief pointer
- **Fazit:** Summarizes key points; does not copy intro or repeat section content verbatim (see Fazit Requirement above)
- **Checkliste/Tipps:** Items are actionable and distinct; no generic "Beachte die Regelungen" that repeats another H2

**When expanding a section:** Ask "Does this add new information or repeat what's already in [H2 Y]?" If repeat, cut or move to the canonical section.

**Sibling/paired post benchmark:** When creating a post with a natural paired post (e.g. Hard Skills vs Soft Skills, Job Enrichment vs Job Rotation), compare depth and formats to the sibling. Aim for parity: both should have comparison list/table, branchenspezifisch examples with industry links, concrete training formats, practical HR steps. Avoid one post being noticeably thinner.

**See:** [Skyscraper Technique 2026](SKYSCRAPER_TECHNIQUE_2026.md) for competitive depth; [Content Quality Standards 2026](CONTENT_QUALITY_STANDARDS_2026.md) for format requirements.

### Formatting for Formulas, Notes, and Legal Info

**When to use which pattern (and how much):** Follow the **Visual format decision guide** at the top of [CONTENT_FORMAT_PATTERNS.md](CONTENT_FORMAT_PATTERNS.md)—matrix, formula-block caps, table vs. note discipline, and new-post vs. improvement workflow hooks.

- **Formulas:** Use `<div class="formula-block">` with one formula per `<p>` for **canonical** equations; keep worked numeric examples in prose or lists unless the section is calculation-first. **Never use tables for formulas or calculations** – formula-block has dedicated styling.
- **Notes:** Use `<blockquote class="blog-note blog-note--important">` sparingly for high-impact “Wichtig:” / “Achtung:” callouts—not for every tip.
- **Legal:** Multiple paragraphs in one section → H3 per paragraph if 2+ sentences each; otherwise merged paragraph with bullet list of paragraph references for scannability.

See [CONTENT_FORMAT_PATTERNS.md](CONTENT_FORMAT_PATTERNS.md) for HTML examples and the full decision guide.

## Section Expansion Guidelines

### When to Expand a Section

**Expand When:**

1. **Competitor Analysis Shows Gap:**
  - Competitors cover subtopics you don't
  - Competitors have more examples
  - Competitors use better formats (tables, lists)
2. **User Needs Not Met:**
  - Section doesn't fully answer the question
  - Missing practical examples
  - Missing step-by-step guidance
3. **Content Gaps Identified:**
  - Missing use cases
  - Missing best practices
  - Missing troubleshooting
4. **Performance Data Indicates Need:**
  - High bounce rate on section
  - Users not engaging with content
  - Competitors ranking higher

### When to Stop Expanding

**Stop When:**

1. **Topic Fully Covered:**
  - All important aspects addressed
  - User needs fully satisfied
  - No content gaps remaining
2. **Diminishing Returns:**
  - Adding content doesn't add value
  - Content becomes repetitive
  - User experience degrades (too long, hard to scan)
3. **Quality Over Quantity:**
  - Better to have focused, valuable content
  - Fluff reduces quality
  - Value matters more than length
4. **Format Limitations:**
  - Some sections don't need extensive expansion
  - Quick reference sections can be concise
  - Definitions can be comprehensive at moderate length

## Expand vs Stop Decision Framework

### Decision Tree

```
Is topic fully covered?
├─ No → Expand section
│   ├─ Add missing subtopics
│   ├─ Add examples/use cases
│   └─ Add best practices
│
└─ Yes → Check value
    ├─ Adding more adds value? → Expand
    │   ├─ Unique insights
    │   ├─ Original data
    │   └─ Expert opinions
    │
    └─ Adding more doesn't add value? → Stop
        ├─ Content becomes repetitive
        ├─ User experience degrades
        └─ Focus on quality over quantity
```

### Questions to Ask

**Before Expanding:**

1. **Does this add genuine value?**
  - New information?
  - Better examples?
  - Unique insights?
2. **Does this address user needs?**
  - Answers questions users have?
  - Provides practical value?
  - Improves user experience?
3. **Does this improve competitive position?**
  - Fills content gaps vs competitors?
  - Matches or exceeds competitor depth?
  - Adds unique value competitors don't have?

**If answer is "no" to all:** Stop expanding, focus on quality

## Formatting Flexibility

### Use Different Formats to Enhance Depth

**Tables:**

- Comparison data
- Specifications
- Pricing
- Structured information

**Lists:**

- Step-by-step guides
- Top N lists
- Feature comparisons
- Checklists

**Visual Breaks:**

- Headings (clear hierarchy)
- Images (support key points)
- Spacing (improve readability)
- Callout boxes (highlight important info)

**FAQs:**

- Answer PAA questions
- Address common concerns
- Cover related topics
- Improve scannability

### Format Selection Guidelines

**Use Tables When:**

- Comparing multiple items
- Presenting structured data
- Showing specifications or features
- Displaying pricing or options

**Use Lists When:**

- Step-by-step processes
- Top N recommendations
- Feature comparisons
- Checklists or action items

**Use Visual Breaks When:**

- Long text blocks need separation
- Key points need emphasis
- Scannability needs improvement
- Mobile readability is important

## Content Depth Checklist

### Coverage Checklist

- Primary topic covered comprehensively
- Related topics addressed
- Edge cases and exceptions included
- Common questions answered (PAA)
- User intent fully satisfied

### Value Checklist

- Practical examples provided
- Step-by-step guides included
- Best practices shared
- Troubleshooting section present
- Real-world scenarios included

### Format Checklist

- Tables used for structured data
- Lists used for step-by-step or comparisons
- Visual breaks improve readability
- FAQs answer common questions
- Images support key points

### Authority Checklist

- Expert insights included
- Original data or research
- Real-world examples
- Up-to-date information
- Credible sources cited

## Examples

### Example 1: Minimum Depth (Appropriate)

**Topic:** "arbeitszeitkonto muster"  
**Competition:** Low  
**Depth:** Minimum  
**Word Count:** 1,200 words  
**Rationale:** Low competition, simple topic, covers basics comprehensively

### Example 2: Competitive Depth (Appropriate)

**Topic:** "zeiterfassung app"  
**Competition:** Medium  
**Depth:** Competitive  
**Word Count:** 2,500 words  
**Rationale:** Matches competitor depth, covers related topics, includes examples

### Example 3: Comprehensive Depth (Appropriate)

**Topic:** "urlaubsantrag stellen"  
**Competition:** High  
**Depth:** Comprehensive  
**Word Count:** 4,000 words  
**Rationale:** High competition, exceeds competitors, includes unique value (templates, examples)

## Key Principles

1. **Value Over Length:** Better content beats longer content
2. **User Intent First:** Match depth to what users need
3. **Competitive Positioning:** Analyze competitors, then exceed their depth/value
4. **Flexible Formatting:** Use tables, lists, visual breaks to enhance readability
5. **Quality Standards:** Maintain quality, don't add fluff

## References

- [Flexible Word Count Guidelines](FLEXIBLE_WORD_COUNT_GUIDELINES.md)
- [Skyscraper Technique 2026](SKYSCRAPER_TECHNIQUE_2026.md)
- [Content Quality Standards 2026](CONTENT_QUALITY_STANDARDS_2026.md)

