Can a Page Have Multiple H1 Tags? What Google Says

Yes, a page can have multiple H1 tags, and Google does not penalize it. Google's own SEO Starter Guide says there is no magical, ideal number of headings, and its title link documentation only asks that your main title be clear and distinctive. Still, for most product pages, collection pages and articles, one descriptive H1 followed by logically nested H2s and H3s is the better default, because it keeps the main title unambiguous for Google and for people using screen readers.

This guide is for Shopify and e-commerce teams whose audit tool just flagged "multiple H1 tags" and who need to decide whether it matters. You'll get what Google, the HTML standard and accessibility guidance actually say, where extra H1s come from in Shopify's Dawn and Horizon themes (we checked the theme code and the live demo stores), a five-minute way to inspect any page, and a priority table that tells you when to fix it and when to move on.

Does Google penalize multiple H1 tags?

No. There is no multiple H1 penalty, and Google has said so in documentation and on video.

• SEO Starter Guide. Google writes that there is "no magical, ideal amount of headings a given page should have." The same section says semantic heading order is great for screen readers, but from Google Search's perspective it doesn't matter if headings are out of order, because the web in general is not valid HTML.
• Title link documentation. Google lists heading elements, such as <h1>, among the sources it uses to create the title link in search results. Its concern is clarity: when a page has two or more large, prominent headings with the same styling or heading level, Google "may use the first heading" as the title link text. The fix it suggests is to make the main title the most prominent text on the page, for example by putting it in the first visible <h1>.
• Ask Google Webmasters video, October 2019. In an episode on multiple H1 headings and accessibility, John Mueller said Google's systems don't have a problem with multiple H1 headings, which he described as a common pattern on the web.

So the honest answer to "can a page have multiple H1 tags" is yes, and a second H1 on its own will not cost you rankings. What it can cost you is a muddled title link, a confusing page for assistive technology users, and a template problem that repeats on every product page. Those are the things worth checking.

H1 versus the title tag

The H1 is the visible main heading inside the page. The <title> element is the document title that browsers show in tabs and that Google uses as a primary source for the title link. They should describe the same topic, but they don't have to match word for word. If Google is rewriting your title links, a weak or duplicated H1 is one of the first things to check, and our guide on why Google rewrites title tags covers the rest.

What HTML and accessibility rules say

The HTML Living Standard defines h1 to h6 as headings for their sections: "The h1 element is for a top-level section, h2 for a subsection, h3 for a sub-subsection, and so on." It doesn't cap the number of H1s. Its rules for headings and outlines say at least one heading should have level 1, and that each heading after another should be at the same level, a higher level, or exactly one level deeper. In plain terms, two H1s side by side are conforming; jumping from an H1 straight to an H3 is not.

One old idea is now gone. Earlier versions of HTML suggested that every <section> or <article> could start with its own H1 and browsers would work out the levels. That outline algorithm was never implemented by browsers or screen readers. MDN's reference now states that nesting multiple H1s in nested sectioning elements is non-conforming, and it recommends a single H1 per page with no skipped levels.

The W3C Web Accessibility Initiative's headings tutorial does not set a count either. It asks you to nest headings by rank and says skipping heading ranks "can be confusing and should be avoided where possible," while noting it's fine to skip ranks when closing subsections (going from an H4 back to an H2).

Why one H1 is still the best default

If Google doesn't care about the count, why bother? Because headings are not mainly for Google. They are how a big share of people actually move through a page.

In WebAIM's Screen Reader User Survey #11 (July to August 2026, 1,780 respondents), 67.8% said that when they look for information on a long page, the first thing they do is jump through the headings. That's more than five times the share who use the browser's Find feature. The same survey found 51.9% of respondents rate heading levels as very useful and another 36.4% as somewhat useful. When a page has two H1s that say different things, or an H1 that is just a logo, that heading list starts in the wrong place.

One H1 also gives your team a rule that's easy to follow. Editors know the product name or article title is the H1 and everything else is an H2 or lower. Developers know a section component should never output an H1. Audit tools stop flagging the same false alarm every month. None of this is a Google requirement. It's a publishing standard that prevents the mistakes Google's title link documentation describes.

Where one H1 is not the right answer

There are pages where more than one top level heading is reasonable: a long single page app view, a page that genuinely presents two independent documents, or a comparison page with two equal subjects. Even then, ask whether a single H1 over two H2s would describe the relationship better. On a Shopify store, that is almost always the case.

How common H1 problems really are

The HTTP Archive's Web Almanac measures headings on millions of pages each year. Its numbers show that a missing or empty H1 is a far more common problem than an extra one.

In the 2025 Web Almanac SEO chapter, 70% of mobile pages had an H1, but only 66% had an H1 with text in it. In 2022 the gap was wider: 66% present and 59% non-empty. The 2022 chapter suggested a likely cause for the gap: sites wrapping logo images in H1 elements on their home pages. That pattern is exactly what Shopify's Dawn theme does, as you'll see below.

H2 is now slightly more common than H1 (72% versus 71% of desktop pages in 2025), which tells you many sites skip the H1 entirely and start their outline one level down. If your crawler reports both "multiple H1s" and "missing H1" across a site, fix the missing ones first. Our guide to fixing a missing H1 tag in Shopify walks through that case.

Where extra H1s come from on Shopify

