H1 vs H2: A Page With No H1 Is a Page With No Title

H1 vs H2 sounds like a formatting detail until your page gets it wrong. An H1 is the one heading that tells everyone, a reader, Google, or an AI engine, what the page is about, and an H2 standing in for it is a subheading pretending to be a title. When the H1 is missing, the page still looks fine to you, because you can see the big text at the top. The machine reading the page can’t. It sees a hero styled to look like a title but tagged as something else, so it has no top-level label to hang the page on.

If the most prominent text on your page is an H2 (or a div, or a styled paragraph) instead of a real H1, that’s this problem. Here’s what it means and whether it’s worth fixing.

Why a missing H1 hurts AI traffic

Getting cited by ChatGPT, Perplexity, or Google’s AI Mode is a retrieval game. These systems break a question into parts, pull the chunks that answer them, and stitch a response together. To decide whether your page is even relevant, they lean on structure. The heading hierarchy tells them what the page covers and how it’s organized, and the H1 is a key structural signal in that hierarchy. No H1 means no clear answer to “what is this page for.”

Google lists the first visible H1 as one of several signals it uses to generate the title link, alongside the title tag, the main visual title, og:title, and other prominent text. When the H1 is missing, Google falls back to those other sources. Sometimes it guesses right. Often it grabs a navigation label, a tagline, or the wrong heading, and now your page is filed under the wrong topic.

There’s an accessibility angle too, and it matters more than it used to. AI agents increasingly read the page’s accessibility tree, the browser’s own semantic map of roles and names. A hero that’s visually huge but tagged as a plain element shows up in that tree with the wrong weight, or no weight. Screen readers hit the same wall: people who navigate by headings land on a page with no top-level entry point. The visual design hides the problem from you. The structure exposes it to every machine that reads the page.

What a correct heading structure looks like

One real H1 per page, holding the page’s main hero text, with the headings beneath it demoted so the hierarchy is clean: H1 for the title, H2 for sections, H3 under those. No skipped levels, no two competing top-level headings.

The visual design doesn’t change. This is a tag swap, not a redesign. The text that already looks like the title becomes the title in the markup too. To a visitor, the rendered page looks the same. What changes is the markup and the accessibility tree, which is what the machines actually read.

Which pages actually need an H1?

Fix this when:

• The page is one you want found and cited: a money page, a service page, a post, anything with a clear subject.
• The hero text is genuinely the title and just tagged wrong. This is the common case and a near-zero-risk fix.

Think twice when:

• The page is a special template (a full-screen landing page, an app screen, a gallery) where the “title” is really branding, not a topic. Forcing an H1 onto a page with no real subject doesn’t help.
• The fix would create two H1s. If the page already hides an H1 somewhere (some themes inject one you can’t see), promoting the hero gives you two competing titles. Check for that one first. The goal is one H1, not more headings.

Honestly, this is one of the cheaper fixes you’ll find. Low effort, low risk, and the downside of leaving it is that AI engines and Google keep guessing your topic. For most content pages, just fix it.

Once you’ve confirmed the hero text really is the page’s title, the change itself is a tag swap. Get AI Traffic applies it with set_content, which rewrites the page body so the title is a single H1 with clean heading levels beneath it, and doesn’t touch the visual design.

Frequently asked questions

What’s the difference between H1 and H2? The H1 is the page’s single top-level title, the one thing the page is fundamentally about. H2s are the section headings underneath it, each covering one part of that topic. An H1 missing, or an H2 doing an H1’s job, breaks that hierarchy, and both search engines and AI systems lean on it to figure out what your page covers.

Is a missing H1 really a problem if the page looks fine? Yes. “Looks fine” is a human judgment based on visual size. Search engines and AI agents read the tag, not the font. A 48px hero tagged as an H2 is, to them, a subheading with no parent.

Does Google require exactly one H1? No. Google tolerates multiple H1s and won’t penalize you for them. John Mueller has called header elements a “really strong signal” for understanding a page’s topics. Multiple H1s are technically allowed, but Search Engine Journal and every major SEO tool treat one H1 per page as best practice. One clear H1 is the safe choice.

Will adding an H1 make me rank or get cited? It’s a precondition, not a magic button. The H1 helps machines identify your topic correctly. Whether you then rank or get cited depends on the content, freshness, and authority. But a page they can’t categorize rarely wins either way.

Is this an SEO fix or an accessibility fix? Both. The same broken structure that confuses Google confuses screen readers and AI agents reading the accessibility tree. Fixing the H1 cleans up all three at once.

Sources

• Google Search Central: Influencing your title links in search results
• W3C WAI: Headings tutorial (page structure)
• Search Engine Journal: How to use header tags for SEO
• web.dev: Build agent-friendly websites (accessibility tree for agents)
• Semrush: How to optimize content for AI search engines