Multiple H1 Tags: Does It Hurt SEO?

TL;DR — Having more than one <h1> tag on a page does not hurt your Google rankings. Google has said this plainly and repeatedly. It’s a myth that a page needs exactly one H1An H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about.. The one thing worth knowing: multiple H1s can make a page slightly harder for screen-reader users to navigate, so one clear main heading is still a good default — just not for the reason most people think.

Evidence for this claim Google's current guidance treats semantic heading order as useful for screen readers but not something that materially changes Google Search behavior. Scope: Current Google SEO Starter Guide; does not establish that every multiple-H1 pattern is ideal HTML. Confidence: high · Verified: 2026-07-14 Google Search Central: SEO Starter Guide Evidence for this claim A page without a single clear first-level heading can be harder for assistive-technology users to navigate. Scope: Accessibility and document organization, not a Google penalty claim. Confidence: high · Verified: 2026-07-14 MDN: Heading elements — Accessibility

What “multiple H1 tags” means

An <h1> is the HTML tag for the main heading of a page. “Multiple H1 tagsWhen a single web page contains more than one <h1> element. The HTML standard permits non-nested sibling h1s, and Google treats multiple h1s as a low-priority ranking concern — but nested h1 patterns are non-conforming, and one clear h1 is still the accessibility default.” just means a page has more than one of them. The classic example: a website template wraps the logo in the header in an <h1>, and then also wraps the article’s actual title in a second <h1>. Now you’ve got two — usually without anyone deciding that on purpose.

If you want the basics of what an H1 is and how it fits under H2s and H3s, the H1 tagAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. article covers that. This page is about one specific question people panic over: does having two (or more) H1s hurt my SEO?

The short answer: no

You’ve probably run an audit tool — Screaming Frog, Ahrefs Site Audit, Semrush, LighthouseLighthouse is Google's free, open-source tool that audits a page under simulated lab conditions and scores it 0–100 across Performance, Accessibility, Best Practices, and SEO. It's lab data — useful for debugging, not a ranking signal. — and it flagged “multiple H1 tags foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore..” That warning makes it sound like a problem. For Google rankings, it isn’t.

Google’s John Mueller has said a page will “rank perfectly fine with no H1 tags or with five H1 tags,” and that when tools flag multiple H1s, “from our point of view that’s not a critical issue.” That’s about as clear as Google gets.

So why does my tool flag it?

Because it’s a low-priority tidiness and usability suggestion, not a ranking penalty. Most tools — including Ahrefs’ own Site Audit — flag it at low severity for exactly that reason. It’s the audit-tool equivalent of “you might want to look at this,” not “this is hurting you.”

The one real reason to still care

It’s not Google. It’s people who use screen readers. A screen reader treats every <h1> on a page as an equally important top-level heading. So if a page has five H1s, a screen-reader user navigating by heading hears five “main” headings and has to guess which one is really the page’s topic. That’s a genuine (if minor) usability issue — separate from SEO.

So the practical takeaway:

• Don’t panic when a tool flags multiple H1s. It’s not a ranking problem.
• One clear H1 per page is still a nice default — mostly for accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. and tidiness.
• If a template adds a stray second H1 (like a logo H1), it’s a low-priority, easy cleanup, not an emergency.

Want the full version — the exact Google quotes with dates, what HTML5 actually changed, why the spec changed again in 2022, and how to tell a harmless duplicate from something worth fixing? Switch to the Advanced tab.

Inventory every H1 and its context

Run this in DevTools Console on the rendered page. It lists each H1An H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about., its text, whether another H1 contains it, and the nearest sectioning ancestor:

console.table([...document.querySelectorAll('h1')].map((h1, index) => {
  const section = h1.closest('section, article, aside, nav');
  return {
    number: index + 1,
    text: h1.textContent.trim().replace(/\s+/g, ' '),
    nestedInH1: Boolean(h1.parentElement?.closest('h1')),
    sectioningAncestor: section?.tagName.toLowerCase() ?? 'none',
    sectionId: section?.id || 'none',
  };
}));

For a fast count and visual outline:

