H1
The primary heading of a page.
The H1 is the primary, top-level heading of a page's visible content — the largest, first heading a reader encounters, semantically distinct from the title tag that lives in the invisible <head>. Where the title tag is written for a search result and a browser tab, the H1 is written for the human already on the page, confirming they landed in the right place.
Every indexable page should have exactly one H1 that accurately describes the page's core topic, and it should be visually and semantically distinct from the title tag rather than a verbatim copy — though the two should closely align in topic so a searcher who clicked a title sees an H1 that confirms the match within the first second on the page.
The H1 is also a load-bearing accessibility element: screen readers use heading structure to let users navigate a page section by section, and a missing or duplicated H1 breaks that navigation model for anyone relying on assistive technology.
H1 vs title tag: what's actually different
The title tag optimises for the search result and browser context, where character and pixel budgets are tight and a searcher hasn't yet committed to the page. The H1 optimises for the on-page moment after the click, where the searcher has already committed and needs immediate confirmation they're in the right place — so the H1 can be slightly longer, more conversational, and doesn't need to squeeze in a brand suffix or geo-qualifier the way a title often does.
Duplicating the title tag verbatim as the H1 isn't harmful, but it wastes an opportunity: a slightly different phrasing that speaks more directly and conversationally to the on-page visitor tends to perform better for engagement than a mechanically duplicated heading.
Why heading structure matters for AI and accessibility
Generative answer engines parsing a page for extractable content lean heavily on heading hierarchy to segment a page into candidate answers — a clear H1 followed by well-labelled H2s and H3s makes it dramatically easier for an AI system to identify which section of the page answers which sub-question, increasing the odds of citation.
Screen readers and other assistive technology expose the heading outline as a navigation menu. A page with no H1, multiple H1s, or headings used purely for visual styling rather than semantic structure actively degrades the experience for users navigating by heading, which is both an accessibility failure and, increasingly, a quality signal search engines factor into evaluation.
Common mistakes
The most frequent H1 problems come from CMS themes and page builders that apply the H1 style to a logo or site name in the header on every page, meaning the actual topical heading further down the page is technically an H2 or unstyled text — a purely visual mistake with real semantic consequences.
- Logo or site name styled as H1 sitewide instead of the page's actual topic heading.
- Multiple H1s on a single page, confusing both crawlers and screen readers about the page's core topic.
- H1 used purely for visual size rather than semantic hierarchy, skipping straight to H3s or H4s below it.
- H1 that doesn't match the searcher's expectation set by the title tag, increasing bounce.
How to audit and fix H1 issues
Run a full site crawl (Screaming Frog, Sitebulb, or Search Console's URL inspection for spot checks) and export H1 counts per page. Flag pages with zero H1s, more than one H1, or an H1 that duplicates the site-wide header/logo text rather than describing the page's specific topic.
Fix template-level issues first — most H1 problems are a single theme or component fix that resolves hundreds of pages at once, rather than a page-by-page content problem.
Writing an H1 that earns the scroll
An H1 has roughly one second to justify the click. The strongest ones name the outcome the visitor came for rather than the category the page belongs to: 'Rank in the Austin Map Pack Within Two Quarters' does more work than 'Local SEO Services'. Keep it under about twelve words so it renders on two lines at mobile widths without pushing the primary call to action below the fold.
Avoid abstraction and internal jargon. Visitors scan for concrete nouns — a service, a place, a timeframe, a number — and skip adjectives such as 'innovative', 'holistic', or 'best-in-class' that every competitor also uses. If the H1 could sit unchanged on a competitor's page, it is not doing its job.
Keep the H1 in the server-rendered HTML rather than injecting it with client-side JavaScript after hydration. A heading that only appears after a framework boots is invisible to crawlers that render on a budget, and it delays Largest Contentful Paint on the exact element most likely to be the LCP candidate on a content page.
- State the outcome or the specific service, not the page category.
- Stay under roughly twelve words so mobile keeps the CTA above the fold.
- Include the geography when the page targets a location query.
- Ship it server-rendered so crawlers and LCP both see it immediately.
Local service-business application
A local service landing page's H1 should state the service and area in plain, natural language distinct from the title tag's more compressed, SERP-optimised phrasing — for example, title 'Roof Repair in Austin, TX | 24-Hr Response', H1 'Fast, Licensed Roof Repair Across Austin'. This confirms the match without simply repeating the tag, and reads more naturally to a visitor scanning the page.
H1 audit checklist
| H1 count per page | Exactly 1 | Multiple or zero H1s are the most common template-level defect found in crawls. |
|---|---|---|
| H1 vs title similarity | Related, not identical | Same topic, different phrasing performs better for on-page confirmation. |
| Heading hierarchy | H1 > H2 > H3 | No skipped levels; used semantically, not purely for font size. |
Frequently asked questions
- Can a page have two H1 tags?
- Technically HTML5 allows multiple H1s in different sectioning elements, but for SEO and accessibility clarity, one clear H1 per page describing its core topic remains best practice, since most crawlers and screen readers still treat the H1 as the singular top-level topic signal.
- Should the H1 be identical to the title tag?
- No, they should be closely related in topic but not identical. The title tag is written for the SERP and browser tab under a tight pixel budget; the H1 is written for the visitor already on the page and can be more natural and conversational while confirming the same core topic.
- Does the H1 tag directly affect rankings?
- It's a moderate on-page relevance signal, less influential than the title tag but still meaningful, and its bigger impact is often indirect — through user experience, accessibility, and how easily AI systems can extract the page's core topic and sub-answers.
- What's the most common H1 mistake?
- CMS themes styling the site logo or business name as an H1 in the header on every page, which means the page's actual topical heading is demoted to an H2 or unstyled text — a template-wide issue that's easy to miss without a full-site crawl.
Title tag: 'Emergency Plumbing Austin | 24/7 Service'. On-page H1: 'Need a Plumber in Austin Right Now?' — same intent, more natural on-page phrasing that confirms the click was correct.
Need this applied to your site?
We turn concepts like these into shipped work every week.