Fix heading hierarchy
Headings should nest H1 → H2 → H3. Skipping levels makes the outline harder to scan and extract. Follow the steps below on your stack, then re-check the live URL.
Headings should nest H1 → H2 → H3. Skipping levels makes the outline harder to scan and extract.
We remember this on this browser so the next guide opens with the same CMS.
At a glance
| Time | ~15 min |
|---|---|
| Category | SEO |
| Steps | 3 |
| Stacks | WordPress, Shopify, Webflow, Next.js, HTML, more |
Steps
Map the current heading outline in page source.
Don’t skip levels (for example H2 → H4). Insert the missing H2/H3 or retag the heading.
Make headings describe the section — avoid empty or icon-only headings.
In HTML / static
Keep a single <h1> and a logical h2→h3 outline.
Snippet
<h1>Page topic</h1> <h2>Section</h2> <h3>Sub-section</h3>
FAQ
- What does “Fix heading hierarchy” fix?
- Headings should nest H1 → H2 → H3. Skipping levels makes the outline harder to scan and extract.
- How long does this usually take?
- About 15 minutes on most CMS and code stacks when you already have access to edit the page.
- Where do I start?
- Start with: Map the current heading outline in page source. Then use the platform picker on this page for placement notes.