A page's H1 is the single strongest statement of what it is about, on the page and to a search engine, and a page that has none, or several competing ones, leaves that judgement to guesswork.
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.
Why it matters
The H1 is the clearest topical signal on the page, ranked above body text and sub-headings in how strongly it tells a search engine what the page is trying to answer. A missing H1 leaves that job to weaker signals like the title tag or the first paragraph. Several H1s split the same signal across competing subjects, and a search engine has to pick one, which is not guaranteed to be the one you meant. 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
- If the page has zero H1s, add one that states the page's actual subject, close to the top of the content.
- 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).
- 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.
- 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.txtfile 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.
- 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.
Frequently asked questions
- 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.