How to Structure Content With Headings (H1-H3) for SEO

Headings are the skeleton of every page you publish. Get the hierarchy right and your content becomes easier to scan, easier to rank, and far more likely to win featured snippets. Here’s the system I use on every article.

Updated August 2026 · 14 min read

Most writers treat headings as decoration — a way to make a long page look less intimidating. That’s a wasted opportunity. Your H1, H2s, and H3s are doing three jobs at once: they tell readers where they are, they tell Google what each section is about, and they decide whether your content is eligible for the featured snippet box that sits above every other result. I’ve audited hundreds of blog posts over the years, and broken heading structure is one of the top five on-page problems I find, right alongside missing title tags and orphaned pages. The good news: it’s also one of the easiest to fix, and the fix pays off on every future article you write.

This guide walks through the exact heading system I use — the hierarchy rules, how to write headings that earn clicks and snippets, the mistakes that quietly hurt rankings, and a pre-publish checklist you can run in under five minutes. No theory for theory’s sake. Everything here is something you can apply to your next post today.

Why Headings Matter More Than You Think

Let’s start with what headings actually do, because the SEO benefit is only one of three.

First, scannability. Eye-tracking studies going back two decades show the same pattern: people don’t read web pages, they scan them. A typical visitor spends a few seconds skimming headings and the first line of each section before deciding whether to commit. If your headings are vague (“Introduction,” “More Info,” “Conclusion”), scanners bounce. If they’re specific (“How Long Should an H1 Be?”), scanners stop, read, and stay — and dwell time is a quality signal you want on your side.

Second, crawl comprehension. Google’s own SEO starter guide tells site owners to use headings to indicate the structure of a page. Heading tags give crawlers a semantic outline of your content: what’s the main topic, what are the subtopics, how do sections relate to each other. A page with clear structure is simply easier for a search engine to understand and match to queries.

Third, featured snippets. The answer boxes, lists, and tables at the top of search results are almost always extracted from content sitting directly under a heading that closely matches the query. If your H2 says “How to Change a Tire” and the paragraph beneath it gives a tight, direct answer, you’re a snippet candidate. If that same answer is buried in an unbroken wall of text, you almost certainly aren’t.

A heading is a promise to the reader. Keep the promise specific, and both humans and crawlers will reward you for it.

The One Rule That Matters: Hierarchy

If you remember nothing else from this article, remember this: heading levels exist to show relationships, not to pick font sizes. H1 is the title of the page. H2s are its main sections. H3s are subsections inside an H2. H4s exist but you’ll rarely need them on a blog post.

The hierarchy should never skip a level. An H2 followed directly by an H4 is like a book with a chapter that jumps straight to sub-subsections — technically readable, structurally wrong. Screen readers rely on this nesting to let visually impaired users navigate your page, so skipping levels is an accessibility problem as well as an SEO one.

Here’s the shape almost every article on your site should have:

If you’re ever tempted to use an H3 because “it looks nicer” at that size, stop. Change the styling in your theme, not the tag. The MDN documentation on heading elements is blunt about this: don’t use heading levels for sizing, and don’t skip levels. CSS controls appearance; HTML controls meaning.

The H1: One Page, One Title

Your H1 is the strongest on-page signal of what the page is about. A few rules that have never let me down:

• Use exactly one H1 per page. HTML5 technically permits multiple, and Google has said it can cope, but “can cope” is not “rewards.” One H1 removes all ambiguity, and every major CMS gives you exactly one title field anyway.
• Put the primary keyword in it, near the front. “How to Structure Content With Headings (H1-H3) for SEO” targets the query directly. “Some Thoughts on Better Writing” targets nothing.
• Keep it under about 60 characters where possible. Not because Google truncates H1s — it doesn’t — but because your H1 usually doubles as your title tag, and title tags get cut off in results. I cover that relationship in depth in the title tags and meta descriptions guide.
• Make it a promise, not a label. Compare “Heading Tags” with “How to Structure Content With Headings (H1-H3) for SEO.” Same topic. The second one tells the reader exactly what they’ll be able to do after reading.

One subtlety: your H1 and your title tag don’t have to be identical. The title tag is written for the search results page (where it competes with nine other blue links); the H1 is written for someone who already clicked. It’s fine for the title tag to add your brand name or a hook, as long as both contain the core keyword and promise the same content.

