# Template Content Depth Guidelines

**Last Updated:** 2026-02-18  
**Purpose:** Per-block depth guidelines for template pages—when to expand vs stop

## Overview

Template 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.

## Per-Block Depth

### Minimum Depth per Block

- **50+ words per block** – No thin blocks
- **200–400 words per block** when target > 1,500 – Substantive blocks

### Format Variety (Format Mix)

- **Tables:** Use for structured data (comparisons, compliance checks, Prüfpunkte)
- **Steps:** Use `type: steps` for how-to sections (e.g. "Schritt für Schritt")
- **Callouts:** Use for disclaimers, critical notes (72h-Meldepflicht, GoBD)
- **Lists:** Use for step-by-step or bulleted items
- **Sections:** Use for narrative paragraphs

**Mix formats across blocks**—avoid all blocks being paragraphs only. Minimum: 1 table OR 1 steps OR 1 callout per template. Reference: Lohnabrechnung Vorlage, Midijob-Rechner.

### Cross-Block Redundancy Check

Before finalizing, verify:

- No two blocks answer the same question
- No repeated content across blocks
- Each block adds distinct value

## Going Beyond Word Count

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

- [ ] **All PAA addressed** – Every PAA from `paa-questions.json` or `faq-research.json` is covered by a block 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 blocks** – Each block has 50+ words; 200+ when target > 1,500
- [ ] **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.

## 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/blog/CONTENT_EXPANSION_CONTINUITY.md).

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

**Expand** when specific gaps are identified:
- `validate-template-content-completeness.php` reports uncovered PAA, content gaps, or missing format recommendations
- `validate-template-content-blocks.php` reports thin blocks

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

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

## References

- [TEMPLATE_CONTENT_CREATION_WORKFLOW.md](TEMPLATE_CONTENT_CREATION_WORKFLOW.md)
- [CONTENT_DEPTH_GUIDELINES.md](../../content/blog/CONTENT_DEPTH_GUIDELINES.md) (blog reference)