What Is an H1 Tag? Getting Your Page Headline Right

Jul 19, 2026 · SEO Glossary

Open the homepage of the last site your agency built and look at the markup. If the company logo is wrapped in an <h1>, you're in good company — it's probably the single most common heading mistake on the web, baked into countless old themes. The logo says the brand name. The H1 is supposed to say what the page is about. Those are rarely the same thing.

What is an H1 tag? It's the HTML element that marks the main heading of a page — the visible headline a reader sees, and the strongest structural hint you can give search engines about the page's topic. It sits at the top of the heading ladder (H1 through H6) and, by long-standing convention, appears once per page describing what that page covers.

What is an H1 tag doing for SEO in practice?

Let's set expectations honestly, because H1s attract more mythology than almost any on-page element. Google has confirmed that headings help it understand page structure and topic, but a perfect H1 won't rescue weak content, and Google copes fine with messy headings. The H1 is a clarity signal, not a ranking cheat code.

Where it earns its keep:

• Topic confirmation. When the H1, the title tag, and the content all agree on the subject, Google's confidence in what to rank the page for goes up. When they disagree, you get muddier rankings and Google rewriting your snippets more often.
• Snippet fallback. Google frequently swaps a weak title tag for the H1 in search results. If your H1 is "Home", that's what searchers may see.
• Accessibility. Screen reader users navigate by headings; the H1 tells them where the page's content actually begins. This alone justifies getting it right.
• User orientation. Someone lands from search, scans for confirmation they're in the right place, and the headline delivers it — or they bounce within three seconds.

The multiple-H1 question, settled

HTML5 technically permits multiple H1s, and Google's John Mueller has said publicly that Google handles them without complaint. So the SEO panic about a second H1 is overblown. And yet I still recommend one H1 per page to every client, for reasons that have nothing to do with penalties: a single H1 forces editorial discipline (one page, one primary topic), keeps screen reader navigation sane, and makes automated quality checks meaningful. When a crawl of a 500-page site flags 40 pages with duplicate or multiple H1s, that's almost always a template bug worth finding — treat the "one H1" convention as a linting rule, not a law of physics.

Writing an H1 that pulls its weight

The mechanics are simple; the discipline is what's rare:

1. Describe this page, specifically. "Emergency Boiler Repair in Leeds — Same-Day Callouts" beats "Welcome" or "Services". Concrete beats clever.
2. Include the primary keyword naturally, once. If the page targets a term, the headline should contain it or a close variant. Don't bolt on three variations — that reads like 2012.
3. Differ from the title tag slightly. They serve different contexts: the title competes for a click on a results page; the H1 confirms and expands once the visitor arrives. Related, not identical, is the sweet spot.
4. Keep it scannable. No hard character limit exists, but headlines past ~70 characters usually mean you're writing a sentence, not a heading.

For homepages specifically — the page where "Welcome" headlines go to die — write the H1 as the one-sentence answer to "what does this company do and for whom." A design studio's homepage H1 reading "Web Design for Independent Restaurants" does more positioning work than most hero paragraphs.

The failure modes I find in real audits

Across hundreds of crawls, H1 problems cluster into a few recurring shapes:

• No H1 at all. Common on JavaScript-heavy sites where the visual headline is a styled <div>. Looks identical to users; invisible as structure.
• Same H1 sitewide. A template hardcodes the company name as every page's H1. I once audited an e-commerce site where all 1,200 product pages shared the H1 "Shop Online" — twelve hundred pages telling Google the same nothing.
• H1 used as a styling shortcut. Someone wanted big text mid-page, so a paragraph became an H1. Style with CSS classes; reserve heading tags for structure — this is really a heading hierarchy problem wearing an H1 costume.
• Empty H1s. An <h1> wrapping an image with no alt text, or left literally empty by a page builder. Structurally present, semantically void.

None of these are visible by eyeballing the page, which is the point: heading problems are markup problems. A site-wide crawl lists every page's H1 next to its title tag, so missing, duplicate, and empty headings surface in minutes instead of being discovered one view-source at a time. On redesigns especially, add the H1 column to your launch checklist — new themes are where sitewide heading regressions ship, and catching one before launch costs nothing while catching it three months later costs a quarter of ranking data.

A two-minute self-check

Right now, on your most important page: view source (or use DevTools) and find the H1. Does it exist? Is there exactly one? Does it describe this specific page in words a searcher would use? Does it roughly agree with the title tag? Four yeses and you're done here — go fix something harder. Any no, and you've found ten minutes of work with a genuinely favorable effort-to-benefit ratio.