Skip to content
Content High severity By Lewis Jones

Missing or Multiple H1 Tags: Why It Matters

A page with zero H1s, or several competing ones. Why exactly one H1 matters for search engines, an example finding, and how to fix it.

A page's H1 is its main title, on the page and for a search engine working out what to call it in results. A page with none, or with several competing ones, leaves that judgement to guesswork.

Are multiple H1 tags bad for SEO?

Not as a penalty. Google does not punish a page for having two H1s, HTML5 allows more than one, and Google's own SEO starter guide says "there's also no magical, ideal amount of headings a given page should have". The cost is ambiguity, not a rule broken. Google builds the title link it shows in results from several sources, and its title link documentation lists "heading elements, such as <h1> elements" among them. The same page recommends putting your title text "in the first visible <h1> element on the page" and making the main title stand out as the most prominent text. Three H1s give it three candidates for that job. So the practical answer to "how many H1 tags per page?" is one: it costs nothing, it removes the guesswork, and screen reader users, who often jump to the H1 to find out what a page is about, land on the right heading.

What this finding means

Crawl Cove's heading-h1 check counts the H1 elements on every indexable HTML page and flags anything other than exactly one. Non-HTML resources (a sitemap, robots.txt, a feed) have no heading outline and are never flagged.

A real finding looks like this:

H1 count is 0 (expected 1)

or, just as commonly on pages built from stacked content blocks:

H1 count is 3 (expected 1)

One finding per page, naming the actual count found. The severity depends on which fault it is. A page with no H1 is rated high. A page with several H1s is rated low, because Google has said several H1s are not a problem and stock themes produce them on every page, and the finding's advice reads "this is a tidy-up, not a fix". (Before v1.3.14 both cases were rated high.)

Why it matters

The H1 is the page's main visible title, and it is one of the places Google looks when it decides what to call the page in search results. A missing H1 leaves that to the title tag, other large text and the copy around it. Several H1s offer competing titles, and Google has to pick one, which is not guaranteed to be the one you meant. A rewritten title link that names the wrong subject is usually the visible symptom. This check was deliberately separated from the related heading-order check (a skipped heading level, such as H2 straight to H4): an earlier, combined version of both faults fired as a single high-severity finding on 83% of real pages, which meant a first audit ranked almost nothing as more urgent than anything else. Splitting them keeps this one, the fault with a real topical-signal cost, at the severity it deserves.

How to fix it

  1. If the page has zero H1s, add one that states the page's actual subject, close to the top of the content.
  2. If the page has several H1s, decide which one genuinely names the page, keep that as the H1, and demote the rest to H2 (or lower, depending on where they sit in the outline).
  3. Check page builders and theme templates. Multiple H1s often come from a template that gives every content block (a hero section, a widget, a repeated component) its own H1 by default, rather than from anything written into the page's actual copy.
  4. Re-crawl the page to confirm exactly one H1 remains and the finding clears.

False positives and edge cases

  • Non-HTML resources are never flagged. A sitemap, robots.txt file or RSS feed has no heading outline, so this check does not run against them at all.
  • A single, weak H1 still passes. This check counts H1s; it does not judge whether the one H1 present is well written. A page with exactly one but unhelpfully generic H1 (say, just "Home") passes this check even though the copy itself is still worth improving.
  • An H1 added by JavaScript is not missing. Since v1.3.16 the check allows for this. Some sites send HTML with no H1 and add it in the browser. When the crawl's JavaScript sample shows that pattern, a page with no H1 in its HTML is rated low and the finding says how many sampled pages gained an H1 in a browser. Google runs JavaScript and will usually see the heading; other crawlers and AI tools that read only the HTML will not. On one tourism site we crawled, 1,918 of 2,600 pages had no H1 in the HTML, and 38 of 40 sampled pages had one once a browser ran the page.
  • A visually hidden H1 still counts. If a theme includes an H1 for accessibility or SEO purposes but hides it visually (a common pattern for a logo-based header), it is still read from the markup and counts toward the total either way.

Related reading

For the related check that flags a skipped heading level rather than an H1 count problem, a readability and assistive-technology issue rather than a topical-signal one, see Skipped Heading Levels: Why Order Matters. For how the H1 fits the rest of a page's heading outline, with counts of H1 faults across 27 real sites, see heading tags for SEO.

Google documentation: Influencing title links in Google Search

Frequently asked questions

How many H1 tags should a page have?
One. Google's starter guide says there is no ideal number of headings overall, and two H1s will not get a page penalised, but a single H1 that names the page gives Google one clear candidate when it builds the title link, and gives screen reader users one heading that says what the page is.
Is having two H1 tags actually a Google penalty?
No, it is not a penalty, and modern HTML5 technically allows more than one H1 within separate sections. The problem is practical rather than a rule being broken: when a page states several different subjects at its highest heading level, a search engine has to guess which one the page is actually about, and it can guess wrong.
Why is this check High severity when heading-order (skipped levels) is Low?
The H1 is a topical-signal problem: get it wrong and a search engine may misjudge what the whole page is about. A skipped heading level (say H2 straight to H4) is a readability and assistive-technology problem, real but narrower in scope, which is why the two were split into separate checks with different severities rather than one finding covering both.
What if my homepage's H1 is my logo or tagline, not a real heading?
That still counts as the page's H1 for this check; the fault it flags is the count (zero or more than one), not whether the single H1 present is well written. A weak but singular H1 passes this check, even though better copy is still worth doing separately.
Does this check run on every page type?
It runs on every HTML page Crawl Cove indexes, but skips non-HTML resources like a sitemap.xml, robots.txt, or an RSS feed, since those have no heading outline to evaluate in the first place.

Audit your site the easy way

Crawl Cove finds this on your machine, on every paid plan. Try the On-Page SEO Checker or see every feature.

Download Crawl Cove