H1 Tags: What Google Says, and What Six Ranking Pages Ship

The page ranking second in the United States for "h1 tag" serves six H1 elements, five of which are navigation panel titles. It is also one of the sources cited in the AI Overview above it, at the same URL. Whatever the one-H1 rule is enforcing, it is not visible in these results.

An H1 is the top-level heading element on a page, the one that names what the page is about. The rule most audits enforce, exactly one per page, is not Google's rule. On 1 November 2026 we fetched ten URLs from an Ahrefs United States results snapshot for the query and counted the heading elements each one served. Six returned the page; five of those six had exactly one H1.

What we measured, and how

The snapshot, dated 10 October 2026, holds thirteen distinct URLs: eight organic results and ten AI Overview sitelinks, with five appearing in both roles. We fetched all eight organic results plus the two sitelink-only URLs that are ordinary articles, moz.com and shopify.com, which is ten. Three sitelink-only URLs were not fetched.

Each request used an ordinary desktop browser user agent, and we counted raw <h1> and <h2> elements in the HTML that came back, navigation included, without rendering JavaScript. Four of the ten answered with HTTP 403 and a bot challenge instead of the page. That is a limit of the method, not a finding about those sites. Counts come from a single fetch and can differ between fetches of the same URL.

What Google actually says about headings

Google's SEO starter guide, last updated 10 December 2025, is brief on the subject, and what it says contradicts most heading advice published elsewhere.

• On purpose: "provide headings to help users navigate your pages".
• On 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."
• On quantity: "There's also no magical, ideal amount of headings a given page should have. However, if you think it's too much, then it probably is."

There is no statement in that guidance that a page should carry one H1, that an H1 must contain the target keyword, or that skipping from H2 to H4 costs rankings. The accessibility argument for a sane heading order is real and Google endorses it in the same sentence. The ranking argument is not one Google makes.

Finding 1: five of six readable pages ship exactly one H1

Of the six pages that returned HTML, five serve a single H1 and one serves six. Every organic result in the set comes from a domain Ahrefs rates between 82 and 96, so this is a results page decided between strong domains rather than one where a heading count is doing the sorting.

Page	Position	H1	H2	Ahrefs DR
w3schools.com/tags/tag_hn.asp	2	6	18	92
developer.mozilla.org heading elements	4	1	11	96
acquia.com title tags vs h1 tags	5	1	10	82
semrush.com/blog/h1-tag/	6	1	7	92
martech.org h1 tag best practices	7	HTTP 403		83
indeed.com h1 vs h2	8	HTTP 403		92
searchengineland.com/guide/h1-tag	9	HTTP 403		91
seranking.com html heading tags	10	1	7	86
shopify.com/blog/h1-tag	AI Overview source	1	15	not reported
moz.com/learn/seo/h1-tags	AI Overview source	HTTP 403		not reported

Position 1 in the snapshot is an AI Overview and position 3 is a block of related questions, which is why the organic positions start at 2 and skip 3. Sitelink rows carry no Domain Rating in the snapshot, which is why those two cells are empty rather than zero.

Finding 2: the page at position two has six H1s

The w3schools reference page carries six H1 elements. Five of them are the titles of navigation panels, carrying the class names tutnav-main-title, refnav-main-title, exnav-main-title and certnav-main-title: "Tutorials" twice, then "References", "Exercises" and "Get Certified". Only the sixth is the content heading.

That page ranks second organically, Ahrefs estimates about 1,250 monthly United States organic visits to the URL across every keyword it ranks for, and the same URL appears among the sources cited in the AI Overview at the top of the results page.

A heading count is a property of a template, not a measure of quality.

H1 and title tag are different fields

Both can carry the same text, and often should, but they are separate fields serving different readers: the title tag is read in the results page before the click, the H1 after it. Google's starter guide also says it draws on "other headings on the page" as one input when it generates the title link, so the two are related without being interchangeable.

The two pages where we recorded the title tag as well show both approaches. Semrush uses an identical string for each: "What Is an H1 Tag? Why It Matters & Best Practices for SEO". SE Ranking does not: its title tag reads "HTML Heading Tags: SEO Basics About H1, H2, H3 You Can't Ignore" while its H1 reads "Mastering HTML H1 and Other Heading Tags for Better Search Rankings".

Google's advice on titles applies to both: "a good title is unique to the page, clear and concise, and accurately describes the contents of the page." Writing a title for the results page and an H1 for the reader who arrived is a legitimate choice. A title that promises something the H1 does not deliver is not. Our guide to writing title tags covers the other half of that pair.

An AI Overview sits above all of it

The snapshot's position 1 is an AI Overview citing ten sources, among them w3schools, MDN, Semrush, Acquia, Moz, MarTech, Shopify and vdigitalservices. The first ordinary blue link is position 2.

Part of the competition on a query like this one is therefore for being quoted rather than only for being ranked, and clear headings serve that directly: a heading is how an engine locates the passage that answers a question. Our work on making a passage quotable and on how AI Overviews choose sources covers what that takes.

What to do with your own headings

Four rules, in the order they pay off.

1. Give every page one obvious content heading. Not because a tool demands it, but because a reader landing mid-page needs to know where they are. Whether your template also emits H1s inside a menu is a separate question with a lower priority.
2. Write the H1 for the reader who just clicked. It should confirm that the promise in the search result was kept.
3. Use H2s for the questions the page answers, and answer each one in the first sentence beneath it. That serves skim readers and the engines lifting passages.
4. Fix heading order for accessibility, and do not expect a ranking change from it. Google says the order does not matter to Search, and says in the same sentence that it matters to screen readers.

What this does not prove

Ten URLs on one query is an illustration, not a study. Four of the ten could not be read, and three sitelink-only URLs were never fetched, so the sample is not the whole results page. The positions come from a snapshot dated three weeks before the fetch, so the page has moved since. Counting raw elements in served HTML also counts headings a reader never sees as a page heading, which is exactly how w3schools reaches six.

Nothing here shows that extra H1s help. It shows that six of them did not stop a page ranking second and being cited in an AI Overview, on a results page where every organic result came from a domain rated 82 or above.

If your audit tool is flagging heading counts across hundreds of pages, that list is worth reading for template bugs and worth deprioritising as a ranking project. Our piece on audit findings that are not problems covers how to tell the difference, and the technical SEO checklist places heading checks where they belong in the queue.