# Blog Content Restructuring Guide

**Last Updated:** 2026-02-11

Guide for when and how to restructure blog posts (vs. simply expanding them), add H3 subheadings, introduce new sections, and expand keywords during content refresh.

## Overview

Blog workflows often emphasize **expanding existing sections**. This guide ensures we also consider:

- **Restructuring** (reorganizing, merging, splitting sections)
- **Adding H3 subheadings** for long content (per [TOC_BEST_PRACTICES.md](TOC_BEST_PRACTICES.md))
- **Adding new sections** to cover competitor gaps and related keywords
- **Re-running keyword research** during content refresh

## Restructure vs. Expand Decision Matrix

### When to Restructure

| Condition | Action |
|-----------|--------|
| Long sections with distinct subtopics (posts >2,500 words) | Consider H3s where sections benefit; H2+paragraphs is valid for many sections |
| Disorganized flow | Reorder sections; regroup related topics |
| Competitor structure differs significantly | Assess competitor H2/H3 structure; adapt where it improves coverage |
| TOC has >15 items with no H3s | Consider H3s for scannability; TOC auto-groups when >15 items |

### When to Expand

| Condition | Action |
|-----------|--------|
| Thin sections (single paragraph, no list/table) | Add 2+ paragraphs or 1 para + list/table per [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md) |
| Content gaps vs. competitors | Add paragraphs or new H3s to cover missing topics |
| PAA questions not answered | Add new content (H2, H3, or paragraph) to address them |
| Word count below target | Expand sections substantively (not filler) |

### When H2+Paragraphs Is Enough

- **Short sections:** Section is brief; paragraphs alone flow well
- **Linear narrative:** Content moves in a straight line; no distinct subtopics
- **Single-topic sections:** One clear idea; H3 would feel forced

### When to Add New Sections

| Condition | Action |
|-----------|--------|
| Competitor covers topic we don't | Add H2 or H3 to cover gap |
| PAA/GSC query matches distinct topic | Add H2 or H3 with answer |
| Related keyword warrants dedicated section | Add H2 or H3; integrate keyword naturally |
| Content gap in competitive-depth-analysis | Add section per recommendation |

## H3 Subsection Standards

H3s are **optional and case-by-case**. Use only when they add clarity. H2+paragraphs is valid for many sections.

### When to Use H3s

- **Distinct subtopics:** E.g. "Rechtliche Grundlage (§ 622 BGB)" under "Was ist die Probezeit?"
- **Step-by-step:** E.g. "Schritt 1: Schriftlich vereinbaren" under "Kann die Probezeit verlängert werden?"
- **Tips/checklists:** Use H3 per tip only if each tip has 2+ sentences; otherwise use `<ul>` with bold lead-in per item (see List vs H3 in [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md))
- **Comparisons:** E.g. "Einfaches vs. qualifiziertes Zeugnis" under "Arbeitszeugnis"

### When to Avoid H3s (Prominent)

- **Short posts (<1,000 words):** Flat H2-only is fine
- **Short or simple sections:** H2+paragraphs flows better; no subdivision needed
- **Forced structure:** Don't add H3s that don't improve flow or scannability—headings support the reader, not decorate the page
- **Over-nesting:** If H2 has >5 H3s, consider splitting H2 into multiple H2s

### When to Use List Instead of H3

- **4+ consecutive brief items** – Per Semji: "replace titles by bullet lists if more than 4 consecutive elements"
- **Each item 1-2 sentences** – Use `<ul>` with bold lead-in per item instead of thin H3s
- **Table or summary already provides structure** – List with brief definitions avoids redundant H3 hierarchy

### Intro Before H3

When using H3s, consider an intro paragraph between H2 and first H3 if it improves flow. Content-driven—not mandatory. Avoid formulaic "coming up next" transitions.

## Adding New Sections

### Criteria

1. **Competitor coverage:** Topic appears in top 10 competitor H2/H3 headings
2. **PAA alignment:** Question matches a PAA or GSC query
3. **Related keyword:** Term has search volume and fits post topic
4. **Content gap:** Listed in `data/competitive-depth-analysis.md`

### Identification Sources

- **SERP_ANALYSIS.md:** PAA table, competitor headings, recommendations
- **competitive-depth-analysis.md:** Content gaps, format recommendations (in `data/` subdir)
- **collect-post-keywords-sistrix.php:** Related keywords
- **collect-faq-research-data.php:** PAA, GSC queries
- **Manual SERP research:** Related Searches, competitor H3 structures

### Workflow

1. Run `php v2/scripts/blog/collect-post-competitor-analysis.php --post={slug} --category={category}`
2. Run `php v2/scripts/blog/analyze-competitor-content-depth.php` (generates content gaps)
3. Review SERP_ANALYSIS.md, competitive-depth-analysis.md
4. Update CONTENT_OUTLINE.md with new H2/H3 sections
5. Run `validate-content-outline-quality.php` before content creation

## Keyword/Topic Expansion Workflow

### Scripts to Re-run During Refresh

```bash
php v2/scripts/blog/collect-post-keywords-sistrix.php --post={slug} --category={category}
php v2/scripts/blog/collect-faq-research-data.php --post={slug} --category={category}
```

### Sources for Related Terms

- **SISTRIX:** `keywords-sistrix.json` (related keywords)
- **faq-research.json:** `paa_questions`, `gsc_top_queries`
- **Web research:** Related Searches on Google, competitor headings
- **SERP_ANALYSIS.md:** Add "Related Keywords" section from manual review

### Integration

- Integrate related keywords naturally (don't stuff)
- Prefer first paragraph of section or H2/H3 heading when it fits
- Add to `meta.keywords` if not already present

## Validation

### Content Structure Audit

Run to flag posts needing H3s:

```bash
python3 v2/scripts/blog/audit-content-structure.py
```

Flags (informational; H2+paragraphs may be appropriate):

- `word_count >2,000` and `h3_count = 0` → "Consider reviewing structure"
- `word_count >2,500` and `h3_count < 10` → "Below typical range; add H3s only if sections would benefit"

### TOC Analysis

```bash
python3 v2/scripts/blog/analyze-toc-structure.py
```

Shows H2/H3 counts, total TOC items, grouping status.

### Outline Validation

```bash
php v2/scripts/blog/validate-content-outline-quality.php --post={slug} --category={category}
```

Optional: Script can warn if target word count >2,500 and outline has 0 H3s.

## Related Documentation

- [TOC_BEST_PRACTICES.md](TOC_BEST_PRACTICES.md) – Heading distribution, grouping
- [CONTENT_DEPTH_GUIDELINES.md](CONTENT_DEPTH_GUIDELINES.md) – Section depth, H3 optional guidance
- [HEADING_HIERARCHY_GUIDE.md](HEADING_HIERARCHY_GUIDE.md) – Hierarchy rules
- [SKYSCRAPER_TECHNIQUE_2026.md](SKYSCRAPER_TECHNIQUE_2026.md) – Competitive analysis
- [BLOG_POST_IMPROVEMENT_PROCESS.md](BLOG_POST_IMPROVEMENT_PROCESS.md) – Full rework workflow