H1, H2, H3 heading hierarchy for SEO

There's a quiet detail that decides much of how a page ranks: the heading hierarchy. Not the keyword, not the length, not the images—the headings. They're what the reader scans first, what the screen reader announces, what Google uses to build its internal map of the content and, increasingly, what AI Overviews extract to answer queries without the user ever opening the page.

This article goes beyond "use an H1 and then H2s." It gathers what the HTML specification actually says, what Google says, what the accessibility guidelines say, and how all of that lands in concrete decisions when a team writes content to rank.

A brief history that explains why there are six levels

HTML headings run from H1 to H6. It's not a 1990s whim: it comes from the first draft of HTML written by Tim Berners-Lee between 1991 and 1993 at CERN. Berners-Lee drew on academic formats and on SGML, where documents carried hierarchical levels to organize chapters, sections, and subsections. When HTML was standardized as HTML 2.0 (IETF, RFC 1866, November 1995), the six levels were already set.

HTML 4.01 (W3C, December 1999) kept them. HTML5 (W3C, recommendation October 2014) introduced the sectioning elements—<article>, <section>, <nav>, <aside>, <main>, <header>, <footer>—and proposed a conceptual change: the "outline algorithm" was going to allow each <section> to start with its own H1, and the browser would calculate the implicit hierarchy. The idea was elegant. It was never implemented. Browsers didn't build the outline. Screen readers kept reading every H1 as level 1 regardless of nesting.

In 2022, the WHATWG and the W3C explicitly recommended not relying on the outline algorithm and returning to the traditional model: one H1 per page, explicit H2-H6 hierarchy. The HTML Living Standard (maintained by WHATWG, the current normative source) states it clearly. That's the practice any serious SEO team follows in 2026.

The operational takeaway: ignore the old debate about multiple H1s with sections. One H1 per page. Explicit hierarchy below it.

What Google actually says

It's common to read contradictory claims about headings and SEO. The source closest to reality is what official Google spokespeople have said publicly.

John Mueller, Google's Search Advocate for over a decade, has repeated several consistent claims in his Office Hours and on X:

• There's no penalty for having multiple H1s, but the recommended practice is still a single one.
• Strict order matters less than logic. Jumping from H2 to H4 doesn't break anything technically, but it breaks comprehensibility.
• Headings are a context signal, not a standalone ranking factor. Google uses them to understand the content, not to "award points" to a page for using them.
• Descriptive phrases in headings are useful because they help the content be understood, both by humans and by processing systems.

This is complemented by what Google Search Central's official documentation says: use headings to introduce new sections, not to style text, and keep a coherent structure. The Search Quality Rater Guidelines—the manual Google uses to train its human evaluators—explicitly mentions that clear organization of information is an indicator of high-quality pages.

The practical translation: headings don't "rank" on their own. But pages with clear headings are better understood, create a better experience, and therefore achieve better organic performance indirectly.

Accessibility: the other half of the argument

Although headings are talked about as an SEO topic, their functional origin is accessibility. WCAG (Web Content Accessibility Guidelines), published by the W3C in versions 2.0 (2008), 2.1 (2018), and 2.2 (October 2023), includes these criteria at its AA level:

• 1.3.1 Info and Relationships: structural information must be programmatically determinable. In textual content, this is met by using real HTML headings (H1-H6), not styled bold text or large font sizes.
• 2.4.6 Headings and Labels: headings must describe the topic or purpose of the section they introduce.

Screen readers—JAWS, NVDA, VoiceOver on Apple, TalkBack on Android—offer the user a feature called a "headings list" or "headings rotor." It lets you navigate the page by jumping from heading to heading, reading only the titles to understand the structure before deciding where to dive in. For a blind user, a page without clear headings is like a book without a table of contents: technically readable, practically impenetrable.

This is where accessibility and SEO converge. Accessible pages are comprehensible pages. Comprehensible pages are pages that Google and the other engines understand better. The heading structure that improves accessibility also improves organic performance, almost as a side effect.

The operational rule, without ambiguity

Beyond the theory, the practice that ages best for normal web content:

• A single H1 per page. It describes the whole topic. It appears once.
• H2 for main sections. Each H2 opens a self-contained section of the content.
• H3 for subsections within an H2.
• Occasional H4, in long or highly structured pieces.
• H5 and H6 rarely needed. If you need them often, the page is probably too dense and should be split.

Quick test: if you read only the page's headings from top to bottom, you should understand what it's about. If you can't, the hierarchy is broken or the headings are too vague.

Headings, featured snippets, and AI Overviews

This is where hierarchy stops being just a comprehension topic and becomes a concrete visibility topic.

Featured snippets—the highlighted answer boxes that appear above the organic results—tend to extract text that immediately follows a well-formulated heading. If your H2 says "How to measure email engagement" and below it you have a clear answer paragraph, the odds of that fragment appearing as a snippet rise notably. If your H2 says "Metrics," the fragment Google extracts is generic and competes with hundreds of identical pages.

People Also Ask works similarly: Google identifies real user questions and matches answers with sections of pages that answer them. Headings phrased as questions—"How much time should you spend on a piece?", "Why do lower thirds fail?"—are direct candidates.

AI Overviews (the AI-generated answer that Google introduced at scale in May 2024 and expanded in 2025-2026) synthesizes information from several pages. The pages most frequently cited are the ones with a clear structure: heading-answer, heading-answer. The language models behind AI Overviews extract better from well-structured sources because they process text sequentially and headings act as topic anchors.