Most duplicate H1s on Shopify stores are not written by editors. They come from the theme, from an app, or from a block a merchant added in the theme editor. We checked Shopify's two reference themes in two ways: by reading the theme code in Shopify's public GitHub repositories (Dawn and Horizon, main branches as of October 2026) and by fetching the live demo stores and counting the H1 elements in the HTML they return (Dawn demo and Horizon demo store version 3.2.0).

Two practical lessons come out of this. First, on both themes the homepage H1 is your store name, not a description of what you sell. That is valid, but if you'd rather your homepage H1 say "Organic cotton baby clothes" than repeat the brand, you have to change the theme so the hero heading becomes the H1 and the logo wrapper doesn't. Adding a second H1 in the hero without touching the header is how most stores end up with two.

Second, on Horizon a heading's look and its level are separate settings. The "H1" option in a text block's typography preset is a style; the actual tag comes from the text content. Dawn does the same thing in code, styling an H1 as an H2 in the pop-up and, elsewhere, an H2 to look like an H1. That's the right approach, and it's the one to use when you fix your own templates.

Other common sources

• Editors pasting the title into the description. The product or article title is already the H1, and the first line of the body repeats it as another H1.
• Page builder and review apps. Section apps sometimes hard code H1 for their banner headings, and review widgets occasionally use large headings for their titles.
• Mobile and desktop duplicates. Some custom themes render one title for desktop and another for mobile and hide one with CSS. Both are in the HTML.
• Promo bars and announcement banners. A sale message styled to look big, marked up as an H1, sitting above the real title.

How to check the H1 tags on a page

A crawler count tells you that a page has more than one H1. It doesn't tell you which one is wrong. Use this sequence on one affected URL, then on one more URL from the same template.

1. Run the URL through a heading checker. Our free H1 and Heading Checker maps the page's heading outline and flags missing or duplicate H1s, empty headings and skipped levels. Note the text of every H1 it finds.
2. Find each H1 in the rendered page. In Chrome, open DevTools, press Ctrl+F or Cmd+F in the Elements panel and search for <h1. Hover each result to see where it sits on screen. Some will be invisible.
3. Compare source and rendered HTML. View Source shows what the server sent; the Elements panel shows the page after JavaScript ran. An app that injects a heading will only appear in the second.
4. Check what assistive technology sees. Open the Accessibility pane in DevTools, or use a screen reader's headings list (Rotor on VoiceOver, Insert+F6 in NVDA). A heading hidden with display: none is removed from the accessibility tree; one that is visually hidden with a utility class, like Horizon's shop name H1, is still announced.
5. Check both breakpoints. Resize to mobile width and repeat. Responsive duplicates only show up this way.
6. Trace each extra H1 to its source. Is it the theme header, a section, a block setting, an app, or the product description? That decides whether you fix one page or one template.

For a site-wide view, a crawler export filtered on "H1: multiple" gives you the list of affected URLs. Group them by template (product, collection, article, page) before you do anything. If every product page has two H1s, you have one bug, not 3,000.

How to fix extra H1s without changing the design

Start by deciding what the main title is. On a product page it's the product name, on a collection page the collection name, on an article the article title, and on the homepage it's whatever single line best describes the store. Everything else gets a level based on its relationship to that title, not on how big it should look.

Fixes by pattern

Here's what a clean product page outline looks like, using illustrative content:

• <h1> Linen Travel Shirt
• <h2> Materials and care, with <h3> Washing instructions underneath
• <h2> Size guide
• <h2> Shipping and returns
• <h2> Customer reviews
• <h2> You may also like, with each product card title as an <h3> or plain text

Make template fixes in a duplicate of your live theme, preview a product, a collection, an article and the homepage, then publish. Fixing the shared section once is faster and safer than editing hundreds of product descriptions. If you keep a hidden H1 for any reason, make sure its text is accurate, because screen reader users will hear it.

When an H1 warning deserves priority

Most "multiple H1" warnings are low priority. Treat them as urgent only when one of these is true:

• Google is showing the wrong title link. If search results show your brand name, a promo line or a section heading instead of the product name, the competing headings may be the reason. Google's documentation describes this exact case.
• The issue sits on a shared template. A broken heading in a product or collection template repeats on every page that uses it, which is where an audit should spend its time.
• The main H1 is empty or meaningless. An H1 with only a logo image and no useful alt text, or an empty H1 left by an app, gives both Google and screen reader users nothing.
• The outline is broken for accessibility. Two different H1s followed by skipped levels make the headings list hard to use, and that matters for every visitor who navigates that way.

If none of these apply, log the issue, fix it during the next template update and spend your time on things with a clearer link to revenue: indexation, internal links, product page content and speed. Our technical SEO audit checklist shows where heading structure fits among those checks, and whether blog headings should be questions covers how to word the H2s once the levels are right.

After you ship a fix, rerun the same URLs through the heading checker, check the headings list in a screen reader, and watch the title links for those pages in Search Console over the next few weeks. Don't expect a ranking jump from a heading fix alone. Expect a clearer page.

What to do next

Pick one product page and one collection page, run them through the checker, and trace every extra H1 to its source. If both come from the theme, fix the section once in a duplicate theme and you've fixed the whole catalog. If you want a second pair of eyes on your templates as part of a wider audit, our technical SEO team can help, or you can book a call.