
Headings are the skeleton of every web page. They tell search engines what your content is about, guide screen reader users through your page, and help sighted visitors scan for the information they need. Yet heading hierarchy remains one of the most consistently broken elements across the web.
A 2025 WebAIM analysis of one million homepages found that 42.1% had skipped heading levels and 10.6% had no H1 tag at all. Meanwhile, Google's own documentation confirms that heading structure is a ranking signal — not a major one in isolation, but a compounding factor that affects crawl understanding, featured snippet eligibility, and passage ranking.
If you care about either SEO or accessibility — and you should care about both — heading hierarchy deserves your attention. This guide covers why it matters, what goes wrong, how to audit your structure, and what proper implementation looks like in practice.
Why Heading Hierarchy Matters for SEO
Search engines use headings to understand page structure and topic relevance. When Googlebot crawls a page, it assigns weight to heading content as a signal of what sections cover. Here is how heading hierarchy directly affects your search performance:
- Crawl understanding: Google uses headings to segment content into passages. Since the 2021 Passage Ranking update, individual sections of a page can rank independently for specific queries — but only if those sections are clearly delineated by headings.
- Featured snippets: Ahrefs data shows that 70% of featured snippets are pulled from content under H2 or H3 tags. If your headings don't match search intent phrasing, you lose snippet eligibility.
- Keyword signals: Heading text carries more weight than body text for relevance scoring. An H2 containing your target keyword tells Google "this section is about X" far more effectively than the same keyword buried in a paragraph.
- Content hierarchy signals: Proper nesting (H1 → H2 → H3) communicates topic-subtopic relationships. This helps Google build a topical map of your content, improving rankings for long-tail variations.
A Semrush study of 100,000 pages found that pages with well-structured heading hierarchies ranked an average of 3.2 positions higher for their target keywords than pages with broken or missing structure. That gap widens for competitive queries where Google uses every available signal to differentiate.
Why Heading Hierarchy Matters for Accessibility
For the 2.2 billion people globally with vision impairments (WHO, 2024), screen readers are the primary interface to the web. And screen readers rely heavily on heading structure for navigation.
How Screen Readers Use Headings
Screen reader users navigate by headings the way sighted users scan visually. The most common navigation method is pressing the "H" key to jump between headings. In the WebAIM Screen Reader User Survey (2024):
- 67.5% of screen reader users navigate by headings as their primary content discovery method
- 86.1% find heading levels "very useful" or "somewhat useful" for understanding page structure
- Users report that skipped heading levels are the #3 most frustrating accessibility issue, behind missing alt text and poor form labels
When headings jump from H2 to H4, a screen reader user cannot tell whether they missed a subsection or whether the developer simply chose H4 for styling reasons. This ambiguity forces users to backtrack, re-read, or abandon the page entirely. Use the Heurilens heading hierarchy checker to instantly identify these gaps on any URL.
WCAG Requirements
WCAG 2.2 addresses headings in multiple success criteria:
- 1.3.1 Info and Relationships (Level A): Headings must be programmatically determined — visual styling alone is insufficient
- 2.4.1 Bypass Blocks (Level A): Headings serve as landmarks for bypassing repeated content
- 2.4.6 Headings and Labels (Level AA): Headings must describe the topic or purpose of the content
- 2.4.10 Section Headings (Level AAA): Content should be organized with section headings
Meeting these criteria is not optional for organizations subject to ADA, Section 508, or the European Accessibility Act (effective June 2025). A heuristic analysis covers heading structure as part of the "consistency and standards" and "recognition rather than recall" heuristics.
The 7 Most Common Heading Mistakes
After analyzing thousands of pages through our heading hierarchy tool, these are the mistakes we see most frequently — ranked by prevalence and impact.
1. Multiple H1 Tags
HTML5 technically allows multiple H1s within sectioning elements, but in practice, Google's John Mueller has recommended using a single H1 per page. Multiple H1s dilute your primary topic signal and confuse screen readers about the page's main subject.
Prevalence: 19.4% of pages (WebAIM Million, 2025)
Impact: Medium for SEO, high for accessibility
Fix: One descriptive H1 per page. Use H2 for major sections.
2. Skipped Heading Levels
Jumping from H2 to H4, or H1 to H3, breaks the logical outline. This is the most damaging structural error because it affects both machine parsing and human comprehension.
Prevalence: 42.1% of pages
Impact: High for both SEO and accessibility
Fix: Never skip levels. H2 sections contain H3 subsections, which contain H4 sub-subsections.
3. Decorative Headings (Styling Abuse)
Using heading tags purely for visual size — an H3 in the footer because it "looks right," or an H2 for a sidebar widget title that has no semantic relationship to the main content.
Prevalence: Estimated 30-40% of pages
Impact: Medium for SEO (noise in topic signals), high for accessibility
Fix: Use CSS classes for visual styling. Reserve heading tags for content structure.
4. Missing H1 Tag
Pages without any H1 tag leave search engines guessing about the primary topic. Some CMS themes hide the H1 or replace it with a logo image without alt text.
Prevalence: 10.6% of pages
Impact: High for SEO
Fix: Every page needs exactly one H1 that describes the page's primary content.
5. Headings That Don't Describe Content
Generic headings like "Overview," "Details," or "More Information" waste keyword opportunities and provide no navigational value to screen reader users.
Impact: Medium for SEO, medium for accessibility
Fix: Headings should be descriptive enough to stand alone. "Pricing Plans for Small Teams" beats "Pricing."
6. Hidden Headings (display:none)
Some developers add headings for accessibility but hide them with display:none or visibility:hidden. Screen readers skip these entirely, making them useless. Google may also ignore or devalue hidden content.
Fix: Use the .sr-only (screen-reader-only) CSS pattern if you need visually hidden headings that remain accessible.
7. Heading-Level Inflation
Using only H2 and H3 for the entire page, creating a flat structure with no depth. This is common on landing pages and single-page sites.
Fix: Even landing pages benefit from proper nesting. If a section has subsections, use the next heading level down.
How to Audit Your Heading Hierarchy
A heading audit is one of the fastest, highest-impact checks you can perform. Here is a systematic approach:
Step 1: Extract the Heading Outline
Run your URL through the Heurilens heading hierarchy checker. It extracts every heading tag, displays the nesting structure, and flags violations including skipped levels, multiple H1s, and empty headings.
Step 2: Evaluate the Outline in Isolation
Read just the headings as a list. Ask yourself:
- Does this outline make sense without the body text?
- Could a reader understand the page's structure from headings alone?
- Does each heading accurately describe the content that follows?
- Are target keywords represented naturally (not stuffed)?
Step 3: Check for Structural Violations
- Exactly one H1? ✓
- No skipped levels? ✓
- No decorative headings (headings used purely for styling)? ✓
- No empty or whitespace-only headings? ✓
- No hidden headings using
display:none? ✓
Step 4: Cross-Reference with Search Intent
Compare your H2s against the "People Also Ask" questions for your target keyword. If there is a common question your headings don't address, you have a content gap. If your H2 phrasing doesn't match how people search, you may miss featured snippet opportunities.
Step 5: Test with a Screen Reader
On macOS, activate VoiceOver (Cmd + F5) and press VO + U to open the rotor, then navigate to the Headings list. On Windows, NVDA (free) offers similar heading navigation. Experiencing your page as a screen reader user reveals structural issues that no automated tool catches.
For a comprehensive approach that goes beyond headings, our 50-point UX audit checklist covers heading hierarchy alongside color contrast, touch targets, and other critical elements.
Heading Hierarchy and Core Web Vitals
Heading structure does not directly affect LCP, INP, or CLS scores. However, the relationship is indirect but meaningful:
- CLS (Cumulative Layout Shift): Improperly sized heading fonts that load via web fonts can cause layout shifts. Define explicit
font-sizeandline-heightfor all heading levels to prevent CLS from font swapping. - Render performance: Deeply nested heading structures with complex CSS selectors (e.g.,
article > section > h3 + p) can marginally increase render time on pages with hundreds of headings. - Content indexing speed: Pages with clean heading structure are parsed faster by Googlebot, leading to quicker indexing of new or updated content.
The real connection is that pages with good heading structure tend to have good overall technical hygiene. Teams that care about heading hierarchy typically also care about color contrast, semantic HTML, and performance — all signals that compound for SEO. Developer teams benefit most from integrating heading checks into their CI/CD pipeline.
Implementation Best Practices
Here is a practical reference for implementing heading hierarchy correctly across common scenarios.
Standard Content Page
- H1: Page title (one per page, matches
<title>tag closely) - H2: Major sections (3-8 per page is typical)
- H3: Subsections within an H2 section
- H4-H6: Deeper nesting (rare on most pages; use sparingly)
E-Commerce Product Page
- H1: Product name
- H2: "Description," "Specifications," "Reviews," "Related Products"
- H3: Individual review titles, specification categories
SaaS Landing Page
- H1: Primary value proposition
- H2: "Features," "How It Works," "Pricing," "Testimonials," "FAQ"
- H3: Individual feature names, FAQ questions
Blog Post
- H1: Article title
- H2: Major sections (these are your featured snippet candidates)
- H3: Subsections, individual list items that need expansion
CSS Separation Principle
The most important rule: never choose a heading level for its default size. Define heading styles independently:
- Use utility classes like
.text-xl,.text-2xlfor visual sizing - Use heading tags (
<h1>through<h6>) strictly for semantic structure - If a sidebar widget title looks like an H3 but is semantically unrelated to the H2 above it, use a
<p>or<div>with heading-like styling instead
Heading Hierarchy Checklist
Use this quick-reference checklist for every page you publish or audit:
- ☐ Exactly one H1 per page
- ☐ H1 contains the primary target keyword naturally
- ☐ No heading levels are skipped (H1 → H2 → H3, never H1 → H3)
- ☐ All headings describe the content that follows them
- ☐ No headings are used purely for visual styling
- ☐ No empty or whitespace-only headings
- ☐ No headings hidden with
display:none - ☐ Heading text is unique (no duplicate H2s on the same page)
- ☐ Key H2s align with "People Also Ask" queries for the target keyword
- ☐ Heading fonts have explicit sizes to prevent CLS
Start Auditing Your Heading Structure Today
Heading hierarchy is one of those rare optimizations that improves SEO, accessibility, and user experience simultaneously. It costs nothing to fix, requires no design changes, and compounds with every other technical optimization you make.
Run your first heading audit with the Heurilens heading hierarchy checker — it takes under 30 seconds to see your complete heading outline with flagged violations. For a full-page analysis that covers headings alongside contrast, heuristics, and more, try Heurilens or explore our plans to find the right fit for your team.
Was this article helpful?






