Skip to content
HyperDAF editorialOn-Page SEO

Heading Structure (H1, H2, H3) for SEO: The Right Way

The first time a screen reader user emailed me about my blog, I felt my stomach drop. “Your articles are great,” she wrote, “but I can’t navigate them. Your headings…

Featured image for Heading Structure (H1, H2, H3) for SEO: The Right Way
On-Page SEOEditor-curated guide
14 min9 sectionsIntermediate
Before you beginWhat this guide gives you
9Focused sections14Minutes to finishIntermediateExperience level5Article views
Start reading
Table of contents9

The first time a screen reader user emailed me about my blog, I felt my stomach drop. “Your articles are great,” she wrote, “but I can’t navigate them. Your headings are all over the place.” I opened one of my posts and looked at it the way her software would: the “headings” were just bold paragraphs. There was no structure at all. To her, my 2,000-word guide was one giant wall of text with no doors.

That email changed how I write. Headings are not decoration. They are the skeleton of your page — the thing that tells Google what your content is about, tells readers where they are, and tells assistive technology how to navigate. Get them right and everything gets easier: rankings, readability, even AI search citations. Get them wrong and your brilliant content sits in a pile nobody can climb.

In this guide, I will show you the exact heading structure I use on every article: one H1, chapters as H2s, details as H3s — never a skipped level, never a vague label. I will show you the five heading mistakes I see on almost every site I audit, and a simple audit you can run on your own content today. If you publish anything on the web, this is for you. Let’s build pages with bones.

Abstract 3D illustration of a layered pyramid of descending geometric blocks representing heading hierarchy.

Here is why this matters more in 2026 than it ever did: AI search systems — Google’s AI Overviews, chatbots, answer engines — use your headings as the cut lines to chunk and cite your content. When an AI system decides which part of your page answers a question, it reads your headings first. Vague headings like “Overview” or “Tips” get skipped by readers and machines alike. Descriptive headings get cited. Your heading structure is now your ticket into the AI answer box, and most sites are still buying the wrong ticket.

In this guide, you will learn:

  • What H1, H2, and H3 tags actually do (and what H4–H6 are for)
  • The one-H1 rule and why it still matters
  • How to nest headings like a book: title, chapters, sections
  • The never-skip-a-level rule (and the screen reader reason behind it)
  • How to write headings that work for SEO, readers, and AI citations
  • The five heading mistakes I find on almost every site audit
  • A 15-minute heading audit for your own content

Ready? Let’s get started.

What H1, H2, and H3 Actually Mean

Forget the word “header” for a moment and think “outline.” Headings are HTML tags — H1 through H6 — that label the sections of your page in a hierarchy. The number signals importance. Here is the plain-English version:

H1 is the page’s main topic. The cover title of the book. There is exactly one per page, and it tells everyone — Google, readers, screen readers — what this page is fundamentally about. On a blog post, it is usually the article title.

H2s are the chapters. They break the H1 topic into its major sections. A typical 2,000-word article has 5 to 8 of them. Each H2 should make sense on its own — if someone read only your H2s, they should get the gist of the whole article.

H3s are the sections inside a chapter. They subdivide an H2 into specific points. Not every H2 needs H3s — only the ones with enough depth to deserve subsections.

H4 through H6 exist for deep nesting in long technical documents. Most blog posts never need them. If you find yourself reaching for H5, your content probably needs restructuring, not deeper headings.

The critical insight: heading levels show relationships, not sizes. An H3 is not “a smaller-looking heading than H2.” It is a sub-point *of* the H2 above it. Never pick a heading level because you like how it looks — that is what CSS is for. Pick it because of where the content sits in the outline.

Abstract 3D illustration of an open book with chapter blocks floating above it.

The One-H1 Rule (Yes, Still)

Technically, modern HTML allows multiple H1s on a page. Practically, for SEO and clarity, the rule stands: one H1 per page, always. Here is why I still enforce it on every site I touch.

Your H1 is your page’s thesis statement. When there are two or three of them, there is no thesis — there is a debate. Google has to guess which topic is the main one. Screen reader users, who often pull up a list of headings to navigate, see multiple “main topics” and lose the map. And honestly, if you need two H1s, you probably have two pages crammed into one.

In WordPress, this gets messy because of themes. Many themes automatically make your post title the H1 — which is correct. The mistake happens when a page builder or a well-meaning site owner adds another H1 inside the content because it “looks right.” I have audited sites with four H1s on the homepage: the logo, the hero headline, a section title, and the footer tagline. Google saw four competing main topics.

The audit is simple: view any page, and check that exactly one H1 exists and that it matches the page’s primary keyword and intent. Your SEO plugin or a free heading-checker browser extension shows this in seconds. If your theme outputs the H1 automatically, never add another H1 in your content — start your sections at H2.