const h1s = [...document.querySelectorAll('h1')];
console.log(`${h1s.length} H1 element(s)`);
h1s.forEach((h1, i) => console.log(`${i + 1}.`, h1.textContent.trim(), h1));

The count alone is not the verdict. Review whether each H1 represents a real top-level heading, whether a logo or shared template creates an accidental one, and whether nested sectioning relies on the obsolete outline-algorithm pattern.

TL;DR — Multiple H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. don’t hurt Google rankings — Mueller has said so directly and repeatedly since 2019 (“not a critical issue”), unreversed through 2026. HTML5 (2014) made multiple sibling <h1> elements conforming; the “exactly one H1” rule is an HTML4/XHTML-strict holdover. The mechanism that once justified nested multiple-H1 patterns — the outline algorithm — was removed from the WHATWG Living Standard in July 2022 (PR #7829) because no browser ever implemented it, which is why nesting H1s inside nested sectioning content is now non-conforming while sibling H1s stay fine. “Harmless for Google” ≠ “zero downside”: Bing’s (2009, unrevisited) line is that extra H1s “diminish the value” of the tag, and screen readers announce every H1 as top-level, so several can confuse heading navigation. 51.3% of sites have multiple H1s somewhere — a common, benign template pattern. Fix for accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all./tidiness, not rankings.

Evidence for this claim Google's current guidance treats semantic heading order as useful for screen readers but not something that materially changes Google Search behavior. Scope: Current Google SEO Starter Guide; does not establish that every multiple-H1 pattern is ideal HTML. Confidence: high · Verified: 2026-07-14 Google Search Central: SEO Starter Guide Evidence for this claim A page without a single clear first-level heading can be harder for assistive-technology users to navigate. Scope: Accessibility and document organization, not a Google penalty claim. Confidence: high · Verified: 2026-07-14 MDN: Heading elements — Accessibility

What we’re actually asking

This article answers one narrow, high-anxiety question: does having more than one <h1> on a page hurt SEO? It deliberately doesn’t re-litigate the general H1 case — whether the H1 is a ranking factor, how it feeds the SERP title linkThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim., the H1-vs-title-tag distinction. That’s the H1 tagAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. deep dive; go there for the broader picture. Here we go deep on the multiple-H1 myth and, more importantly, on the HTML-spec history that almost every competing article gets vague about.

Does Google penalize multiple H1 tags?

No. And Google has said so about as many ways as it can.

The core statements come from a September 30, 2019 Webmaster Central hangout, where John Mueller was direct:

“You can use H1 tags as often as you want on a page. There’s no limit, neither upper or lower bound.”

“Your site is going to rank perfectly fine with no H1 tags or with five H1 tags.”

And — this is the single most relevant line for the “my audit tool flagged it” crowd — he addressed the tool warnings head-on:

“Some SEO tools flag this as an issue and say like ‘oh you don’t have any H1 tag or you have two H1 tags’… from our point of view that’s not a critical issue.”

He softened that with the honest caveat that it can still be worth a look: “From a usability point of view maybe it makes sense to improve that. So it’s not that I would completely ignore those suggestions but I wouldn’t see it as a critical issue.” That’s the whole verdict in miniature — not a ranking problem, maybe a usability nicety.

In a follow-up #AskGoogleWebmasters video a few days later, Mueller added: “Our systems don’t have a problem when it comes to multiple H1 headings on a page. That’s a fairly common pattern on the web.” (I’d treat the exact wording of the other lines from that video as relayed-but-widely-corroborated rather than transcript-verified — the “not a critical issue” and “no limit” lines above are the ones I’d hang an argument on.)

Is this still true in 2026?

Yes. I looked specifically for a newer Google statement that walks any of this back, and there isn’t one. The 2019 Mueller quotes remain the most recent direct on-the-record Google statement on the multiple-H1 question. The adjacent position — that heading order and count don’t affect rankings — got reinforced in Google’s July 2024 SEO Office Hours, where Gary Illyes said out-of-order headings don’t matter for Google Search and that “just because a non-Google tool tells you something is good or bad, that doesn’t make it relevant for Google.” Google’s SEO Starter Guide files heading count under things you shouldn’t focus on: “There’s also no magical, ideal amount of headings a given page should have.” Five-plus years, no reversal. Treat the position as stable, not stale.

Did HTML5 actually change the rule, or is that an urban legend?

This is where I can add something most articles skip. “HTML5 allows multiple H1s” gets repeated everywhere without anyone citing what changed or when. The real history has three acts, and getting them straight is the whole point of this page.

Act 1 — the HTML4/XHTML-strict era: “one H1” was a convention, not really a hard rule

The “exactly one H1 per document” belief predates HTML5. It came out of XHTML-strict-style document thinking and a general sense that a document has one title. It was never a bright-line HTML4 validation error the way people remember it — it was a convention that hardened into folklore.

Act 2 — HTML5 (2014): multiple sibling H1s become explicitly conforming

HTML5 put the matter to rest at the spec level. The WHATWG HTML Living Standard still carries a worked example of a document with three sibling top-level headings — <h1>Apples</h1>, <h1>Bananas</h1>, <h1>Carambola</h1> — captioned to the effect that a document can contain multiple top-level headings. That’s the plainest possible spec-level confirmation: multiple <h1> elements are conforming HTML.

HTML5 also introduced the outline algorithm, which is where the “multiple H1s, especially inside sections, are fine” idea really came from. The intended pattern was that each <article>, <section>, or <aside> could open with its own <h1>, and a conforming browser was supposed to compute each heading’s effective level from how deeply it was nested — so a deeply nested <h1> would be treated as if it were an H3 or H4. On paper, that made lots of H1s not just legal but the recommended way to structure a page.

Act 3 — July 2022: the outline algorithm is removed because no browser ever built it

Here’s the fact almost no competing article mentions. The outline algorithm was pulled from the WHATWG Living Standard in PR #7829 (“replace current outline algorithm with one based on heading levels”), authored by Steve Faulkner and merged July 1, 2022. The document “outline” concept was replaced with one derived purely from the flat sequence of <h1>–<h6> elements and their explicit levels — not from nesting inside sectioning elements.

The reason for the removal is the whole story: the outline algorithm had sat in the spec for over a decade without a single browser ever implementing it. Screen readers and browsers always treated every <h1> as a top-level heading regardless of nesting. The “some H1s effectively become H3s” behavior the spec described never existed anywhere except in the spec text. Accessibility writers had been saying so for years — Adrian Roselli’s 2016 There Is No Document Outline Algorithm is the piece the spec discussion kept coming back to, and Bruce Lawson’s plain-language explainer summarizes why removing it actually improves accessibility guidance.

What that leaves you with today

So the precise, current (post-2022) status — and this is the cruxChrome User Experience Report — Google's public dataset of real-world (field) performance data from eligible Chrome users. It's the official field-data source behind the Core Web Vitals program. of the “does it hurt” question:

• Several sibling <h1> elements at the same nesting depth (the Apples/Bananas/Carambola pattern) remain conforming HTML.
• Nesting an <h1> inside nested <section>/<article>/<aside> specifically to lean on the old outline-algorithm behavior is now non-conforming, precisely because that mechanism was removed.

MDN states it cleanly: multiple <h1> elements “on one page is allowed by the HTML standard (as long as they are not nested), this is not considered a best practice,” and nesting H1s in nested sectioning elements “was allowed in older versions of the HTML standard. However, this was never considered a best practice and is now non-conforming.” MDN’s own recommendation: “Prefer using only one <h1> per page and nest headings without skipping levels.”

Most SEO content collapses all of this into a single blanket “multiple H1s are HTML5-legal.” You can be more precise than that.

What about Bing?

Bing is the one place the engines genuinely diverge — but read its position with a date attached. Bing’s citable H1 statement is a 2009 webmaster blog post, Architecting content for SEO (SEM 101):

“Only use only one <h1> tag per page. No, you won’t be considered web spam if you use two, but you diminish the value of the <h1> tag if you use more than one (after all, there is supposed to be only one big idea per page, right?).”

That’s a softer, dilution-style caution rather than Google’s flat “not critical” — Bing says extra H1s won’t get you flagged as spam but weaken the signal. Two honest caveats: it’s from 2009, which predates HTML5’s 2014 multiple-H1 allowance, and there’s no evidence Bing has revisited it since. It’s still the most recent Bing-specific statement I can find, so I cite it — but as a dated position, not a current one.

If it doesn’t hurt rankings, why do accessibility experts still say to avoid it?

Because this is the real, current, non-mythical downside — and it’s a completely different axis than SEO.

Screen readers announce every <h1> as a top-level heading, regardless of where it sits in the page’s HTML structure. The outline algorithm’s promised nesting-aware behavior — where a nested H1 would be announced as a lower level — never existed in assistive technology. So a page with several H1s presents a screen-reader user (many of whom navigate page-to-page by heading) with several competing “this is the main thing” signals. The BOIA accessibility team frames it as: when multiple H1s are present, users “must ask which heading truly represents the main topic.” HTML validators say the same thing in tooling language — “all <h1> elements are treated as top-level headings by many screen readers and other tools.”

This is why “multiple H1s don’t hurt Google rankings” and “multiple H1s have zero downside for every user” are two different claims. The first is true. The second isn’t. Keep them separate.

So should you fix a page with multiple H1s?

Triage, don’t panic. Three cases:

1. A template bug — logo-in-H1 plus title-in-H1. This is the single most common real-world cause. It’s low priority for SEO, but it’s an easy accessibility win: demote the logo to a <div>, <p>, or <span> (or an <h2> if it genuinely needs a heading) and leave the article title as the one H1. Quick, low-risk.
2. Keyword-stuffing across several H1s. If someone crammed the same target phrase into five H1s to game rankings, that’s worth fixing — but not because Google penalizes the count. It’s worth fixing because it reads as low-quality to the humans deciding whether to stay, and Mueller’s “not critical” framing was never a license for manipulative heading spam. The fix is writing honest headings, not deleting H1s per se.
3. A template that legitimately uses sibling H1s and no one’s confused. If a design genuinely calls for several equal top-level headings and it’s clean and readable, you can leave it. Conforming HTML, no ranking issue. Weigh the minor accessibility nuance and move on.

How common is this, really?

Common enough that treating it as a catastrophe makes no sense. In my million-domain Site Audit study of over a million domains, 51.3% of sites had pages with multiple H1 tagsWhen a single web page contains more than one <h1> element. The HTML standard permits non-nested sibling h1s, and Google treats multiple h1s as a low-priority ranking concern — but nested h1 patterns are non-conforming, and one clear h1 is still the accessibility default.. My framing at the time still holds: multiple H1s are allowed in modern HTML and Google has said they’re not a problem — worth confirming each H1-tagged heading is actually page-relevant, but not a significant concern. If roughly half the web has this and Google hasn’t said a word against it in five-plus years, it’s clearly not the SEO emergency your audit tool’s red flag implies. (For how missing H1s compare — also extremely common, also low-impact — see the H1 tag article; I won’t restate those numbers here.)

The bottom line

Multiple H1 tags do not hurt your Google rankings. HTML5 made sibling H1s conforming; the 2022 spec change removed the outline mechanism that once justified nested ones, so nesting H1s in nested sectioning content is the only genuinely non-conforming case now. Bing’s dated “diminishes value” caution and the real, current accessibility concern are the reasons a single clear H1 is still the tidy default — not any Google penalty. Fix template duplicates when it’s cheap; don’t spend a sprint on it.

For the general H1 picture — ranking-factor status, the title-link relationship, missing-H1 data — see the H1 tag deep dive. For the whole H1–H6 family and heading order, see the header tagsHeader tags (heading tags) are the HTML elements <h1> through <h6> that mark the structural hierarchy of a page's content. They help users, search engines, and screen readers understand what each section is about. hub. And the <header> landmark element is a different thing entirely from an H1 heading — don’t confuse them.

AI summary

A condensed take on the Advanced version:

• Direct answer: no, multiple H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. don’t hurt Google rankings. Mueller, 2019: a page ranks “perfectly fine with no H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. or with five H1 tags,” and when tools flag multiple H1s “from our point of view that’s not a critical issue.” Unreversed through 2026.
• HTML5 (2014) made multiple sibling H1s conforming, ending the HTML4/XHTML “exactly one H1” convention. The spec’s own Apples/Bananas/Carambola example shows multiple top-level headings.
• July 2022: the outline algorithm was removed from the WHATWG Living Standard (PR #7829, Steve Faulkner) because no browser ever implemented it. Result: sibling H1s stay conforming; nesting H1s inside nested sectioning content is now non-conforming (per MDN).
• “Not an SEO problem” ≠ “no downside.” Bing’s 2009 (unrevisited) line is that extra H1s “diminish the value” of the tag; screen readers announce every H1 as top-level, so several can confuse heading-based navigation — a real, current accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. concern independent of SEO.
• Audit-tool warnings are low-severity by design (Ahrefs’ own Site Audit included), matching Mueller’s “not critical… maybe worth a usability look.”
• Most common cause is templating — logo-in-H1 plus title-in-H1 — not content strategy. 51.3% of sites have multiple H1s somewhere (Patrick’s million-domain study), so it’s widespread and largely benign.
• Triage: fix template duplicates cheaply (accessibility win); fix genuine keyword-stuffed H1s for quality; leave clean sibling-H1 designs alone.
• Bottom line: structure for readers and accessibility; the “one H1” default is about tidiness and screen readers, not a Google penalty.

Official documentation

Primary-source documentation from the search engines and the HTML spec.

Google

• SEO Starter Guide: The Basics — heading count and order under “things you shouldn’t focus on”; “no magical, ideal amount of headings.”
• Influencing your title links in Google Search — lists <h1> elements as a source for the SERP title linkThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and suggests putting the title text in the first visible <h1> (a practical reason to order multiple H1sAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. well).
• July 2024 SEO Office Hours — Gary Illyes: heading order doesn’t affect Google rankings, and non-Google tool warnings aren’t automatically relevant to Google.

HTML spec (WHATWG) / MDN

• HTML Living Standard — Sections — the conforming multiple-top-level-heading (Apples/Bananas/Carambola) example.
• WHATWG html PR #7829 — “replace current outline algorithm with one based on heading levels” (Steve Faulkner; merged July 1, 2022).
• WHATWG html commit 6682bde — the merged outline-algorithm-removal change.
• MDN — <h1>–<h6> heading elements — the current conforming/non-conforming distinction and the “prefer one H1” recommendation.

Bing / Microsoft

• Architecting content for SEO (SEM 101) — Bing’s “one H1 per page” / “diminishes the value” position (2009, unrevisited).

Quotes from the source

On-the-record statements from Google and Bing, plus the HTML spec and accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. sources. Each deep link jumps to the quoted passage where the page supports text fragments.

Google — multiple H1sAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. don’t hurt (John Mueller, Sept 30, 2019 hangout)

• “You can use H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. as often as you want on a page. There’s no limit, neither upper or lower bound.” — John Mueller, Google. Jump to quote
• “Your site is going to rank perfectly fine with no H1 tags or with five H1 tags.” — John Mueller, Google. Read the coverage
• “Some SEO tools flag this as an issue and say like ‘oh you don’t have any H1 tag or you have two H1 tags’… from our point of view that’s not a critical issue.” — John Mueller, Google. The single most relevant line for the “my audit tool flagged multiple H1s” question. Read the coverage
• “Our systems don’t have a problem when it comes to multiple H1 headings on a page. That’s a fairly common pattern on the web.” — John Mueller, Google, #AskGoogleWebmasters (Oct 2019). Watch

HTML spec / MDN — what’s conforming today

• “While using multiple <h1> elements on one page is allowed by the HTML standard (as long as they are not nested), this is not considered a best practice.” — MDN Web Docs. Read on MDN
• “Nesting multiple <h1> elements in nested sectioning elements was allowed in older versions of the HTML standard. However, this was never considered a best practice and is now non-conforming.” — MDN Web Docs. Read on MDN
• “Prefer using only one <h1> per page and nest headings without skipping levels.” — MDN Web Docs. Read on MDN

Bing — one H1 per page (2009, unrevisited)

• “Only use only one <h1> tag per page. No, you won’t be considered web spam if you use two, but you diminish the value of the <h1> tag if you use more than one (after all, there is supposed to be only one big idea per page, right?).” — Bing WebmasterMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. Blog, “Architecting content for SEO (SEM 101)” (2009). Read on Bing

Accessibility — the real reason to keep one H1

• “When multiple <h1> tags are present, users must ask which heading truly represents the main topic.” — BOIA (Bureau of Internet Accessibility). Read on BOIA

Should I fix my multiple H1 tags?

Work down this until you hit a verdict. None of these are ranking emergencies — this is triage for accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all., tidiness, and the occasional real quality problem.

1. Is the same keyword phrase crammed into several H1sAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. to manipulate rankings?

• Yes → Fix it — but as a content quality fix, not an H1-count fix. Rewrite the headings to honestly describe their sections. Google won’t penalize the count, but keyword-stuffed headings read as low quality to humans. Done.
• No → Continue.

2. Is one of the extra H1s a logo, site name, tagline, or widget wrapped in <h1>?

• Yes → This is the classic template bug. Low priority for SEO, but an easy accessibility win: demote it to a <div>/<p>/<span>, or <h2> if it truly needs to be a heading. Leave the real page titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. as the single H1. Do it when convenient.
• No → Continue.

3. Are the H1s nested inside nested <section>/<article>/<aside> elements (the old outline-algorithm pattern)?

• Yes → This is now non-conforming HTML (post-2022 spec change) and screen readers never honored the intended nesting anyway. Convert the nested ones to the appropriate <h2>/<h3> for their depth. Worth cleaning up for accessibility.
• No (they’re sibling H1s at the same level) → Continue.

4. Do the sibling H1s genuinely represent several equal top-level ideas, and is the page clean and readable?

• Yes → Conforming HTML, no ranking issue. You can leave it. If you want the screen-reader clarity, consolidate to one H1 + H2s — but this is optional. Leave it or tidy it; your call.
• No / it just looks accidental → Consolidate to one clear H1 with H2s beneath. Low-risk cleanup. Tidy it up.

The overriding rule: at no branch is the answer “your rankings are being hurt.” The reasons to act are accessibility, HTML conformance, and content quality — never a Google H1-count penalty.

Multiple-H1 anti-patterns

The recurring ways people get this wrong — in both directions.

1. Panicking over the audit-tool warning. “Multiple H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore.” lights up red and someone files a P1 ticket. It’s a low-severity usability note, not a ranking penalty — Mueller called it “not a critical issue.” Triage it accordingly.

2. Wrapping the logo in an <h1> on every page. The most common real cause of a stray second H1. It puts the same heading on every page and wastes the H1 signal on your brand instead of the page’s topic. Demote it to a non-heading element.

3. Assuming “HTML5 allows multiple H1s” means any multiple-H1 pattern is fine. Sibling H1s are conforming. Nesting H1s inside nested sectioning elements is non-conforming since the 2022 spec change. The blanket claim glosses over the one case that’s actually wrong.

4. Trusting the old outline algorithm to “downgrade” nested H1s. No browser or screen reader ever implemented it — that’s why it was removed from the spec. A nested <h1> is announced as top-level, same as any other H1. Don’t structure a page on the assumption that nesting changes its effective level.

5. Keyword-stuffing across five H1s and calling it “Google says it’s fine.” Mueller’s “not critical” was about honest structural duplicates, not manipulative heading spam. Multiple descriptive H1s: fine. Five copies of your money keyword in H1s: a quality problem, even if the count itself isn’t penalized.

6. Treating multiple H1s as “zero downside.” The over-correction. Google doesn’t care about the count, but Bing’s stated (dated) view is that extra H1s dilute the tag, and screen readers genuinely get confused by several top-level headings. “Doesn’t hurt Google rankings” isn’t “no downside for anyone.”

7. Spending a sprint retro-fixing multiple H1s across an established site for rankings. The wins here are accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. and tidiness, not rankings. If you’re reworking H1s expecting a traffic lift, you’ve mis-scoped the project.

Multiple H1s — cheat sheet

Does it hurt? By concern

The HTML timeline

Fast facts

• 51.3% of sites have multiple H1s somewhere (my million-domain study) — common, benign.
• Audit tools flag it at low severity (Ahrefs Site Audit included), matching Mueller’s “not critical.”
• Most common cause: logo-in-H1 + title-in-H1 template bug.
• Google looks at the first <h1> for SERP title-link generation — so if you have several, order the most important one first.
• The reason to keep one H1 is accessibility + tidiness, not a Google penalty.

Fixing, ranked by priority

1. Keyword-stuffed H1s → rewrite (quality fix)
2. Logo/widget as H1 → demote to non-heading (easy accessibility win)
3. Nested H1s in nested sections → convert to H2/H3 (conformance)
4. Clean sibling H1s → optional; leave or consolidate

Resources worth your time

My related writing & data

• We Studied Over 1 Million Domains to Find the Most Common Technical SEO Issues — my million-domain Site Audit study; source of the 51.3%-multiple-H1An H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. figure and my “not a problem” framing.
• What Is an H1 Tag? SEO Best Practices — the general H1 deep dive: ranking-factor status, the title-link relationship, missing-H1 data.
• The Beginner’s Guide to Technical SEO — where on-page elements like headings fit in the bigger picture.

Related on this site

• The H1 tagAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. article — the general H1 case (this article deliberately doesn’t repeat it).
• The header tagsHeader tags (heading tags) are the HTML elements <h1> through <h6> that mark the structural hierarchy of a page's content. They help users, search engines, and screen readers understand what each section is about. hub — the full H1–H6 hierarchy and heading order.
• The title tagThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. article — the head element that drives your SERP title link (and which the H1 feeds into).

From around the industry

• Google Says H1 Headings Are Useful but Not Critical (Search Engine Journal) — verbatim Mueller quotes from the Sept 2019 hangout, including “not a critical issue” and “no limit, neither upper or lower bound.”
• MDN — <h1>–<h6> heading elements — the current conforming/non-conforming distinction and the “prefer one H1” recommendation.
• WHATWG html PR #7829 (Steve Faulkner) — the July 2022 change that removed the outline algorithm; the primary source for the spec history.
• There Is No Document Outline Algorithm (Adrian Roselli, 2016) — the foundational argument the spec removal was built on.
• Why the HTML outlining algorithm was removed from the spec (Bruce Lawson, 2022) — the plain-language explainer.
• Multiple H1 Tags Are Bad for Accessibility (And SEO) (BOIA) — the accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. case for one clear H1.
• Architecting content for SEO (SEM 101) (Bing WebmasterMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. Blog, 2009) — Bing’s “diminishes the value” position, in its own words.

Test yourself: Multiple H1 Tags

Five quick questions on the multiple-H1An H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. question. Pick an answer for each, then check.

Multiple H1 Tags

When a single web page contains more than one <h1> element. The HTML standard permits non-nested sibling h1s, and Google treats multiple h1s as a low-priority ranking concern — but nested h1 patterns are non-conforming, and one clear h1 is still the accessibility default.

Related: H1 Tag, Header Tags, Title Tag

Multiple H1 Tags

Multiple H1 tagsAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about. means a single HTML page contains more than one <h1> element — for example, a template that wraps the logo in an <h1> and also wraps the article title in a second <h1>, or a page built from <article>/<section> blocks that each open with their own <h1>. MDN’s heading-element reference explains that multiple non-nested H1s are allowed by the HTML standard but are not considered best practice; a page should generally have one H1. Google’s public guidance likewise treats multiple H1s as a low-priority ranking concern, but one clear H1 remains the simpler accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. default. The old HTML outline algorithm that encouraged nested section H1s was removed from the standard in 2022 because browsers never implemented it, and nested H1 patterns are now non-conforming.

Related: H1 Tag, Header Tags, Title Tag