Heading Structure for SEO: H1-H6 Best Practices Guide

Let's settle the question everyone arrives with: how many H1s can a page have? The honest answer has two layers. In the HTML5 spec, multiple H1s are technically valid; the spec imagined that sectioning elements like <article> and <section> would create their own heading scopes. In practice, browsers never implemented that outlining algorithm, screen readers don't use it, and Google's John Mueller has said you can use multiple H1s but a single clear H1 is the cleaner signal. So the spec permits many; clarity argues for one. Use one H1 per page. Not because more than one breaks SEO (it doesn't), but because one unambiguous "this is what the page is about" beats a flat pile of equal-weight headings for every system that reads your page.

That last phrase matters: headings are read by systems, plural. Search engines use them to understand structure. Screen readers use them as a navigation map. And the second group is the one most "SEO heading" advice forgets.

Headings are an accessibility feature first

Before headings were ever an "SEO" topic, they were how blind and low-vision users navigate a page. A screen reader user can pull up a list of every heading and jump straight to the section they want, exactly like a sighted user skims bold subheadings. That only works if the hierarchy is logical.

This reframes the whole "don't skip levels" rule. Going from an H2 straight to an H4 isn't a search-ranking penalty; it's a broken rung in the ladder a screen reader user is climbing. They hit the gap and lose the sense of where they are. So:

✅ Logical nesting               ❌ Skipped level
H1  Page title                   H1  Page title
  H2  First major section          H2  First major section
    H3  A detail                      H4  Detail (where did H3 go?)
  H2  Second major section          H2  Second major section

Get the structure right for the screen reader, and you've automatically given search engines the clean outline they want too. Accessibility and SEO point the same direction here.

Headings are not a keyword field

Here's the correction that this article exists for: headings are not a direct ranking lever, and they are not a place to stack keywords. Google understands page content far beyond heading text now; cramming your target phrase into every H2 does not move rankings, and an obviously keyword-stuffed heading reads as spam to the humans you actually need to convince to stay on the page.

Compare:

• ❌ <h2>Free SEO Tools | Best SEO Tools | SEO Tools Online</h2>
• ✅ <h2>Which free SEO tools are worth your time</h2>

The second one tells a reader exactly what the section covers, and it still naturally contains the words someone might search. That's the whole technique: write the heading for the human skimming your page, and the keywords take care of themselves because they're genuinely what the section is about. A descriptive heading like "How to fix a redirect chain" beats a vague "Overview" every time, not because of keyword density, but because it sets a real expectation.

There's a real SEO payoff hidden in good headings, though, and it isn't ranking: question-style H2s that match how people search can win featured snippets. An H2 reading "How long should a meta description be?" with a direct answer right beneath it is exactly the shape Google lifts into a snippet. That's headings helping you indirectly, through structure that's easy to extract, not through the heading being a ranking factor.

A heading is structure, never styling

The most common technical misuse: reaching for an <h3> because you want text that's a bit smaller, or an <h2> because you want it bigger. Heading levels communicate hierarchy, not size. The moment you pick a level for its appearance, you've corrupted the outline that screen readers and crawlers depend on.

The rule is clean: choose the heading level by where the content sits in the document's logical tree, then use CSS to make it look however you want. Need a big eye-catching line that isn't actually a section? That's a styled <p> or <div>, not a heading.

A 30-second self-audit

Run this on any page you're unsure about:

1. Exactly one <h1>? It should name the page's main topic.
2. No skipped levels? Every H3 sits under an H2, every H4 under an H3.
3. Do the headings alone tell the story? Read just the headings top to bottom; they should form a coherent outline of the page. If they don't, your structure is off, not just your copy.
4. Any heading chosen for its size? Convert it to a styled non-heading element.
5. Any keyword-stuffed headings? Rewrite them as a plain description of the section.

Doing this by eye on a long page is tedious and easy to get wrong, since nested levels hide in the markup. Paste your URL into our Heading Analyzer and it extracts the full H1–H6 outline, flags multiple H1s, and shows you exactly where a level was skipped. For the broader picture of how headings sit alongside title tags and meta descriptions in a page's structure, that audit pairs well with checking your on-page basics too.

Frequently Asked Questions

Is it bad SEO to have more than one H1?

No, it won't hurt your rankings; HTML5 permits multiple H1s and Google handles them fine. But a single H1 gives the clearest "this is the page's topic" signal to both search engines and screen readers, so one is the recommended practice for clarity, not because extras are penalized.

Do headings directly improve my Google rankings?

Not directly. Headings help search engines understand your page's structure and help readers scan it, but heading text is not a standalone ranking factor. Their real value is indirect: clear structure improves usability, accessibility, and your odds of winning a featured snippet.

Why does skipping from H2 to H4 matter if it looks fine?

Because screen reader users navigate by heading level, and a skipped level breaks that navigation; they hit a gap with no context for where the H4 belongs. Search engines also expect sequential nesting. Visually it may look fine; structurally it's broken.

Should my H1 match my title tag exactly?

They don't have to be identical. The title tag is written for the search results page; the H1 is for visitors on the page. Keep them about the same topic, but the H1 can be longer or phrased differently for on-page readers.

Can I use a heading tag just to make text bigger?

No. Heading levels signal document hierarchy, not font size. Picking a level for its appearance corrupts the outline that screen readers and crawlers rely on. Use the correct level for the structure, then style it with CSS.

How many H2s should a page have?

There's no fixed number; use as many as the content needs, commonly a handful in a typical article. What matters is that each H2 marks a genuinely distinct section and that the headings together form a logical outline, not that you hit a particular count.