Nest Like a Book: The Structure That Always Works

Here is the mental model I give every writer I work with: your page is a book. The H1 is the title on the cover. Each H2 is a chapter. Each H3 is a section within that chapter. Google reads your page the same way a reader reads a book’s table of contents — and increasingly, so do AI systems.

A correct structure looks like this:

H1: How to Bake Sourdough Bread → H2: What You Need Before You Start → → H3: The Starter → → H3: The Flour → H2: Mixing and Folding the Dough → → H3: The Autolyse Step → → H3: Stretch and Fold Technique → H2: Baking Day → H2: Troubleshooting Common Problems → → H3: Dense Crumb → → H3: Burnt Crust

See how every H3 belongs to the H2 above it? “The Starter” is part of “What You Need Before You Start” — not floating free. That parent-child relationship is the whole game. When the relationship is clean, Google understands your content’s structure instantly, and your table of contents (if you use one) writes itself.

Here is the part most guides miss: your headings are your outline, so write the outline first. Before I write a single paragraph of a new article, I write all the headings. Then I read just the headings. If they tell the full story of the article on their own — the promise, the steps, the payoff — the structure is sound. If they read like “Introduction… Details… More Details… Conclusion,” I rewrite them before writing anything else. This one habit has improved my articles more than any SEO trick I know.

Abstract 3D illustration of stacked geometric levels connected by glowing lines forming an outline tree.

Never Skip a Level (The Rule With Teeth)

This is the rule people break most often, usually by accident: jumping from an H2 straight to an H4 because the H4 “looked better,” or from H1 to H3 skipping H2 entirely. The hierarchy must step down one level at a time: H1 → H2 → H3. Never H1 → H3. Never H2 → H4.

Why does this matter so much? Two reasons, and the second one is the one that changed my mind forever.

First, skipped levels confuse the content relationships. An H4 sitting directly under an H2 with no H3 between them is like a book with Chapter 1 followed by Section 1.1.1.1 — the reader cannot tell what belongs to what. Search engines build the same kind of outline, and gaps in it make your structure unreliable.

Second, screen readers announce heading levels as navigation. A blind user pressing the “next heading” key hears “Heading level 2: Mixing and Folding” then “Heading level 4: Stretch and Fold Technique” — and the jump from 2 to 4 tells them they missed something. They did not miss anything; the structure lied to them. That email I got at the start of this guide? This was exactly her problem. I fixed my headings that same week, and I have never skipped a level since.

Bonus Tip: If a heading level looks wrong visually, fix it with CSS, not by changing the tag. In the WordPress block editor, every heading block can be styled independently of its level. Structure is meaning; appearance is paint. Never mix them up.

Writing Headings That Rank, Read, and Get Cited

A structurally perfect page with terrible heading text still fails. Each heading should do three jobs at once:

1. Describe the section honestly. “Mixing and Folding the Dough” tells the reader exactly what is below it. “Details” tells them nothing. I have a personal ban on vague headings: no “Overview,” no “More Info,” no “Things to Know,” no “Conclusion” as a bare label. Every heading must earn its place by describing real content.

2. Include keywords where they fit naturally. Your H1 should contain your primary keyword — that is the single most important heading decision you will make. H2s should carry related terms and question phrases your audience actually searches. H3s can hold long-tail variations. But “naturally” is doing heavy lifting in that sentence: if a keyword does not fit, do not force it. A clear heading without a keyword beats a stuffed heading every time.

3. Stand alone. This is the 2026 skill. Read each heading in isolation, as if it appeared in an AI answer or a search snippet with no context. Does it still make sense? “The Starter” is weak alone. “What You Need: The Sourdough Starter” is strong alone. Headings that make sense out of context get cited; headings that need context get skipped. When I rewrote my old vague headings with this test, my content started appearing in answer boxes I had never targeted.

One more technique I love: question headings for H2s. “How Long Does Sourdough Take to Rise?” mirrors exactly what people type into Google, which makes it a natural fit for featured snippets and voice search. I do not make every H2 a question — that gets monotonous — but one or two per article, placed where the content genuinely answers them, works beautifully.

Abstract 3D illustration of a robotic eye scanning glowing heading bars.

The Five Heading Mistakes I Find on Every Audit

I have audited hundreds of WordPress sites. These five mistakes appear on nearly all of them.

Mistake 1: Multiple H1s. Covered above — usually caused by themes or page builders. One H1 per page, no exceptions.

Mistake 2: Skipped levels. H1 → H3 jumps, or H2 → H4 for styling. Fix the CSS, keep the hierarchy clean.

Mistake 3: Bold paragraphs pretending to be headings. This was my own sin. Selecting text and hitting “bold” instead of choosing a heading block. It looks like a heading to sighted readers and means nothing to Google or screen readers. In the block editor, always use an actual Heading block.

