Open any page on your site and count the headings. Now ask yourself a harder question: if you removed every paragraph and kept only the H2s and H3s, would a stranger understand what the page is about?
For most sites I've audited, the answer is no. Not because the writing is bad, but because the heading structure was never designed. It accumulated. Someone added an H3 for a promo banner, someone else used an H2 purely to make text bigger, and a plugin quietly injected two more H1s into the sidebar. The page still ranks, so nobody notices. Until it doesn't.
Getting headings right for SEO and readability isn't complicated, but it is unforgiving. The rules are simple; the edge cases are where everyone trips. Here's what actually matters.
Key Takeaways
- One H1 per page, and it should describe the page's actual topic, not your brand name
- Never skip levels: H1 → H2 → H3. Jumping from H2 to H4 confuses both screen readers and crawlers
- A heading every 200–300 words is a reasonable rhythm for long-form content
- Headings in menus, sidebars, and FAQ accordions count too — and frequently break hierarchy
- If your outline reads like a table of contents, you've done it right
Why heading structure matters more than most people admit
Headings do three separate jobs at once, and people usually only think about one of them.
For search engines, headings are the cheapest available signal about what a page covers and how its sections relate. For readers, they're the scanning mechanism — most visitors will read your H2s before deciding whether to read anything else. And for assistive technology, headings are navigation: screen reader users jump from heading to heading the way sighted users scroll.
That third job is the one I see neglected most. When I first started building pages, I treated heading tags as a styling tool. I'd use an H3 because it looked the right size. It took a screen reader demo — someone tabbing through one of my pages and landing on "Related articles" before the main content — for me to understand the damage. The structure I'd built communicated a hierarchy that had nothing to do with what the page said.
The scanning reality
Readers don't read. They scan, they stop, they read one section properly. Your headings are the only part of the page guaranteed to be seen. If your H2s are vague ("More information", "Our approach"), you've wasted the one element everyone actually reads.
What happens when you get it wrong
Broken hierarchy rarely causes a dramatic ranking collapse. It causes quiet degradation: your page gets associated with the wrong subtopics, featured snippets go to competitors with cleaner structure, and your click-through rate sags because your title and headings don't align. Nothing breaks. It just underperforms, and you never quite know why.
The heading hierarchy, explained with actual examples
Six levels exist. You will realistically use three, occasionally four.
- H1 — the page title. One per page. Describes the whole document.
- H2 — a major section. Think of these as chapters.
- H3 — a subsection inside an H2. Sub-chapters.
- H4 through H6 — rarely needed. If you're reaching for H5, your content probably belongs on its own page.
Here's a real outline, taken from a service page I restructured:
| Level | Heading | Purpose |
|---|---|---|
| H1 | Email deliverability consulting | Page topic |
| H2 | Why your emails land in spam | Problem framing |
| H3 | Authentication: SPF, DKIM, DMARC | Technical subsection |
| H3 | List hygiene and engagement signals | Second subsection |
| H2 | How the audit works | Process |
| H2 | Pricing | Commercial |
Notice the discipline: no level skipped, no H2 masquerading as decoration, and the outline alone tells you what the page offers. That's the test. Read only the headings — do you get the argument?
How to structure headings for both SEO and readability
Start with the outline before you write
Write the headings first, as a list, with nothing underneath them. If the list doesn't hold together, the article won't either. I do this on paper, and roughly a third of the time the outline collapses and I realise the piece has two topics, not one.
Once the skeleton works, fill it. This is the single highest-leverage habit I've adopted, and it costs nothing.
Balance keywords against clarity
Your H1 and main H2 should contain the phrase you're targeting — naturally, once. Not in every heading. Repeating an exact keyword across five H2s reads as manipulation to humans and adds no value for crawlers that already parsed your H1.
A workable split: target phrase in the H1 and one or two H2s. Semantic variations, related terms, and genuine questions in the rest. If a heading reads like a search query and nothing else, rewrite it.
How long should a section be?
Roughly 200–300 words between headings is comfortable for most topics. Shorter sections feel choppy; longer ones become walls of text that defeat the purpose. But this is a guideline, not a law. A dense technical explanation can run 500 words without needing a break. A pricing section might need three lines.
How many headings per page?
I aim for five to eight H2s on a typical article. Fewer and the page feels unpartitioned; more and you're probably fragmenting ideas that belong together. There is no penalty for a specific number — the penalty is for a structure that doesn't match the content.
The edge cases nobody talks about
This is where most audits find real problems.
Headings in menus and sidebars
Your theme likely wraps widget titles in heading tags. That means your sidebar could be injecting H2s or H3s into every page, competing with your actual content hierarchy. Check your markup. In my experience, roughly half of WordPress themes do this by default, and almost nobody notices until an accessibility audit flags it.
FAQ accordions and tabbed content
FAQ questions should be headings if they represent real subsections. But be careful: if your FAQ block sits inside an H2 section, the questions are H3s, not H2s. Duplicating H2s inside an accordion flattens your hierarchy.
Blog listing pages
Each article preview on a listing page will often carry its own heading from the template. If your theme outputs the post title as an H2, you now have fifteen H2s on one page, none of them related. Usually the fix is to downgrade preview titles to H3 or remove the tag entirely.
The heading audit I run on every page
- View source and search for every heading tag on the page — including widgets
- Count the H1s. If it's not exactly one, fix it today
- List the headings in order and read them alone
- Check for skips: any H2 followed directly by an H4?
- Ask whether each heading would make sense to someone who landed mid-page
- Confirm the target phrase appears once, in the H1
This takes ten minutes per page. It has caught more structural issues than any tool I've paid for.
Common mistakes and how to avoid them
Using headings for styling. The most frequent error. If you want big text, use CSS. The tag carries meaning whether you intended it or not.
Headings that say nothing. "Introduction", "Conclusion", "More details" — these waste the most valuable real estate on the page. Replace them with the actual point of the section.
Keyword stuffing. Three variations of the same phrase across consecutive H2s. It reads badly and adds nothing.
Ignoring mobile. Long headings wrap awkwardly on small screens. Aim for under 60 characters where you can.
The good news: fixing headings is cheap. You're editing text, not rebuilding a site. The less good news is that you have to actually look, and most of the time you won't like what you find. I certainly didn't.
Start with your five highest-traffic pages. Read the headings in isolation. If they don't tell a coherent story, you've found your next hour of work — and probably a few percent of organic traffic you'd been leaving on the table.
