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.

Why it matters

While HTML5 allows multiple H1s, in practice one clear primary heading helps Google and screen readers understand the page topic. Multiple H1s dilute the signal.

Schedule a fix in your next sprint. Warnings won't block your site but they consistently leave performance on the table. Estimated SEO impact: medium — measurable effect on click-through or relevance.

How to fix

• Keep one primary H1 that summarizes the page
• Demote other H1s to H2 or H3 based on their importance
• Check header/hero sections, sometimes both have <h1>

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.

Example

Here's a typical instance — the problematic line is highlighted in red:

<h1>First heading</h1>
<h1>Second heading</h1>

And the fix — the corrected line, highlighted in green:

<h1>Primary page heading</h1>
<h2>Subsection</h2>

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 multiple h1 tags on page 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

Related issues