The page has more than one h1
What this check looks for
This page uses ‹count› <h1> elements. HTML5 permits this and search engines handle it, so it is reported for you to consider rather than as a fault.
Why it matters
Several top-level headings can make a page harder to navigate by heading with a screen reader, because nothing in the structure says which one is the page's subject. Whether that matters depends on what the page is.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- SEO
- Module
- Seo audit
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
The <h1> elements found were:
‹headings›
**This deducts nothing, and the reason is that the old advice is no longer accurate.** The HTML5 outline algorithm that justified multiple <h1>s was never implemented by browsers or assistive technology and has been removed from the specification, but the specification still permits several <h1> elements and Google has stated it handles them without difficulty.
Where it is worth reconsidering: a page whose main content is a single article usually reads better with one <h1> for the article and <h2>s below it. Where it is fine: a genuine multi-section landing page, or a template that gives each of several equal panels its own heading.
The practical test is to navigate the page by heading with a screen reader. If the heading list identifies the page, the structure is working.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other seo audit checks
- The page declares more than one canonical URL
- The canonical URL cannot be used
- The page declares no canonical URL
- The canonical URL points at a different page
- The page has no h1 heading
- The heading levels skip a level
- An hreflang annotation is not valid
- The hreflang set does not include this page
- The page's declared language is not a well-formed language tag
- The page does not declare what language it is written in
- Images on the page have no alt attribute
- robots.txt blocks this page from being crawled