Dispatch
What Is an H1 Tag and Why Heading Hierarchy Matters for SEO
An H1 tag is the top-level heading element on a web page, the HTML markup (<h1>Your Heading Here</h1>) that identifies the main headline of the content below it. It sits...
On this page
An H1 tag is the top-level heading element on a web page, the HTML markup (<h1>Your Heading Here</h1>) that identifies the main headline of the content below it. It sits at the top of a six-level heading system, H1 through H6, that exists to give a page a logical outline, the same way a book has a title followed by chapter headings and subheadings.
The H1 is often confused with the title tag, but the two do different jobs. The title tag is metadata: it’s what shows up in the browser tab and, in most cases, as the blue clickable headline in search results. The H1 is visible, on-page content: the headline a visitor actually sees when the page loads. They commonly say something similar, since both are supposed to describe what the page is about, but they don’t have to be identical, and forcing them to match word-for-word is not a requirement.
Why Heading Hierarchy Exists
A page’s headings (H1, H2, H3, and so on) aren’t a styling tool, they’re a structural one. Used correctly, they create a nested outline: the H1 states the overall topic, H2s mark the major sections within that topic, H3s mark subsections within an H2, and so on. Search engines use that structure to understand how a page’s content is organized and how its sections relate to one another. People using screen readers rely on it even more directly: the W3C Web Accessibility Initiative’s heading documentation notes that headings let assistive technology users navigate a page section by section instead of reading it top to bottom, similar to how a sighted user scans a table of contents or skims bolded subheads. A properly nested structure (H2 before H3, H3 before H4, no level skipped without reason) is what makes that kind of navigation possible. The W3C’s technique H42 specifically documents using real <h1>–<h6> markup, rather than just styling regular text to look like a heading, as the correct way to identify headings programmatically.
One H1 Per Page: Practice, Not a Hard Rule
It’s worth being precise about what “one H1 per page” actually means, because it gets oversimplified often, and the common version of this nuance is itself out of date. Older SEO advice pointed to a “document outline algorithm” in the HTML5 spec, the idea that an H1 nested inside its own <article> or <section> got an effective, scoped heading level based on nesting depth, similar to a fresh chapter starting its own numbering. That algorithm was never actually implemented by any major browser, and the WHATWG removed it from the living HTML standard outright; even the leftover visual convention of browsers rendering a nested H1 at a smaller font size based on its sectioning depth was removed from the spec in 2025. Practically, every <h1> on a page today is read by assistive technology, and treated by search engines, as a literal, page-level heading 1, full stop, regardless of which element contains it. Multiple non-nested H1s remain syntactically valid HTML (the standard only requires that a page’s outline include at least one level-1 heading), but there is no longer any spec-based mechanism, real or theoretical, that makes a “second H1” behave like anything other than a second, competing top-level heading. The overwhelming convention, and the safer default for both SEO and accessibility, is a single H1 per page that clearly states what the page is about. Multiple H1s blur that signal: there’s no harm to a person or a crawler that can definitively be measured, but there’s also no upside, and a page with one unambiguous, well-matched H1 is easier for both users and search engines to interpret at a glance. Unless you have a specific structural reason for multiple H1s, default to one.
How the H1 Should Relate to the Title Tag
The H1 and title tag should typically be closely aligned, but “closely aligned” is not the same as “identical.” A reasonable pattern:
- The title tag is often written with search and click-through in mind: it has tighter length constraints (Google generally truncates long titles in search results), and it may include a brand name or a slightly different phrasing optimized for how people search.
- The H1 is written for the person already on the page: it can be more natural, more descriptive, and doesn’t need to account for SERP truncation.
For example, a title tag might read “Best Running Shoes for Flat Feet (2026 Picks) | BrandName” while the on-page H1 simply reads “Best Running Shoes for Flat Feet.” Same topic, same intent, different framing for different contexts. What matters is that both accurately represent what the page delivers, not that they’re a word-for-word match.
Common H1 Mistakes
| Mistake | Why it's a problem |
|---|---|
| Missing H1 entirely | Leaves both users and crawlers without a clear topic anchor for the page; common on poorly configured CMS templates or custom-built pages |
| Multiple, unrelated H1s on one page | Splits the page's topical signal and confuses the outline a screen reader user relies on |
| H1 that doesn't match page content or search intent | Creates a mismatch between what brought someone to the page and what they actually find |
| Styling regular text (a <!–INLINECODE6–> or <!–INLINECODE7–>) to <em>look</em> like a heading with CSS, without using real heading markup | Visually convincing but invisible to assistive technology and search engines, since neither reads CSS styling as a structural heading |
| Skipping heading levels (H1 straight to H3, no H2) | Breaks the logical outline; the W3C's heading guidance flags this as something to avoid because it disrupts in-page navigation for screen reader users |
| Using the H1 purely for keyword stuffing rather than a natural description of the page | Reads poorly to actual visitors and doesn't serve the structural purpose a heading is for |
E-commerce H1 Patterns
E-commerce sites tend to have two distinct H1 contexts that are worth treating differently:
- Category pages (e.g., “Women’s Running Shoes”) generally benefit from an H1 that names the category plainly and matches how people actually search for that category. This is the page collecting all the topical and link signals for that category, so a clear, singular H1 helps reinforce what the whole page, and the products on it, are about.
- Product pages typically use the product name and key distinguishing details as the H1 (e.g., “Nike Pegasus 41 Running Shoe, Men’s”), since that’s the literal subject of the page. Some platforms inject this from product-feed data automatically, which is convenient but worth spot-checking, since auto-generated H1s can end up truncated, duplicated across variants, or missing key distinguishing detail (like color or size) that would otherwise help differentiate near-identical product pages from one another.
A frequent failure mode on large catalogs is templated H1s that are identical or nearly identical across many product or category pages (a generic “Shop Now” or a category name with no further detail repeated site-wide). That doesn’t break anything technically, but it wastes the differentiating value an H1 is supposed to provide.
Auditing H1s at Scale
On a small site, checking H1s page by page is realistic. On anything larger, a site crawler is the practical approach. A crawler like Screaming Frog’s SEO Spider can export every page’s H1 (and title tag) in one pass, which makes it straightforward to spot pages with no H1, pages with multiple H1s, H1s that are duplicated across many URLs, or H1s that diverge sharply from the title tag in a way that suggests a templating bug rather than an intentional choice. Google’s own URL Inspection tool in Search Console is useful for confirming, page by page, how Google is actually rendering and reading a given page’s structure, which is a good way to catch cases where JavaScript rendering quietly strips or duplicates heading markup that looks fine in the page source.
The Practical Takeaway
An H1 is a structural signal, not a ranking trick. The version of “good H1 practice” that holds up is simple: one clear, accurate H1 per page, written in real heading markup (not styled text), describing what the page is actually about, loosely aligned with but not forced to duplicate the title tag, and checked at scale on larger sites so templating issues don’t quietly spread across hundreds or thousands of URLs. Everything else, from category-page conventions to accessibility benefits, follows from getting that basic structure right. If you manage more than a handful of pages, run a crawl for H1 count first, zero H1s and multiple H1s are both one-line crawler exports, and either one is worth fixing before anything else on this list.