Free Header Tag Generator

WordPress

1. Open the post in Block Editor. Generate the outline here, copy it.
2. In WordPress, paste each heading into a Heading block, set the level (H1 already set by post title; use H2/H3 for the rest).
3. Use the document outline view (top-left of the editor) to verify the hierarchy renders correctly.

Webflow

1. Open the page in Designer. Generate the outline, then add each heading as a Heading element with the correct tag dropdown (H1, H2, H3).
2. For CMS-driven posts, define the heading structure in the Collection Page template once; the headings auto-render for every CMS item.
3. Run the published page through the H1, H2, H3 Heading Checker tool to confirm the outline renders cleanly.

Ghost

1. In the post editor, the post title is auto-H1 — do not add another # heading.
2. For body H2s, use a Header card and set level to H2. For H3 sub-points, use Header card with level H3.
3. Markdown shortcut: ## for H2, ### for H3. Avoid # in body content; that creates duplicate H1s.

Notion as CMS (Super, Potion, Feather)

1. Notion blocks render as semantic HTML in these CMS adapters. Use Notion's Heading 1/2/3 blocks; they render as <h1>/<h2>/<h3>.
2. Verify the rendered output: View Source on the live page and confirm your headings are real H tags, not divs.
3. If wrappers introduce extra divs, switch to a CMS adapter with cleaner HTML output.

Markdown / static site generators

1. Generate the outline, copy as Markdown. Each heading prefixed with # / ## / ### corresponds to H1 / H2 / H3.
2. Paste into your post file (Hugo, Jekyll, MDX, Astro, etc.). The static site generator converts to semantic HTML on build.
3. Avoid using only # for everything — the rendered HTML will have multiple H1s, breaking your outline.

Output has multiple H1 suggestions

Cause: AI returned alternative angle headlines, all rendered as H1.

Fix: Pick one H1 that matches your post. Demote the others to H2 (rejected angles) or delete entirely. Final published page should have exactly one H1.

Headings are too generic ("Introduction", "Conclusion")

Cause: Your input was generic ("blog post", "article", "guide").

Fix: Re-input with specifics. "Beginner guide to sourdough bread" produces specific H2s; "guide" produces "Introduction / What it is / Conclusion".

No H3s under H2 sections

Cause: AI defaulted to flat H1 -> H2 structure.

Fix: Prompt with "include H3 sub-sections" or manually add 2-3 H3s under each major H2 to break down complex topics. Long posts need this layer.

Headings are too long (15+ words)

Cause: AI tried to pack too much context into one heading.

Fix: Cut to 5-12 words. Move the rest into the section body. Long headings hurt scanability and depress click-through from internal navigation.

Keyword stuffed into every heading

Cause: AI overweighted the input keyword.

Fix: Edit so 2-3 H2s contain the keyword, the rest use entity-related terms. Stuffing every header is detected by Google and hurts ranking.

Output is poorly ordered

Cause: AI generated headings in topical groups but not narrative order.

Fix: Reorder so the post flows: hook, problem, framework, examples, objections, CTA. Re-arrange H2 blocks; keep H3s with their parent H2.

Headings do not match the page intent

Cause: You input a topic but the AI generated for the wrong commercial intent (informational vs. transactional).

Fix: Re-input with explicit intent: "informational blog post on X" vs. "comparison/transactional landing page for X". The framing changes the outline.

Outline has 20+ H2s for a 1,500-word post

Cause: AI generated more sections than the word count supports.

Fix: Cut to 5-8 H2s. Every section needs ~150-300 words to develop. Anything shorter is a bullet list inside another section, not its own H2.