Quick answer

Multiple H1 elements deserve a review, not an automatic rewrite. A page may use more than one H1 in a valid component system, but duplicate or competing primary headings often indicate a template mistake, hidden content, or unclear structure. Keep the page’s primary subject obvious and use lower-level headings for sections.

What the issue means

An H1 is a top-level heading in the HTML outline. NOTABIS reports multiple-h1 when the crawled document contains more than one H1 element. The rule counts elements; it does not understand whether one is visually hidden, inside a reusable component, or intentionally used for a separate region.

This makes the finding a structural review signal. The right question is not “How do I force the count to one?” but “What is the primary subject of this URL, and do the headings communicate it clearly?”

Why it matters for SEO

Headings help readers scan and help systems interpret page structure. Multiple H1s do not by themselves guarantee a ranking problem, and modern HTML can support more flexible heading structures than old SEO folklore suggests. The practical risk is ambiguity: a duplicated site header, modal heading, or component heading may compete with the actual page title.

Accessibility also matters. Screen-reader users often navigate by headings, so a predictable hierarchy makes long pages easier to understand.

How NOTABIS detects it

The multiple-h1 rule counts H1 elements in the delivered page HTML and records an issue when the count is greater than one. It does not score the wording, visual prominence, CSS visibility, or accessibility quality of the headings.

If a client-rendered site adds headings after the initial response, compare raw and rendered evidence before deciding whether the server output also needs improvement.

How to check it yourself

Inspect the DOM and search for h1. Then identify each result in the rendered page: is it the main page heading, a hidden template fragment, a dialog, a navigation component, or duplicate content? Check mobile layout too, because responsive components sometimes expose both desktop and mobile headings.

How to fix it

Keep one clear page-level H1 where that matches the page’s design, and change section headings to H2 or H3 according to their nesting. Remove duplicate template output rather than hiding a second copy with CSS. If a dialog or application view genuinely has its own context, ensure the heading structure remains understandable and test it with assistive technology.

Do not change headings without checking visual design, anchor links, CSS selectors, and automated tests.

Examples

Problematic template output:

<h1>Store</h1>
<h1>Red running shoes</h1>

A clearer hierarchy is:

<h1>Red running shoes</h1>
<h2>Specifications</h2>
<h2>Delivery information</h2>

When it is intentional or does not need fixing

Multiple H1 elements may be acceptable in some component or application architectures. A legitimate exception should still have a coherent accessible structure and no accidental duplicate content. Do not downgrade a finding solely because a tool expects one H1; inspect the page’s actual experience.

Related issues

Compare missing H1 tags, missing main landmarks, and duplicate content.

Run a NOTABIS audit

NOTABIS can identify URLs with multiple H1 elements so you can review shared templates and distinguish genuine structure problems from intentional component patterns.