"No H1 Heading Found": Fixing the Most Common SEO Miss

If you scan enough websites, you start seeing the same handful of problems over and over. The one that surprised me most, when I started running GazeSite against real sites, was how many pages have no H1 heading. Not obscure pages. Homepages. Pages someone paid a designer for, pages with a big beautiful headline right at the top. The headline is there. The H1 is not.

That distinction is the whole story, so let me spell it out. HTML has six heading tags, h1 through h6. They form an outline: h1 is the title of the page, h2s are its major sections, h3s are subsections, and so on. The h1 is supposed to appear once and say what the page is about. But here’s the thing: nothing forces you to use it. You can take a plain div, style it with CSS to be forty pixels tall and bold, and it will look exactly like a heading to every human who sees it. To software, it’s nothing. It’s an anonymous box that happens to contain large text.

And software is a bigger part of your audience than it appears. A search engine crawler reads your HTML, not your pixels, and it uses the heading outline as one signal of what the page is about and how it’s organized. A screen reader, the software a blind visitor uses to browse, leans on headings even harder: a standard way to navigate is to jump from heading to heading, skimming the outline the way a sighted visitor skims the layout. And lately there’s a third reader, the AI assistants that summarize and answer questions from web pages; they too work from structure, not appearance. A page without an H1 tells all of these readers: this page has no title. Whatever the humans see, the machines see a document that never says what it is.

How do pages end up this way? Almost never through ignorance of what an H1 is. It’s usually drift. A designer builds the hero section, the styling gets attached to generic elements, and since it looks right, no one ever inspects the tags underneath. Or a developer uses h1 styling somewhere else and, to avoid a conflict, quietly demotes the real title to a div. Or a page template starts its headings at h2 because the h1 was in some header component that later got removed. Every one of these changes is invisible. The page looks identical before and after. That’s what makes this class of bug so common: it has no symptoms you can see.

Which is, incidentally, why I believe in auditing pages with software rather than eyeballs. Your eyes will tell you the page has a headline. Only the HTML will tell you whether it’s real. When GazeSite reports “No H1 heading found,” it’s reporting a gap between how the page looks and what the page says, and those gaps are exactly the ones humans can’t catch by looking.

The fix is usually pleasantly small. Find the page’s main headline, the text that answers “what is this page,” and make it an h1. If it’s currently a styled div or span, change the tag and move the styling to a class so it keeps looking the same. If your headline is an image or a logo, give the page a real text h1 anyway; a logo is a name, not a statement of what the page offers. Use exactly one h1. HTML5 technically permits more in some structures, but one is what search engines and screen reader users expect, and there’s no advantage in being clever here. Then let the rest of the headings form an honest outline underneath it: h2 for sections, h3 inside those, without skipping levels just because an h4 happens to look better. Style is the stylesheet’s job. Structure is the markup’s job. Most heading problems come from making one do the other’s work.

I should be honest about the size of the prize. Adding an H1 will not transform your rankings overnight; it’s one signal among many, and search engines are good at guessing when structure is missing. But guessing is the operative word. Every place you make a machine guess about your page, you accept whatever it guesses. The title it infers might be your tagline, your company name, or the first bold text it finds. The H1 is your chance to state, unambiguously, in your own words, what the page is about. It costs one tag. I have a hard time constructing an argument for making the machine guess instead.

There’s also a compounding effect I didn’t appreciate at first. The pages missing an H1 are usually missing other structure too: meta descriptions, sensible heading order, labeled sections. Fixing the H1 forces you to answer the question “what is this page’s one main statement,” and that question tends to improve the page beyond the tag. Sometimes the honest answer is that the page makes no main statement, and that discovery is worth more than any SEO tweak.

So look under the paint. View the source of your most important page and search for an h1. If it’s there and it says the right thing, good; you’re ahead of a surprising share of the web. If it’s not, you’ve just found the cheapest fix in SEO: one tag, ten minutes, and your page finally introduces itself.