Skip to main content
SEO & Writing

Heading Hierarchy h1–h6: The Rules That Actually Affect Rankings

Run any SEO crawler over a site and you will get a wall of heading warnings: no h1, multiple h1s, skipped from h2 to h4, a heading that is just an image. Some of those warnings point at real problems. Most do not. Google's own documentation says headings help it understand page structure — it never says you need exactly one h1, and John Mueller has said outright that a page can rank fine with several h1s or none styled as expected. But heading hygiene still matters, for three concrete reasons: headings are a relevance signal, they feed featured snippets and AI answers, and they double as your page's accessibility outline. This article separates the rules that carry weight from the ones that mostly waste a sprint.

The one rule that actually carries weight

One h1 per page that accurately names the page topic. That is it. Not because multiple h1s break anything — they don't — but because in practice, a page with one clear h1 usually has a coherent topic, and a page with six h1s usually doesn't. The h1 is your strongest on-page relevance hint after the title tag. Write it as a natural sentence, not a keyword dump. If your h1 could be read aloud as the answer to "what is this page about", it is doing its job.

Two things about the h1 that are genuinely overrated: matching it exactly to the title tag (a slight variation is fine and often better, since the title competes in the SERP while the h1 competes on the page), and worrying about it being first in the DOM. Rendered order is what Google evaluates; a visually-first heading is fine even if the markup nests it deeper.

Skipped levels: a warning, not an error

Dropping from h2 to h4 looks wrong in an audit report. In ranking terms it is close to harmless. Screen readers handle skipped levels fine — they announce the level and move on. Google extracts the heading text and moves on too. The real cost is different: a heading structure with gaps usually means the document outline itself is muddled, and a muddled outline means the author wasn't clear on what the sections were. Fix the outline, and the level gaps fix themselves.

The case where it does matter: design-driven heading abuse. A marketing page uses an h3 somewhere purely because the font size looked right in the mockup, then the developer carries the pattern to the next section, and soon the "document outline" is actually a CSS style sheet pretending to be semantics. This is the one skipped-level scenario worth fixing — not for ranking, but because the outline stops describing the content, and both Google's extraction and assistive tech lose the plot.

Headings are a relevance signal — so write them like one

Heading text is weighted heavier than body text. Not as much as the title, but enough that the difference shows up. Practical version: put the entity you want to rank for in your h2s, in natural phrasing. A guide about heading hierarchy should have h2s mentioning "heading hierarchy", "h1", "semantic HTML" — not "Introduction", "Why It Matters", "Conclusion". Generic h2s waste the strongest slots on the page. If every h2 on your blog is "Benefits", "How to", and "FAQ", Google has almost nothing structural to latch onto. This is one of the few heading rules with a measurable effect.

Featured snippets and AI answers read your outline

Both traditional featured snippets and AI-generated answers lean heavily on document structure to pick what to quote. A well-structured page with a question-shaped h2 followed by a direct 40–60 word answer under it is the classic snippet bait. If your content covers the topic but buries the answer mid-paragraph under a generic heading, you lose these placements to worse content that is better structured. Restructuring an existing article into question-form h2s — the query itself as the heading, a concise answer right below — regularly lifts a page into snippet positions without any new content being written.

Accessibility: the outline you get for free

Screen reader users navigate by headings the way sighted users skim. WCAG requires headings to describe topic or purpose, and a logical structure. If your headings are an SEO afterthought — vague, generic, or faked with bold paragraphs — you are forcing screen reader users into the same guessing game that skim-readers escape by seeing your layout. The fix is identical to the SEO fix: descriptive headings in a logical order. Write your heading outline in a plain text editor first, and if it reads like a table of contents, you have it right. If it reads like a collection of section badges, you don't.

The checklist

  • Exactly one h1 per page, a natural sentence naming the page topic.
  • h2s are question-shaped or entity-ful — carry your target phrasing naturally.
  • Answers to those h2 questions appear directly under the heading in 40–60 words.
  • No h-for-font-size. If text is decorative, it's a paragraph or a span with CSS.
  • The outline, read alone, should summarize the page like a table of contents.
  • Skipped levels: fix if they reveal an outline problem, otherwise don't block a ship.

Auditing your own pages

You don't need a crawling subscription to check this. Paste a URL into our h1-h6 checker and you get the outline as the browser sees it: level order, duplicates, empty headings. For the snippet-side effect, check how your headings actually render in search results with the SERP preview tool — a heading that reads like a section badge in the SERP reads like one to Google too. And if you are restructuring a page around new section titles, the title generator helps you produce focused variants for h1s and meta titles without drifting into keyword stuffing — sanity-check the direction of what you write. Finally, once a heading structure exists, keep h2s and their supporting text aligned: if the section grew in draft, check length and keyword balance with the keyword density checker pro so the natural phrasing you just fixed doesn't creep back into stuffing.

Everything on that list is one afternoon of work on a typical site — and unlike most heading "optimizations", it targets the parts of the system that demonstrably consume heading structure.