H2s: Your Section Titles Are Mini Headlines

H2s are where most articles succeed or fail. Each one should work like a headline for the section beneath it — specific enough that a scanner can navigate by headings alone and still understand your entire argument.

Here’s the test I run on every draft: I delete all the body text and read only the headings in order. If the outline makes sense as a standalone summary of the article, the headings pass. If I see “Tips,” “More Ideas,” or “Final Thoughts,” those get rewritten. This article’s H2s should pass that test — go ahead and skim them.

Write H2s as questions and statements people actually search

A practical trick: mine the “People also ask” box and autocomplete suggestions for your topic, then turn the best ones into H2s verbatim or near-verbatim. “Why Headings Matter More Than You Think” works as a section title; “Do heading tags affect SEO?” works even better if that’s what people type. You’re aligning your structure with real query language, which helps both rankings and snippet eligibility.

Keep H2s reasonably short — 70 characters or fewer is a good working limit — and front-load the important words. “H2s: Your Section Titles Are Mini Headlines” puts the keyword first; “Why You Should Treat Every Single One of Your Section Titles as a Mini Headline” buries it.

How many H2s is right?

There’s no magic number, but there’s a useful heuristic: one H2 for every distinct subtopic, and a new one roughly every 200–400 words. For a 2,500-word article, that lands you at 7–12 H2s, which matches what I see across well-structured ranking content. If you go 800 words without a heading, scanners are staring at a wall. If you have a heading every 80 words, the page feels choppy and the headings stop meaning anything.

H3s: Subsections That Do the Detail Work

H3s live inside H2 sections and break a big subtopic into digestible pieces. In this article, “Write H2s as questions” and “How many H2s is right?” are H3s — they belong to the H2 section above them and wouldn’t make sense as top-level sections.

Three situations where H3s earn their keep:

• Step-by-step processes. Each step gets an H3 (“Step 1: Export your current headings,” “Step 2: Map them into a hierarchy”). This is also prime snippet material — Google loves pulling ordered steps from headed sections.
• Comparisons. An H2 of “Manual vs. Automated Heading Audits” with H3s for each approach lets readers jump straight to the one they care about.
• Examples. “Example: Fixing a Real Post’s Structure” as an H3 signals concrete, practical content — the kind readers and algorithms both favor.

If you find yourself reaching for an H4, pause and ask whether the article has grown a section that deserves to be its own post with an internal link instead. Deeply nested content is often a sign of scope creep, not thoroughness.

How Headings Win Featured Snippets

Featured snippets — the extracted answer boxes at the top of Google results — follow predictable patterns, and headings sit at the center of most of them. The mechanics are simple: Google finds a heading that matches or closely paraphrases the query, then extracts the content immediately beneath it.

That gives you a repeatable formula:

• Match the heading to the query. If the query is “how many H1 tags per page,” an H2 reading “How Many H1 Tags Should a Page Have?” is a near-perfect snippet hook. A heading reading “The Great H1 Debate” is not.
• Answer immediately underneath. The first 40–60 words after the heading should deliver the answer directly, in plain language. Context and caveats come after. Burying the answer three sentences deep is the most common way pages lose snippets they should own.
• Match the format to the snippet type. Paragraph snippets want a concise 40–60 word answer. List snippets want an actual <ul> or <ol> under the heading. Table snippets want a real HTML table. Write the content in the format you want extracted.
• Keep the answer self-contained. If the paragraph only makes sense after reading the two sections before it, it won’t get pulled. Each snippet candidate should stand alone.

Worth knowing: winning a snippet isn’t purely about structure — the page generally needs to rank on page one already, and the answer has to be accurate. But among pages of similar authority, the one with the cleaner heading-to-answer structure wins far more often than not.

Keywords in Headings: Enough, Not Everywhere

Yes, keywords in headings still matter — they’re a genuine relevance signal. No, you should not stuff a keyword into every heading on the page. Here’s the distribution that works:

• H1: primary keyword, once. Non-negotiable.
• H2s: two or three H2s containing natural variations or closely related phrases (“heading structure,” “featured snippets,” “H1 per page”). The rest should use natural language that covers the topic’s vocabulary.
• H3s: whatever reads naturally. Don’t force it.

