H1-H6 heading structure

Headings are the skeleton of your page. They tell Google what the page is about at a structural level. They tell users where they are when they scan. They tell screen readers how to navigate for people who can't see the page. Done right, a heading structure triples the ranking surface of a page and dramatically improves readability. Done wrong, you get cluttered pages that nobody reads and Google misunderstands. This page walks through the rules, the query-capture trick that most SEOs miss, and the common mistakes that waste the chance.

The mental model: your page is an outline

A page with good headings reads like a table of contents. You can scan the headings alone and understand what's covered, in what order, at what depth. Google reads that outline to understand the page's topic structure. Users read it to decide where to jump in. Screen readers use it as the primary navigation tool.

A page without good headings is a wall of prose. Google has to work harder to figure out what it's about. Users skim, miss what they came for, and bounce.

The heading hierarchy rules

• Exactly one H1 per page. It matches the page topic and includes the primary keyword naturally.
• H2s for major sections. Most articles need 3 to 8 of them. Fewer and the page feels dense. More and it fragments.
• H3s for subsections. Use only if the H2 section genuinely needs breaking down.
• H4 to H6 almost never. If you need them, your page structure is probably too deep.
• Don't skip levels. H1 directly to H3 breaks the hierarchy Google and screen readers rely on.

H1 best practices

• Include the primary keyword, near the front, reading naturally.
• Differ slightly from the title tag. The title is for the SERP. The H1 is for the reader who's already arrived.
• Keep it to 6 to 12 words typically. Longer H1s feel like subtitles, not headlines.
• Exactly one. Two H1s on a page confuse Google and screen readers.

H2s as query capture, the underused SEO weapon

Every H2 on your page is a chance to rank for a related query. If a user searches "how long should a blog post be" and your H2 is literally "How long should a blog post be?", you dramatically increase your chance of ranking for that variation. You also become a strong candidate for the Featured Snippet.

Two moves to exploit this:

1. Mine PAA questions. Google "your primary query." Note the People Also Ask questions. Use them verbatim as H2s on your page.
2. Answer immediately under each H2. Put a direct 40 to 60 word answer right below the H2. Google pulls those into PAA boxes and snippets.

This single trick can turn a page that ranks for 5 queries into a page that ranks for 40.

Headings and accessibility

Screen readers for blind users navigate almost entirely through headings. A clean H1 to H2 to H3 hierarchy lets them jump around a page the same way a sighted user skims.

Good news: the same heading structure that helps SEO also helps accessibility. Bad news: headings used only for visual styling, like wrapping a decorative bold phrase in an H3, break both.

Common mistakes

Tools that audit your headings

• SEO Meta in 1 Click. Browser extension that shows a page's heading tree.
• Screaming Frog. Crawls your whole site and reports heading issues at scale.
• Chrome DevTools Accessibility tab. Shows how a screen reader would interpret your heading structure.
• Ahrefs and Sitebulb. Site-wide audits include heading-level reports.

What to do with this

Pull up your top-ranking content and check the headings. If every H2 is a generic section label like "Overview" or "Features," rewrite them as actual queries your audience might search. Watch your long-tail rankings rise. Thirty minutes of heading work is often worth more than a week of new content.

Next: URL structure, one of the most permanent on-page signals and the one hardest to change later.