How to Structure Headings H1 H2 H3 for SEO: A Complete Guide

How to structure headings H1 H2 H3 for SEO (and why most sites get it wrong)

Open any page on your site and count the headings. Nine times out of ten, they follow the same pattern: the H1 carries the page title, an H2 introduces each block of content, and the H3s… well, nobody quite remembers why they're there. They were added because the theme put them there, or because a plugin generated them, or because someone on the team said "subheadings help SEO" and nobody asked what that actually meant. That reflex is exactly where the problems start.

Heading structure is one of the few technical topics where you can see the damage in ten seconds, on your own site, without any tool. Open your browser, right-click on the page, and inspect the headings. You will find skipped levels, multiple H1s, headings used purely for styling, and — my favourite — an H3 floating above an H2 because the font size looked better that way. The structure is a hierarchy, not a design choice, and search engines read it as one.

What a heading tag actually does

Strip away the marketing and a heading tag does three things at once. It tells a screen reader what section it is entering, it tells a crawler how the page is organised, and it tells a human reader scanning the page whether this paragraph is worth their time. Three audiences, one element. That's why sloppy headings cost you more than you'd expect.

H1, H2, H3 — what the levels mean

The H1 is the page's main subject. There is normally only one, and it should say plainly what the page is about. The H2 marks a major section. The H3 marks a subsection inside an H2. The pattern continues down through H4, H5 and H6, though on a blog post you will almost never need anything past H3 — and if you do, it usually means the page should have been split in two.

Think of it as a book. The H1 is the title on the cover. H2s are the chapter titles. H3s are the sub-sections within a chapter. You would never open a book where chapter four sits inside chapter two's first paragraph, but that is exactly what a skipped heading level does to a crawler.

H4, H5, H6 sizes: what actually changes

Here is a question I get constantly, and it exposes the confusion nicely: what are the actual sizes of H1 through H6? The honest answer is that there is no fixed size. Browsers ship default styles — an H1 is roughly twice the body text, each level steps down from there — but any theme or stylesheet can override every one of those values.

I once spent an afternoon chasing a "broken" heading hierarchy on a client's blog. The H3s looked bigger than the H2s. Turned out the previous developer had styled them that way in CSS for a specific landing page and the rule leaked site-wide. The markup was perfect. The hierarchy was invisible to the reader. Visual size and semantic level are two different things, and conflating them is the root cause of most heading messes.

• A heading should be chosen for its level in the hierarchy, never for how large it renders.
• If a heading needs to look bigger, change the CSS class — an H4 styled as an H2 stays an H4 in the document structure.
• Headings are not font sizes. They are landmarks.

How many H1 headings should a page have?

Google's own position, stated publicly by John Mueller more than once, is that multiple H1s are not a problem — HTML5 allows headings inside sectioning elements, and the crawler handles it. So technically, you can have several.

I still recommend one. Not because a second H1 will hurt you, but because "we allow it" is not the same as "it helps you". When I audit sites with three or four H1s, they almost always turn out to be accidental: the site logo wrapped in an H1 in the header, the post title in another, a widget title in a third. That's not a strategy, that's drift. Fix the drift, keep one H1, and spend your energy on the H2s — they do far more work.

When multiple H1s genuinely make sense

There is one case where I don't argue: modular pages built from independent components, like a homepage assembling a hero, a pricing block and a testimonial section, each of which is a self-contained unit that might later be reused elsewhere. In that architecture, giving each component its own heading can be legitimate. Blog posts, service pages, product pages — none of them need this. One H1. Every time.

The hierarchy rules that actually matter

Forget the theory for a moment. Here is what I check when I review a page, in order:

1. Exactly one H1, containing the page's core topic in plain language — no keyword stuffing, no "|" pipes crammed with three location names.
2. Every H2 answers a question. If you can't phrase the section as a question a reader might ask, the section probably shouldn't exist.
3. No skipped levels. H2 goes to H3. If you need a fourth tier, you need a shorter page.
4. No empty headings. A heading followed by an image and no text is a heading doing nothing.
5. Headings that read as a table of contents on their own — cover the body copy and see whether the outline still makes sense to you.

The fourth one is my pet peeve. I've audited sites where the H2 was purely decorative — a section separator with no text beneath it, just a picture. The crawler reads a heading that leads nowhere. It's the structural equivalent of a signpost pointing at a wall.

H1 H2 H3 examples you can copy

Rather than abstract rules, here's the shape I use on almost every informational page I publish. It hasn't failed me in years, and it survives theme changes, redesigns and CMS migrations.

Level	Role	Example
H1	Page subject, stated once	How to structure headings H1 H2 H3 for SEO
H2	Major section, phrased as a question or benefit	How many H1 headings should a page have?
H3	Sub-answer inside that section	When multiple H1s genuinely make sense
H4	Rare. Detail inside an H3, or a step in a process	Step 3: verifying the outline after publishing

Notice the H4 row. You'll use it maybe once in twenty articles. If you're reaching for it more often, the page is trying to say too much. I learned that the hard way on a 4,000-word guide I wrote early in my blogging days — it had H4s inside H4s, and readers told me it felt like a legal document. They were right. Splitting it into three pages more than doubled the time people spent reading.

Does heading structure actually move rankings?

Honestly? On its own, no. I have never seen a page climb because someone fixed a skipped H3. Anyone who tells you headings are a ranking factor in isolation is overselling it.

What headings do is remove friction. They help the crawler understand which part of the page addresses which query, they help the reader find the paragraph they came for, and they make your content eligible for the kinds of rich results that reward clear structure. That is a second-order effect, and second-order effects compound. On two sites I've worked on, the change that followed a full heading cleanup — nothing else touched, same content — was a measurable lift in pages-per-session and a small but real improvement in how often those pages appeared for long-tail queries. Not dramatic. Consistent.

The myth of "headings are a ranking factor"

Headings are a signal, and signals feed into understanding. Understanding feeds into relevance. Relevance feeds into how you rank for the specific things people type into the search bar. It's a chain, and every link matters more than any single one of them. Fixing your headings won't rescue thin content. But thin content with a clean structure will always outperform thin content with a broken one.

The headline benefit nobody talks about

Here's a thought that tends to change how people approach this. A screen reader user navigating your page by headings is doing exactly what a crawler does: jumping from landmark to landmark, skipping the body copy. If your hierarchy is broken, you haven't just made life harder for a bot. You've made your content unusable for a real person who has no other way in.

That framing is worth more than any checklist. It's also the reason I stopped treating alt text, heading structure and link labels as separate tasks. They're the same task: making the page navigable for anything that reads structure rather than pixels.

So the next page you publish, before you touch the meta description or worry about the keyword density, open the editor and look at your outline. Is there one H1? Does it descend cleanly? Do the H2s read like the questions you'd want answered if you were the visitor? If yes, you're already ahead of most of the pages you're competing with — and you didn't need a plugin to get there.