Start here
Before You Fix It: What This Check Means
Heading hierarchy is a content-outline signal that helps both readers and parsers navigate long pages. In plain terms, this checks whether the page headings form a clear outline instead of jumping around. Scavo reads all heading tags (`H1` to `H6`) in document order and evaluates structure.
Why this matters in practice: incorrect signals here can dilute indexing clarity and search traffic quality.
How to use this result: treat this as directional evidence, not final truth. Search indexing outcomes depend on crawler recrawl cadence and ranking systems outside your direct control. First, confirm the issue in live output: verify raw HTML output and crawler-facing validators Then ship one controlled change: Keep one H1 as page title. Finally, re-scan the same URL to confirm the result improves.
TL;DR: Headings skip levels (H1 → H3) or are out of order, making content harder for screen readers and search engines to parse.
88.8% of screen reader users find heading levels very or somewhat useful for page navigation (WebAIM Survey #10, 2024). When headings skip levels or are out of order, screen reader users can't build a mental map of your content structure. Search engines also use heading hierarchy to understand content relationships and assign keyword relevance.
What Scavo checks (plain English)
Scavo reads all heading tags (H1 to H6) in document order and evaluates structure.
Exact logic:
Fail: no H1 found.Warning: more than one H1 found.Info: one H1 exists but no H2 headings are present.Warning: heading hierarchy skips levels (for example H1 to H3).Pass: one H1, at least one H2, and no hierarchy gaps.
Scavo records heading counts by level and detected hierarchy gaps.
How Scavo scores this check
Scavo assigns one result state for this check on the tested page:
- Pass: baseline signals for this check were found.
- Warning: partial coverage or risk signals were found and should be reviewed.
- Fail: required signals were missing or risky behavior was confirmed.
- Info: Scavo could not gather enough reliable evidence on this run to score pass/fail confidently.
In your scan report, this appears under What failed / What needs attention / What is working for heading_structure, followed by Recommended next steps and Technical evidence (for developers) when needed.
- Scan key:
heading_structure - Category:
SEO
Why fixing this matters
A logical heading outline makes long pages easier to read and improves navigation for assistive technologies. It also gives clearer section signals to crawlers.
Common reasons this check flags
- Design system uses heading tags for visual size only.
- Content editors skip directly from H2 to H4.
- Reusable modules inject extra H1s.
- Short landing pages use paragraphs instead of H2 section breaks.
If you are not technical
- Ask your team to produce a simple heading outline for the page.
- Confirm there is one main heading and clear subsection headings.
- Ask for before/after source proof.
- Re-run scan and verify status changed.
Technical handoff message
Copy and share this with your developer.
Scavo flagged Heading structure (heading_structure). Please ensure this URL has exactly one H1, add H2 section headings where appropriate, and remove skipped heading levels (for example H1→H3). Share source proof and re-run the scan.If you are technical
- Keep one H1 as page title.
- Use H2 for major sections, H3 under related H2 blocks.
- Avoid jumps like H2→H4 unless structure genuinely justifies it.
- Move visual styling into CSS classes, not heading-level misuse.
Good outline example
<h1>Scavo Pricing</h1>
<h2>Plans</h2>
<h3>Solo</h3>
<h3>Agency</h3>
<h2>FAQ</h2>How to verify
- Use browser accessibility tooling or heading map extension.
- Confirm no level jumps in main content sequence.
- Validate representative page templates, not one URL only.
- Re-run Scavo and confirm expected status.
What this scan cannot confirm
- It does not score heading copy quality.
- It does not verify whether every section is semantically perfect.
- It does not evaluate ARIA landmarks or full accessibility compliance.
Owner checklist
- [ ] Define heading hierarchy standards in editorial guidelines.
- [ ] Add block/editor constraints that prevent heading jumps.
- [ ] Include heading outline review in pre-publish QA.
- [ ] Re-check after major component or markdown renderer changes.
FAQ
Why does Scavo return Info when no H2 exists?
Because some pages can be valid with minimal structure, but adding H2s usually improves readability and section clarity.
Are heading level jumps always wrong?
Not always, but repeated jumps are usually a structure smell. This check warns so teams can review intentionally.
Can multiple H1s ever be acceptable?
Possible in some HTML5 patterns, but operationally many teams use one H1 for clarity. This check warns on multiple H1s.
Does this replace an accessibility audit?
No. It is a focused structural signal, not full accessibility verification.
Sources
- Google Search Central: SEO starter guide
- MDN: HTML heading elements
- W3C WAI tutorial: Page structure and headings
Need help creating a heading standard your content team can follow? Send support one long-form page and your preferred outline style.
