Heading levels skip a level
76 audited sites hit the "Heading levels skip a level" issue; this hub breaks it down by platform, gatekeeper, vertical and country.
What it means
Heading levels skip a level when a page jumps from, say, an h2 to an h4 without an intervening h3, or when a styled div is used as a heading instead of a real heading element. This breaks the expected h1 through h6 hierarchy on the page.
Why it matters
Skipped heading levels distort the semantic tree that Googlebot and screen readers both consume. Since headings are explicit topic and structure signals, gaps make it harder for the crawler to infer content priority and for AI extractors to identify the correct heading hierarchy. The issue also affects snippet eligibility and internal linking context.
How to fix it
- Replace styled divs or spans with real heading elements (h1–h6) in the HTML source.
- Ensure each heading level is used in order without gaps: h1, h2, h3, etc.
- Use CSS to control visual size and weight independently of the semantic level.
- Verify with axe DevTools or Lighthouse that headings report no skipped levels.
When it's not a problem
This is a false alarm when the visual style suggests a skip but the actual HTML uses the correct heading element in sequence. It's also fine if the design intentionally uses a larger font for an h4 but the markup is correct.
How common is it?
76 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.
Audit your own site — free
77 checks, internal PageRank, render-diff. No signup, results in ~30s.