# Content Writing Guidelines 2026

**Last Updated:** 2026-02-11
**Purpose:** Consolidated 2026 best practices for blog content: natural flow, answer-first formatting, readability, and flexible heading hierarchy.

## Overview

Content must serve both human readers and AI systems. Prioritize natural flow and user value over rigid structure. See also [CONTENT_WRITING_BEST_PRACTICES_2026.md](../CONTENT_WRITING_BEST_PRACTICES_2026.md) for human-first and AI-optimization principles.

## Answer-First Formatting

- **Direct answer below question headings:** 40–60 word direct answer; first sentence = the answer
- **Featured snippet optimization:** Match format to intent (paragraph for definitions, lists for steps, tables for comparisons)
- **Self-contained chunks:** Each section should be quotable without extra context

## Chunk Size and Readability

- **Chunk size:** 40–120 words for AI extraction; 250–350 words per section (Yoast)
- **Short sentences:** <20 words preferred; vary length for rhythm
- **Short paragraphs:** 2–4 sentences; avoid walls of text
- **Plain vocabulary:** Avoid jargon unless necessary; define terms when used

## Natural Flow and Heading Hierarchy

- **H3s are optional and case-by-case.** "Optional" means *not every section needs H3s*—not "prefer skipping H3s." When criteria are met (3+ distinct subtopics, Formen/Arten, Vor-/Nachteile, Tipps, Rechtliches), use H3s. H2+paragraphs is valid for short or linear sections.
- **Don't force robotic headings.** Structure for chunkability; prioritize flow over quotas.
- **Decision criteria:** Add H3 when section has distinct subtopics, step-by-step items, or comparisons. Omit H3 when section is short, linear, or paragraphs flow better alone. See [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md) and [HEADING_HIERARCHY_GUIDE.md](HEADING_HIERARCHY_GUIDE.md) for the full H3 checklist.

See [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md) and [HEADING_HIERARCHY_GUIDE.md](HEADING_HIERARCHY_GUIDE.md).

## When H3s Are Used: Intro Before First H3

When H3s are used, they need not sit directly under the H2. An **optional intro paragraph (or two)** between the H2 and the first H3 can create a smoother, more cohesive transition. Per Australian Style Manual: put a short introductory paragraph under each heading that expands the heading and summarizes the section's purpose.

- **Pattern:** H2 → optional intro paragraph(s) → H3 → content. The intro orients the reader and smooths the transition.
- **When:** Only when content benefits. Not every section needs it. Decide per section via manual review.
- **Anti-cheesy:** Avoid formulaic transitions ("Jetzt schauen wir uns... an", "right now we'll talk about...", "Im Folgenden..."). Intro should add context or summarize; not announce what follows.
- **Content-driven:** Structure is decided per piece via manual review. No rigid automation or templates.

## Entity Consistency

- **Stable terminology:** Use consistent entity names (Probezeit, Kündigungsfrist, etc.) across sections
- **Avoid contradictions:** Ensure factual consistency; AI systems extract with high confidence when terminology is stable

## Internal Linking

- **Semantic relationships:** Link to related topics; reflect topic clustering
- **Anchor text:** Natural, descriptive; avoid generic "hier klicken"

## Example: Natural Flow (Probezeit)

Sections like "Anteilige Berechnung" and "Urlaubsabgeltung bei Kündigung" as H2s with paragraphs directly below (no H3s) demonstrate natural flow. H2+paragraphs is valid when the section is short or flows linearly.

## Related Documentation

- [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md) – Section depth, H3 optional guidance
- [HEADING_HIERARCHY_GUIDE.md](HEADING_HIERARCHY_GUIDE.md) – When H2 stands alone
- [BLOG_CONTENT_RESTRUCTURING_GUIDE.md](BLOG_CONTENT_RESTRUCTURING_GUIDE.md) – When to use H3 vs expand
- [TOC_BEST_PRACTICES.md](TOC_BEST_PRACTICES.md) – Heading distribution
- [CONTENT_WRITING_BEST_PRACTICES_2026.md](../CONTENT_WRITING_BEST_PRACTICES_2026.md) – Human-first, AI optimization