The takeaway for 2026: descriptive headings, phrased with the same search intent you hope to capture, are one of the few SEO optimizations that still works with AI Overviews—where other tactics have become invisible.

Mistakes that recur in every team

Multiple H1s "because it looks better." Breaking the hierarchy for design is breaking it for SEO. The solution is to separate style (CSS) from structure (HTML). An H2 can be displayed visually just as large as an H1 without being one in the code.

Generic H2s like "Introduction," "Conclusion," "Resources." They add no keyword or intent. Replace them with descriptive phrases: instead of "Introduction," "Why hierarchy matters for SEO."

Headings with no content below them. An H2 that opens a three-line section doesn't deserve to be one. Merge it with the previous one or expand it.

Duplicate headings across many pages. "Best practices," "Common mistakes," "Conclusion" repeated across 30 articles is a sign of a template, not thoughtful content. Varying the headings by specific topic reinforces the uniqueness of each piece.

Level jumps. Going from H2 straight to H4 without an intermediate H3 breaks the logical hierarchy. Some screen readers announce "level 4" where the user expected "level 3," creating confusion.

Bold text confused with a heading. A paragraph in bold and large size isn't a heading, it's styling. For SEO and accessibility, that "section" doesn't exist. If it's important, it should be a real heading.

Headings that don't promise what the section delivers. An H2 that says "How to measure engagement" and below it only describes what engagement is without measuring anything fails to keep its promise. The coherence between heading and immediate content is what makes a fragment work for a featured snippet.

Keyword stuffing in headings. Repeating the exact same keyword in five consecutive H2s doesn't help ranking and hurts readability. Varying with synonyms, different phrasings, and related subtopics produces a better experience and better organic performance.

Clickbait headings with no substance. "This will change the way you do SEO" works on social media but fails as an H2 inside a page. The user arrives expecting something concrete, and a vague heading disorients them.

Changing the hierarchy mid-page. A page that uses H2-H3 in its first half and H3-H4 in the second seems to have two documents glued together. Consistency all the way through.

Forgetting the H1 in visual CMSs. Some block editors (WordPress Gutenberg, Squarespace, Wix) can produce pages without an H1 if it isn't explicitly selected. It's worth verifying the final HTML, not trusting the editor.

Markdown, MDX, and modern CMSs

If you use Markdown or MDX (as Polimake.com does), the hierarchy is transparent: # is H1, ## is H2, ### is H3, and so on. The discipline is the same: a single line with a single # per file, everything else ## and below.

In traditional visual CMSs (WordPress, Drupal, Joomla), the hierarchy depends on the theme and the editor. It's worth reviewing existing pages with a DOM inspector or with extensions like HeadingsMap or Web Developer Toolbar to verify that the resulting hierarchy is the one you want.

In modern frameworks (Next.js, Astro, Nuxt, SvelteKit), the hierarchy is decided by the component template. Technical teams sometimes put the site name inside a global <h1> by default, which produces pages with two H1s without the writer knowing. Auditing global components—header, banner, breadcrumb—is important.

How to fit hierarchy into the workflow

The heading hierarchy shouldn't be decided at the end, once the body is already written. It's a decision for the brief: how many sections the piece will have, in what order, what question each one answers. This avoids the frequent pattern—"I write the article and then figure out how to divide it"—that almost always produces incoherent hierarchies and sections that don't fit.

On teams that produce a lot of content, a heading template by piece type helps. Blog posts, glossary articles, case studies, comparisons, and long guides can each have a recommended structure that reduces repeated decisions and maintains consistency. Templates aren't straitjackets—they adapt to the topic—but they provide a starting point that avoids reinventing the structure every time.

Another useful practice: reviewing the structure before starting to write. Listing the headings first as an outline, validating that the outline covers the intent, and only then writing the body. It turns the hierarchy into a conscious decision rather than an accident.

Creative operations is what sustains this discipline at volume. At Polimake, Studio defines the editorial architecture and the piece-type templates; Studio coordinates the calendar and approvals; Media executes production when associated visual material is needed.

Related concepts

• General SEO tips as broad territory.
• What keywords are that you should reflect in headings.
• What SEO means as general context.
• Editorial calendar for sustaining regular production.
• Content production with templates and review.

To wrap up

The heading hierarchy seems like a technical detail. In practice, it's one of the decisions that most influence whether a page is understood, ranks, and gets cited. Done well, it helps a user decide to stay in three seconds, a screen reader navigate it with dignity, Google understand its topic, a featured snippet rescue it, an AI Overview cite it.

What sets apart those who work it well isn't knowing more theory. It's having turned the decision into part of the writing process—not a correction at the end—and having resisted the temptation to use headings as a styling device. An H2 is a promise to the reader and to the machine. Keeping it consistently, in every piece, is one of the few things that still moves the ranking in 2026.

Quick references

• One H1 per page. It describes the whole topic.
• H2 for sections, H3 for subsections. H4-H6 rarely.
• Descriptive phrases, not labels. "How to measure engagement" beats "Metrics."
• Coherence between heading and immediate content—especially for featured snippets.
• Don't use headings as visual styling. Style goes in CSS; structure, in HTML.
• Verify existing pages with HeadingsMap or another outline tool.
• Audit global components of the CMS or framework to avoid unintended duplicate H1s.
• Headings as questions work well for People Also Ask and AI Overviews.
• Templates by piece type to sustain consistency at volume.
• Decide structure in the brief, not at the end of the process.