You run a site audit, and there it is in orange or red: “Multiple H1 tags found on 412 pages.” Many business owners panic at this point. They have heard that a page must have exactly one H1, and that two of them will confuse Google or even get the page penalized.
The short answer is calmer than that. Google has said plainly that multiple H1s are not a problem for its systems. But that doesn’t mean the warning is useless. Multiple H1s are often a sign of a messy template, and messy headings can hurt readers who use screen readers, and occasionally the title Google shows for your page.
Let me explain what Google has actually said, why themes create extra H1s in the first place, when it matters and when you can safely ignore it, how to fix it in common CMSs, and how to read the warning in your audit tool.
What Google has said about multiple H1 headings
First, a quick definition. An H1 is the top-level heading in a page’s HTML, written as <h1>. It is usually the main title of the page that readers see. H2 to H6 are lower levels used for sections and sub-sections. If you’re new to headings, our lesson on headings and page structure explains the basics, and our guide to heading tags H1 to H6 covers how to use them well.
Google’s position has been consistent for years. In an October 2019 #AskGoogleWebmasters video, reported by Search Engine Land, John Mueller said:
“Our systems don’t have a problem when it comes to multiple H1 headings on a page.”
— John Mueller, Google, via Search Engine Land, Multiple H1s won’t get in the way of your SEO, Google says
Around the same time, as Search Engine Journal reported, Mueller described H1 elements as “a great way to give more structure to a page” but said a missing or imperfect H1 was “not a critical issue.”
Google’s current SEO Starter Guide (last updated December 2025) goes further on heading order:
“Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn’t matter if you’re using them out of order.”
— Google Search Central, SEO Starter Guide
So where does the “one H1 per page” rule come from? Partly from older SEO habits, and partly from accessibility and HTML guidance, which I cover below. Even some well-known SEO guides still recommend it. Ahrefs’ on-page SEO checklist, for example, recommends one H1 per page as the natural place for the page title. I agree with that as a tidy default. I just don’t treat breaking it as an emergency.
Why your theme is producing more than one H1
Very few people type two H1s on purpose. Extra H1s almost always come from the theme, a page builder or a plugin. These are the usual culprits:
- The logo or site name wrapped in an H1 on every page, so the real page title becomes the second H1.
- Hero sliders where every slide’s headline is an H1, even the hidden ones.
- Page builder heading widgets where an editor picked “H1” because it looked big, not because it was the main title.
- Sidebar or footer widget titles coded as H1 in older themes.
- Separate mobile and desktop headers, where the same title appears twice in the HTML and one is hidden with CSS.
- Pasted content from Google Docs or Word, where “Heading 1” styles came through as H1.
- Blog archive pages where every post title in the list is an H1.
- Cookie banners, popups or modal windows that use an H1 for their own title.
The duplicated mobile/desktop header is worth a special mention. It’s common on sites where the mobile menu is built as a separate block of HTML. If that block includes the page title or site name as an H1, you end up with two H1s, one hidden. Google indexes the mobile version of your site, so it’s worth checking what that mobile markup contains. I cover this in more depth in our guide to mobile navigation and hamburger menus.
When multiple H1s matter and when they don’t
Here is how I sort the cases. Most fall into “leave it” or “fix when convenient.”
| Situation | Does it matter? | Why |
|---|---|---|
| Logo is an H1 on every page, page title is a second H1 | Low. Fix when convenient | Google can still work out the main title; screen reader users hear the site name as the top heading on every page |
| Article uses H1 for its title and for two section headings | Low to medium | Search is fine; the outline is flatter than it should be for assistive tech |
| Three equally large H1s at the top, none clearly the main title | Medium | Google may struggle to pick the main title for the title link |
| H1s hidden in sliders or popups with promotional text | Medium | The first prominent heading may be a promo line, not your page topic |
| No visible H1 at all, styled divs instead | Medium | Loses a clear main-title signal and hurts heading navigation |
| Every post on a blog archive is an H1 | Low | Archive pages rarely matter much; tidy up in the theme |
| Single-page app with H1s per view, only one visible at a time | Low, if rendered correctly | Check what Google’s rendered HTML shows |
The one SEO risk worth knowing: title links
The real search-related risk is not rankings. It’s the title link, the clickable blue headline Google shows for your page. Google often builds it from your title tag, but it can also use other text on the page. Its title link documentation says its sources include the main visual title, heading elements and other large and prominent text, and it suggests making your main title distinctive, for example by putting it in the first visible H1 on the page.
The same documentation lists “no clear main title” as a problem: when several headings have the same visual weight, Google may use the first one. If your first H1 is a slider headline that says “Big Autumn Sale”, that could end up as the title link for a product category page. That is a real, if rare, reason to clean things up. Our guide on title tags versus H1s explains how the two should work together, and our guide on why Google rewrites title tags covers the other triggers.
What accessibility guidance says about H1s
This is where the “one H1” habit makes the most sense. People who use screen readers often move around a page by jumping from heading to heading. That turns your headings into a table of contents they listen to. The same headings also power any on-page contents list, which I cover in our guide to tables of contents and jump links.
WebAIM’s Screen Reader User Survey #10 (December 2023 to January 2024, 1,539 valid responses) asked how people find information on a long web page. 71.6% said their first step is to navigate through the headings. In the same survey, 88.8% found heading levels very or somewhat useful. WebAIM notes the sample was not controlled, so I treat these as strong direction rather than exact population figures.
MDN, the widely used web developer reference, describes multiple H1s as allowed by the HTML standard but not a best practice:
“Prefer using only one <h1> per page and nest headings without skipping levels.”
— MDN Web Docs, The HTML Section Heading elements
MDN also notes that nesting multiple H1s inside sectioning elements, an idea from older HTML versions, was never considered a best practice and is now non-conforming. If you heard that “HTML5 lets every section have its own H1”, that advice is out of date. The W3C’s Web Accessibility Initiative tutorial on headings adds that skipping heading ranks can be confusing and should be avoided where possible.
So the honest summary is this: for Google, one H1 versus several is a minor detail. For people using assistive technology, a clear single H1 followed by logical H2s and H3s is meaningfully better. That is a good enough reason to fix it, without the fear. Our guide to where accessibility and SEO overlap covers more of these shared wins.
How to find every H1 on a page in two minutes
Before you change anything, see what you actually have. Here is a quick method that needs no paid tools:
- Open the page in Chrome.
- Right-click and choose Inspect, then open the Console tab.
- Paste this and press Enter:
[...document.querySelectorAll('h1')].map(h => [h.innerText.trim(), h.offsetParent !== null]) - You’ll get a list of every H1’s text and whether it is visible (
true) or hidden (false). - Repeat with Chrome’s device toolbar switched to a phone size, because mobile layouts sometimes reveal different headings.
- For a whole site, run a crawler. Screaming Frog, for example, has an H1 tab with a filter for pages with multiple H1s.
If you’d rather see the full outline, run the same snippet with 'h1,h2,h3' instead of 'h1' and add h.tagName to the output. You’ll quickly spot jumps like H1 straight to H4, or H2s used for sidebar labels.
Fixing heading markup in WordPress, Shopify and page builders
The fix depends on where the extra H1 comes from. Here is a practical map.
| Source of extra H1 | Where to fix | What to change |
|---|---|---|
| Logo or site title in header | Theme template (WordPress header.php in a child theme; Shopify header section Liquid file) | Use H1 for the logo only on the home page, or not at all; wrap it in a <div> or <p> elsewhere |
| Page builder heading widget | The widget’s HTML tag setting | Change the tag to H2 or H3; keep the visual size with styling |
| Block editor content | Heading block toolbar | Change the level; keep only the post title as H1 |
| Hero slider | Slider plugin layer settings | Use H2 or paragraph tags for slide text |
| Widget titles | Theme’s widget registration (developer) | Change the wrapper to H2 or H3 |
| Duplicate mobile header | Theme header template (developer) | Render one header and restyle it responsively, or demote the duplicate |
| Pasted content | The post editor | Convert pasted H1s to H2s |
A few notes on common setups:
- WordPress: most modern themes output the post title as the only H1. If yours doesn’t, always change templates in a child theme, or your fix will vanish with the next theme update. Our WordPress SEO setup guide covers theme choices.
- Shopify: headings live in theme section files. Many themes let you pick a heading size in the theme editor, but that often changes only the look, not the tag. Check the HTML after any change. Our Shopify SEO guide has more on theme-level fixes.
- Wix, Squarespace and similar builders: text styles labeled “Heading 1” usually output an H1. Use those styles for the page title only, and pick Heading 2 or 3 for sections even if you prefer the bigger look; you can restyle the size in the site’s design settings.
Don’t make these fixes worse than the problem
- Don’t hide a keyword-stuffed H1 with CSS to “keep” an SEO heading. Hidden headings that readers can’t see are a bad idea.
- Don’t delete the visible title just to remove a duplicate. Demote the extra one instead.
- Don’t rewrite every H1 on the site in one go without tracking. Change the template, then watch titles and clicks for a few weeks.
A worked example: one template, 412 warnings
Example (hypothetical): A home-services business has a 430-page WordPress site. An audit flags 412 pages with multiple H1s. It looks alarming.
On inspection, there are just two causes:
- The theme wraps the logo text “Example Plumbing & Heating” in an H1 on every page. That accounts for 405 of the 412 pages.
- Seven landing pages built with a page builder use an H1 widget for a mid-page promo banner.
The fix for cause one is a single change in the child theme’s header template: keep the logo as an H1 on the home page only, and use a <p> elsewhere. That takes a developer perhaps 30 minutes, including testing. The fix for cause two is seven quick widget edits.
The audit warning count drops from 412 to zero. Will rankings jump? I wouldn’t expect them to; Google has told us this was never a ranking problem. What improves is that screen reader users now hear the actual page topic as the first heading, and Google gets one clear main title on every page. That is a cheap improvement worth making, but not one worth losing sleep over.
This example also shows why I always look at causes, not warning counts. Four hundred warnings from one template line is a smaller problem than ten warnings from ten different editors doing ten different things.
How to read the multiple H1 warning in audit tools
Audit tools flag multiple H1s because it’s easy to detect, not because it’s important. Here is how the common heading warnings compare, in my view.
| Warning | Priority I’d give it | What to check first |
|---|---|---|
| Multiple H1 tags | Low | Is it one template causing all of them? Is the first H1 the real title? |
| Missing H1 | Medium | Is the visible title a styled div? Is the H1 added by JavaScript only? |
| H1 identical to title tag | Very low | Usually fine; see our title tag vs H1 guide |
| Duplicate H1 across pages | Medium | Are these near-duplicate pages that should be merged or made distinct? |
| Non-sequential headings (H1 to H4) | Low for SEO, medium for accessibility | Mostly a theme or editor habit; fix in templates |
| H1 too long | Low | Only matters if it’s stuffed or unreadable |
When you report to a client or boss, I suggest grouping warnings by root cause and effort, not by count. “One header template change fixes 405 pages” is far more useful than “412 errors.” Our step-by-step SEO audit guide explains how to prioritize findings like this.
One more nuance: some tools look at the raw HTML, and some look at the rendered page after JavaScript runs. If your theme adds or removes headings with JavaScript, two tools may disagree. When in doubt, use the URL Inspection tool in Search Console and check the rendered HTML Google actually sees.
Questions people ask about multiple H1 tags
Will multiple H1 tags get my site penalized?
No. Google has said its systems don’t have a problem with multiple H1s on a page. There is no penalty for it.
Should the H1 be the same as the title tag?
It can be, and that’s fine. Many sites make them slightly different, with the title tag tuned for search results and the H1 for readers on the page. Keep them about the same topic.
Is it okay to have no H1 at all?
Google said a missing H1 isn’t critical, but I wouldn’t choose it. A clear H1 helps readers, screen reader users and Google’s title link systems identify the main title.
Does HTML5 allow an H1 in every section?
That idea came from an outline algorithm that browsers and screen readers never implemented. MDN now describes nesting H1s in sections as non-conforming. Use one H1 and nested H2s and H3s.
Should my logo be an H1?
Only on the home page, if at all. On inner pages, the page’s own title should be the H1, and the logo can be a linked image or plain text.
What I would do about your multiple H1 warning today
In brief: multiple H1s won’t hurt your rankings, and you don’t need to panic about a big warning number. But a clean heading structure helps real people, especially those using screen readers, and it helps Google pick the right title. Find the root cause, fix it once in the template, and move on to bigger issues.
If your audit list is long and you’re not sure what to fix first, our SEO team can sort the real problems from the noise. Get in touch for a quote and send us your latest audit.
Further reading on multiple H1 tags
- Mobile Navigation and Hamburger Menus: SEO Best Practices
- Image Sitemaps: Do You Need One?
- Table of Contents and Jump Links for SEO
Sources for this multiple H1 tags guide
- Search Engine Land: Multiple H1s won’t get in the way of your SEO, Google says
- Search Engine Journal: Google Says H1 Headings Are Useful but Not Critical
- Google Search Central: SEO Starter Guide
- Google Search Central: Influencing your title links
- MDN Web Docs: The HTML Section Heading elements
- W3C WAI: Headings tutorial
- WebAIM: Screen Reader User Survey #10 Results
- Ahrefs: On-Page SEO Checklist