The test is always the same: does the heading sound like something a human expert would write as a section title? “Heading Structure SEO Best Practices Heading Tags” is keyword salad and reads like it. Google’s helpful content guidance is explicit that content written primarily for search engines is what their systems try to demote — and headings are one of the most visible places that over-optimization shows. If you’ve done your keyword research properly, the subtopics themselves will supply natural keyword variations for your headings. That’s the right way to do it: let the research drive the outline, and the outline drives the headings.

Headings, Accessibility, and Why the Two Are the Same Fight

Everything that makes your headings good for SEO makes them good for accessibility, and vice versa. Screen reader users navigate long pages by jumping between headings — it’s the equivalent of sighted scanning. When your hierarchy is clean, they get an accurate table of contents for your page. When you skip from H2 to H4, or bold text instead of using real heading tags, their outline has holes in it.

Practical accessibility rules that double as SEO rules:

• Never use headings for non-heading text. If you want a big bold disclaimer, use CSS. Headings that aren’t section titles pollute the document outline for both crawlers and assistive technology.
• Don’t skip levels. H2 → H3 → H4 is fine. H2 → H4 is not.
• Make headings meaningful out of context. Screen reader users often pull up a list of all headings and jump straight to one. “Step 3” means nothing in isolation; “Step 3: Rewrite vague headings” does.

Accessibility is also increasingly tied to the overall quality perception of a site. You don’t need to become an accessibility specialist to get headings right — you just need to use the tags the way they were designed to be used.

Common Heading Mistakes I Find in Audits

These five show up constantly, and all five are fixable in an afternoon:

The multiple-H1 problem deserves a special note because it’s usually not the writer’s fault. Plenty of themes wrap the site title or logo in an H1 on every page. Check yours: view source on a blog post and search for <h1. If you find two, the fix is a one-line template change, and every page on the site benefits.

Bad headings rarely get a page penalized. They just quietly cap how well an otherwise good article can perform — and compound across every post you publish.

A Five-Minute Heading Audit for Existing Posts

You don’t need a paid tool for this. Here’s the exact process I run when auditing an older article:

• Step 1: View the outline. Use your browser’s reader mode, an accessibility inspector, or just view source and scan the heading tags. You want the raw list of H1–H4 in order.
• Step 2: Check for exactly one H1. Two or more means a theme issue. Zero means the title isn’t tagged at all. Both need fixing in the template, not the post.
• Step 3: Check for skipped levels. Any H3 that follows an H1 directly, or H4 that follows an H2, gets renumbered.
• Step 4: Run the skim test. Read only the headings, top to bottom. Rewrite any that are vague, cute, or keyword-stuffed until the outline alone tells the article’s story.
• Step 5: Hunt for snippet opportunities. Pick two or three H2s that map to real questions and tighten the first paragraph under each into a direct 40–60 word answer.

On a typical 2,000-word post this takes about five minutes, and it’s one of the highest-return edits you can make. If you want to fold this into a broader pass over the whole page — titles, internal links, images, speed — my one-hour SEO audit checklist walks through the full routine, and headings are step two on it.

Putting It Together: An Example Outline

Here’s how this system looks applied to a real topic — say you’re writing a post targeting “how to repot a plant”:

• H1: How to Repot a Plant Without Killing It (Step-by-Step)
• H2: When Should You Repot a Plant?
• H2: What You Need Before You Start
• H2: How to Repot a Plant in 6 Steps
• H3: Step 1: Water the Day Before
• H3: Step 2: Loosen the Root Ball
• H3: Step 3–6: …
• H2: Aftercare: The First Two Weeks
• H2: Common Repotting Mistakes

Every heading is a query or a promise. The H2 sequence passes the skim test. The step H3s are formatted exactly the way list snippets get extracted. And the whole thing took maybe ten minutes to outline — before a single paragraph was written. That’s the real payoff of this system: headings aren’t an editing pass at the end. They’re the blueprint you write from, and articles built on a good outline are faster to write, easier to read, and better positioned to rank.

Once your structure is solid, connect it up: a well-structured post with a smart internal linking strategy passes authority to your other pages and keeps readers moving through your site. Headings get them reading; links keep them here.

Sources and further reading: Google’s SEO Starter Guide and the MDN heading elements reference were consulted for this article. Reviewed and updated August 2026. Related reads on this site: title tags and meta descriptions, keyword research for beginners, and the one-hour SEO audit checklist.