An H1 heading that ranks for a query doesn't have to be a perfect keyword-match sentence — but it does have to be the most important heading on the page, and many sites have multiple H1s, no H1 at all, or H1s that say "Home" because a CMS template set it up that way and nobody checked
The previous articles on this site covered competitive content research with heading extraction, accessibility and WCAG, AI extraction and question-formatted headings, and the visual-vs-semantic heading distinction. This article addresses H1 specifically — the rules and recommendations around the page title heading, the most consequential heading on any page, and the common implementation mistakes that audits consistently find.
The H1: what it should represent
The H1 is the primary heading of a page — semantically, it's the title of the main content section. In a well-structured page:
- There's one H1 per page
- The H1 reflects the page's primary topic (matching or closely related to the
<title>tag, but not necessarily identical) - Everything else on the page is a subtopic of what the H1 names
The <title> tag vs the H1 serve different purposes:
<title>: displayed in browser tabs, bookmarks, and search result listings — often includes the site name: "How to Bake Sourdough — The Bread Lab"H1: displayed on the page itself as a visible heading — typically just the content topic: "How to Bake Sourdough"
These can differ, and having them differ is normal. They should both accurately describe the page's content, but they're optimized for different display contexts.
The "one H1 per page" question: what the spec and what Google say
HTML5 technically permits multiple H1 elements per page — the specification introduced the concept of "sectioning content" (article, section, nav, aside elements) each having their own heading hierarchy, allowing H1 inside each section. In the sectioning model, a page could have multiple H1s, each scoping to its own section.
In practice, browser support for the sectioning model's heading hierarchy was never implemented correctly — screen readers and accessibility tools still process H1 elements as page-level headings regardless of their sectioning context. The outline algorithm described in HTML5 was ultimately abandoned and removed from subsequent HTML specifications.
Google's position: John Mueller has said Google prefers one H1 per page as the primary heading, but handles multiple H1s fine. He's characterized it as a "best practice" preference rather than a hard ranking requirement.
The practical recommendation: one H1, as the most prominent, topically relevant heading — not because multiple H1s break anything, but because multiple H1s usually indicate either: CMS template issues (the page title and the article title both using H1), or misunderstanding of heading hierarchy.
Common H1 implementation problems found in audits
No H1 at all: some CMS themes and page builders use styled <div> or <h2> elements for what visually appears as the page title, leaving the page without any <h1>. As covered in the previous visual-vs-semantic headings article, "looks like an H1" and "is marked up as H1" are independent properties.
Generic H1s from CMS templates:
<h1>Home</h1>on the homepage (the CMS using the page name as the heading)<h1>Blog</h1>on a blog category page instead of the actual category name<h1>Welcome to [Site Name]</h1>— a greeting rather than a topic description
These pass technical validation (there is an H1) but fail to serve the heading's informational purpose — neither users nor search engines understand the page's topic from these.
H1 not containing the primary keyword: while keyword stuffing is harmful, an H1 that uses completely different vocabulary from what the page targets (or what users search for) misses the basic alignment between search intent and heading content. The H1 should naturally describe the page's topic in terms that match how users think about that topic.
H1 buried below other headings: some page layouts show a visual "hero" area with large text (styled as H2 or a div), then the actual H1 appears lower on the page in smaller text. This creates a visual hierarchy mismatch — the most prominent text isn't the H1.
H1 length: what works for headings vs titles vs SEO
There's no strict character limit for H1 headings — unlike <title> tags, H1s aren't truncated in search results (they're not typically used directly as the displayed title in results). However:
Readability: very long H1s (beyond 70 characters) become unwieldy as visible headings on the page — they take up significant vertical space, may wrap awkwardly on mobile, and are harder to scan.
Specificity vs breadth: a very long H1 is often a symptom of trying to target too many keywords or concepts in a single heading. A focused page covering a specific topic should have a focused H1.
Common guideline: 20-70 characters for most H1s — long enough to be descriptive, short enough to scan easily.
How heading extractors reveal H1 implementation issues
Running a heading extractor on your own pages reveals patterns that are otherwise easy to miss:
- Pages with no H1 in the extracted structure
- Pages where the extracted H1 is "Home" or another generic value
- Pages with multiple H1s (indicating the heading hierarchy issue described above)
- Pages where H1 appears much lower in the heading hierarchy than H2 or H3 elements that precede it structurally
For template-driven sites (WordPress, Shopify, etc.): the H1 is often generated dynamically from a template variable. Auditing the template is more efficient than page-by-page checking — find where <h1> appears in the theme templates and verify the variable it outputs is the page's primary topic title, not the site name or a generic category term.
How to use the Heading Extractor on sadiqbd.com
- For your own pages: extract headings to verify there's exactly one H1, that it accurately describes the page's primary topic, and that the heading hierarchy is logical (H2s under H1, H3s under H2, no skipped levels)
- For competitor research: extract headings to understand how well-ranking pages structure their content — H1 choice and H2 structure often reveal topical organization decisions worth analyzing
- For site audits: running the extractor on multiple pages reveals template-level issues (every page has the same generic H1) vs content-level issues (individual pages have weak headings)
Frequently Asked Questions
Does Google use the H1 as the title in search results?
Sometimes, but not reliably. Google generates search result titles from multiple signals — the <title> tag, the H1, Open Graph title tags, and other on-page text. When the <title> tag is missing, too short, or too long, Google often uses the H1 as a substitute. When the title and H1 are in good shape, Google typically uses the <title> for the result listing. This isn't a reason to make H1 and <title> identical — they serve different contexts and can legitimately differ. But it does mean that H1 content can affect what appears in search results when <title> isn't suitable.
Is the Heading Extractor free? Yes — completely free, no sign-up required.
Try the Heading Extractor free at sadiqbd.com — extract the complete heading structure of any web page instantly.
