How Many H1 Tags Should a Page Have?

Google has said for years that it does not care how many H1s a page has. Your visitors, your screen-reader users, and your own editors do.

How Many H1 Tags Should a Page Have? — Troiana insight cover

In short

Use one H1 per page, containing the page's main topic in the words people search for. Google has stated repeatedly that multiple H1s are not a ranking problem, and HTML5 technically allows them, but a single H1 is the convention that screen readers, browsers, and editors all expect, and it forces the useful discipline of deciding what the page is about. Below it, use H2s for the main sections and H3s inside them, in order, without skipping levels.

The two true statements

Google does not penalise multiple H1s. John Mueller has said so on several occasions, in several ways: the ranking systems handle pages with many H1s, no H1, or headings in strange orders without difficulty. If your page has three H1s, it is not losing rankings because of that.

One H1 is still the right convention. Because the H1 is not only a signal to Google. It is the page's title as far as assistive technology is concerned, it is what browsers and reader modes use to name the document, it is what every editor and CMS assumes, and it is the single clearest statement of what the page is about. Multiple H1s make that ambiguous for everyone except Google.

The practical rule follows: one H1, and the argument about whether two would hurt is not worth having.

What the H1 is for

The H1 is the on-page headline. It should say, in words a searcher would recognise, what the page is about. On this page it is the question in the title. On a service page it is the service. On a product page it is the product name.

It usually mirrors the title tag but need not be identical; the title tag is written for the search result and can be tighter, while the H1 is written for the person who has already arrived and can be fuller. Both should contain the primary phrase, and they should not contradict each other.

The H1 is not the logo, not the site name, and not "Welcome". Those are the three most common misuses, and each wastes the one element on the page that most clearly announces the topic.

The structure underneath

Headings are an outline. A screen reader user navigates a page by jumping between them, which is why order and nesting matter more than the tag count:

  • H1: the page's topic, once.
  • H2: the main sections. On a long article, five to eight of them. Each should be a meaningful statement, not a single word.
  • H3: subsections within an H2. Use them when a section genuinely has parts.
  • H4 and below: rarely needed on a web page; if you are using them, the page may want splitting.

Do not skip levels. An H2 followed directly by an H4 is an outline with a missing entry, and both assistive technology and reader modes handle it badly. Do not use heading tags for styling; if you want large text that is not a heading, use CSS on a paragraph.

Why headings matter for search, if not for the count

Google uses headings to understand the structure and sub-topics of a page, and there is consistent evidence that content under a heading phrased as a question is what gets pulled into featured snippets and People Also Ask boxes. A page with clear H2s that match the sub-questions people actually ask is a page that can rank for each of them. That is where headings earn their keep, and it has nothing to do with how many H1s there are.

The same structure is what AI answer engines extract from. A clearly headed section that answers one question in its first sentence is the unit they quote.

Mistakes worth fixing

The logo in an H1. Common in older themes. The site name is not the page's topic; wrap the logo in a link or a div, and give the page a real H1.

No H1 at all. Page builders sometimes produce this. The page still ranks, but it has thrown away its clearest topic statement and its accessibility landmark.

Every heading is an H2. A flat outline with no hierarchy. Fine for short pages; on long ones, promote the section headings and demote the sub-points.

Headings chosen for style. "H3 looks nicer" is how outlines get broken. Choose the level by meaning and fix the appearance in the stylesheet.

Keyword repetition in every heading. Six H2s that each begin with the target phrase read as spam and help nothing. Use the phrase where it is natural, and let the sub-headings describe their sections.

Checking a page in a minute

Use the browser's accessibility tree, a headings bookmarklet, or the outline view in any SEO extension. You are looking for one H1 that names the topic, H2s that read as a sensible table of contents on their own, and no skipped levels. If the outline reads like a summary of the page, the headings are doing their job; if it reads like a random list of phrases, they are not.

If you would like the heading structure of your key pages reviewed alongside the rest of their on-page work, book a call; it is one of the quicker fixes on any site audit.

Common questions

Is it bad to have multiple H1 tags?

Not for Google rankings; Google has said repeatedly it handles multiple H1s fine. It is still poor practice because screen readers, browsers and editors treat the H1 as the page's single title, and multiple H1s make the page's topic ambiguous. Use one, and put the main sections in H2s.

Does the H1 have to match the title tag?

No, but they should agree. The title tag is written for the search result and can be shorter; the H1 is for the visitor who has arrived and can be fuller. Both should contain the page's primary phrase and describe the same topic. A title promising one thing and an H1 announcing another confuses readers and search engines alike.

Does the H1 tag affect SEO?

Modestly. Google uses headings to understand a page's topic and structure, and the H1 is the strongest of them, but it is one signal among many and not a ranking lever on its own. Its larger value is in featured snippets and AI answers, which favour clearly headed sections, and in accessibility.

Can a page have no H1?

It can, and it will still be indexed and can still rank. It has, however, given up its clearest statement of topic and the landmark that screen-reader users rely on to identify the page. Every page should have exactly one H1 that names what it is about.

Should the H1 include keywords?

It should include the page's primary phrase, written naturally as the page's headline. That is not stuffing; it is telling readers and search engines what the page is about. Avoid repeating the phrase across every subheading, which reads as spam and adds nothing.

Have something worth building right?