Skipped Heading Level
Jumping from H2 to H4 (skipping H3) breaks the accessibility tree — screen readers announce a level that does not exist in the outline.
Why it matters
Jumping from H2 to H4 (skipping H3) breaks the accessibility tree — screen readers announce a level that does not exist in the outline.
Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: medium — measurable effect on click-through or relevance.
How to fix
- Demote the H4 to H3 to close the gap
- Or add an H3 section between the H2 and the H4
- Use the browser DevTools "Accessibility Tree" to verify the outline
Common causes
If the rule is firing across many pages, the root cause is almost always one of these:
- Editorial team copy-pastes from another page and brings its heading levels with it.
- Theme uses headings for visual styling rather than document structure.
- WYSIWYG editor inserts new headings at whichever level the cursor was last on.
- Multi-author pages stitch sections together without a single owner of the outline.
Anti-patterns to avoid
Even with the best intentions, these "fixes" make the issue worse — recognise them so you don't ship them:
- Skipping levels (
<h1>directly to<h4>) for visual styling. - Multiple
<h1>s on one page because each section "felt like a top heading". - Using headings as decorative dividers without semantic content.
How atlookup detects this
Our crawler renders each page with a real headless browser, then walks the heading tree and checks for missing levels, duplicates, and skipped depths. Pages where the rule fires for skipped heading level are flagged on the report.
If you'd like to see this rule fire on your own site, run a free 60-second audit — every page is reported with the exact lines that triggered it.
Tools to verify the fix
Once you've applied the fix, double-check with these external validators:
- axe DevTools — Flags heading-order violations (a11y + SEO).
- HeadingsMap — Browser extension that visualises the heading tree.
Frequently asked questions
Why does Skipped Heading Level matter for SEO?
Jumping from H2 to H4 (skipping H3) breaks the accessibility tree — screen readers announce a level that does not exist in the outline.
How do I fix skipped heading level?
Demote the H4 to H3 to close the gap Or add an H3 section between the H2 and the H4 Use the browser DevTools "Accessibility Tree" to verify the outline
Is this a critical SEO issue?
Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: medium — measurable effect on click-through or relevance.
How does atlookup detect skipped heading level?
Our crawler renders each page with a real headless browser, then walks the heading tree and checks for missing levels, duplicates, and skipped depths. Pages where the rule fires for skipped heading level are flagged on the report.
Does this affect accessibility?
Yes. This issue maps to WCAG 1.3.1 (Level A). Fixing it improves both SEO ranking signals and the experience for users on assistive technology.
Related issues
H1_MISSING
Missing H1 Tag
The H1 is the main on-page heading — a crucial signal for Google and screen-reader users.
HEADING_EMPTY
Empty Heading Tag
An <h1>-<h6> with no text is invisible to screen readers and Google.
H1_MULTIPLE
Multiple H1 Tags on Page
While HTML5 allows multiple H1s, in practice one clear primary heading helps Google and screen readers understand the page topic.
HEADING_HIERARCHY_BROKEN
Broken Heading Hierarchy
Heading levels should descend logically (H1 → H2 → H3), not skip levels.