Mistake 4: Keyword-stuffed headings. “Sourdough Bread Baking | Best Sourdough Bread Recipe | Easy Sourdough Bread” as an H2. This is not 2012. Write for the human first; the keyword will fit naturally in a well-written heading.

Mistake 5: The heading-content mismatch. An H2 that promises “Troubleshooting Common Problems” followed by two sentences about flour brands. Every heading is a promise to the reader. If the content under it does not deliver, readers bounce — and headings that consistently mislead train readers to stop trusting your structure.

Note: Headings inside images do not count. If your “heading” is text baked into a graphic, Google cannot read it as a heading and screen readers cannot navigate to it. Real text, real heading tags, always.

The 15-Minute Heading Audit

Here is the audit I run on any page, mine or a client’s. Set a timer — it really takes fifteen minutes.

Minutes 1–3: Count the H1s. Open the page and use a heading-checker tool or your browser’s developer tools. Exactly one H1? Good. More than one? Note each extra for fixing.

Minutes 4–6: Trace the hierarchy. List every heading in order with its level. Look for skips (H2 → H4), orphans (an H3 with no parent H2 above it), and bold-text impostors. Mark each one.

Minutes 7–10: Read headings alone. Copy just the headings into a blank document. Do they tell the story? Are any vague (“Overview,” “Details”)? Does each make sense out of context? Rewrite the weak ones right in the list.

Minutes 11–13: Check keywords. Does the H1 contain the primary keyword? Do the H2s cover the related terms and questions? Note gaps — but do not stuff; note only genuine misses.

Minutes 14–15: Check the promise. Skim one section per heading. Does the content under each heading deliver what the heading promises? Flag mismatches for the next editing pass.

Do this for your ten most important pages and you will find problems on at least half of them. I guarantee it — I have never audited a site that passed clean.

Abstract 3D illustration of a magnifying glass over a checklist of geometric heading bars.

If headings feel connected to your broader design, our guide to layout rules for readable WordPress design shows how structure and visual hierarchy work together. And if you are fixing headings inside the block editor and hitting weird errors, how to fix block validation errors covers the heading-block glitches I see most.

Frequently Asked Questions

How many H1 tags should a page have? One. Exactly one. While modern HTML technically permits more, a single H1 gives Google, readers, and screen readers one clear statement of what the page is about. Multiple H1s create competing “main topics” and muddy your SEO. If your theme outputs the H1 automatically, start your content sections at H2.

Can I skip from H1 to H3 if there is no H2 content? No — restructure instead. If you have no H2-level content between the H1 and the H3, then that H3 is really an H2. Skipped levels confuse search engines building your content outline and break screen reader navigation, which announces each level change to blind users. Step down one level at a time, always.

Do keywords in headings still help SEO? Yes, but as a clarity signal, not a stuffing opportunity. Your primary keyword in the H1 helps Google confirm the page’s topic. Related terms in H2s help it map your coverage. The ranking benefit comes from headings that accurately describe well-organized content — not from repeating keywords. Write the clear heading first, fit the keyword in where it belongs naturally.

Should headings be questions or statements? Both, mixed. Question headings (“How Long Does Sourdough Take?”) match real search queries and work well for featured snippets and voice search. Statement headings (“Mixing and Folding the Dough”) are cleaner for procedural sections. I use one or two question H2s per article where the content genuinely answers them, and statements everywhere else.

Do H4, H5, and H6 matter for SEO? Barely. They carry minimal ranking weight and exist for deep structure in long technical documents. Most articles never need them. If you are reaching for H5, consider whether your content needs restructuring instead — deeply nested headings usually signal a section that should become its own article.

Final Thoughts

That email from the screen reader user still sits in my inbox. I keep it as a reminder that the web is not just what I see on my screen — it is what machines read, what assistive technology navigates, and what AI systems cite. Headings are where all of those meet. One H1, clean chapters, honest labels. It is not glamorous work. It is foundation work.

Run the 15-minute audit on your most important page today. I promise you will find something to fix — everyone does. Fix it, then do the next page. Your readers will feel the difference even if they never consciously notice your headings, and that is exactly the point. Good structure is invisible. Bad structure is all anyone remembers.

You have the model now: book, chapters, sections. Go build pages with bones. And if this guide helped you fix a heading mess, tell me about it in the comments — I collect heading horror stories, and yours might be the best one yet.

Written by

Omar Farouk

Omar advises founders on building and pricing SaaS products on WordPress infrastructure. With 9 years across startups and agencies, he writes about business models, licensing, and sustainable growth.

6 published articles
View all articles

Related articles

View all articles

Join the discussion

Your email address will not be published. Required fields are marked *

Keep comments relevant and respectful.