H2 and H3 Heading Structure for SEO (A Practical Guide)

Use one H1 (your page title), H2s for major sections, and H3s only inside an H2. Never skip a level. Never choose a heading tag based on how it looks — that's what CSS is for.

That's the whole rule. Everything below explains why it matters, how Google uses it, and how to avoid the structural mistakes that quietly tank SEO.

How Google Parses Heading Hierarchy

Google's crawlers read headings as a document outline. The heading structure tells them: here's the main topic (H1), here are the major subtopics (H2s), here are the supporting details under each subtopic (H3s).

This outline is used in at least two ways:

1. Topical relevance signals. Headings carry more weight than body text for keyword relevance. A keyword in an H2 is a stronger signal than the same keyword buried in a paragraph.
2. Featured snippet extraction. When Google generates a list-based featured snippet, it frequently pulls H2 or H3 text as the list items. A cleanly nested structure makes your content far more eligible for these.

A heading hierarchy that jumps from H1 to H4, mixes H2s and H3s at the same logical level, or uses heading tags purely for visual styling sends a garbled outline. Google can still index the page, but you're making its job harder — and you're leaving snippet eligibility on the table.

For a complete picture of the on-page signals that matter, the on-page SEO guide covers heading structure alongside the other elements that influence rankings.

The Structure Rule in Plain Terms

H1  — Page title (one per page, always)
  H2 — Major section
    H3 — Sub-point under that section
    H3 — Another sub-point under the same H2
  H2 — Next major section
    H3 — Sub-point
  H2 — Another major section

That's a valid structure. What's invalid:

• Jumping from H1 directly to H3 (skipping H2)
• Placing an H2 inside an H3
• Using multiple H1s
• Using H4s when H3s haven't been used yet

The rule isn't arbitrary. It mirrors how document structure works in every formal writing system. An outline that goes 1. Introduction > 1.1.1. First Detail without a 1.1 doesn't make logical sense — and Google's parser agrees.

For a deeper look at the H1 specifically, see how many H1 tags per page.

How Featured Snippets Pull From Clean Heading Structure

Google's featured snippets fall into a few types: paragraph snippets (a short answer to a question), list snippets (ordered or unordered), and table snippets. Heading structure primarily affects list snippets.

When Google sees a question-like H2 followed by a series of H3 sub-items, it recognizes a potential list answer. Example:

## What Are the Rules for URL Slugs?

### Use Hyphens, Not Underscores
### Keep It Under 75 Characters
### Remove Stop Words

That structure is a clean list. Google can extract those H3s as list items in a featured snippet without needing to parse paragraph text. The page at /guides/on-page-seo/url-slug-best-practices demonstrates this structure in practice — the "7 Rules" section uses exactly this pattern.

The takeaway: if you're targeting a "what are the X rules/steps/types" query, structure your answer as an H2 question with H3 items beneath it. That's the format Google is looking for.

Writing H2s as Questions to Target "People Also Ask"

Google's People Also Ask (PAA) boxes show up on the majority of informational queries. Each PAA item is a question. Each answer Google shows is pulled from a page that answers that specific question cleanly.

H2s written as questions improve your eligibility for PAA placements. Compare:

Weak: ## Paragraph Length Strong: ## What Is the Ideal Paragraph Length for Blog Posts?

The strong version matches how PAA questions are phrased. The answer immediately below it — a short, direct paragraph — becomes a candidate for extraction.

Guidelines for question-based H2s:

• Use the actual phrasing users search, not editorial paraphrase
• Keep the question under 60 characters where possible
• Follow it immediately with a direct 2–3 sentence answer, then elaborate
• Don't force every H2 to be a question — use this where you have a clear Q&A structure

For related guidance on paragraph length and structure, see ideal paragraph length for blog SEO.

The Styling-Driven Heading Bug

This is the most common structural mistake on CMS-built sites, and it's almost always the designer's fault (or the developer who implemented the designer's mockup without thinking about semantics).

The scenario: a designer mocks up a page where a certain text style — say, a slightly smaller bold subheading — looks best represented by an H4 in their preview. The developer implements it as <h4>. The content team sees "H4 for subsections" as the pattern and follows it. The result is a page with H1, H2, H4 — no H3 anywhere — and Google gets a broken outline.

The fix is to separate visual style from semantic meaning:

• Use heading tags (h1 through h6) for their structural role only
• Use CSS classes to control how those headings look
• Never choose a heading level based on font size

If H3 "looks too big" in your design, the answer is h3 { font-size: 1.1rem; } — not switching to H4.

The Scannable Outline Test

Here's a practical test for every article you publish: strip out everything except the headings and read them top to bottom. Does the resulting outline tell a coherent story? Can a reader understand what the page covers, in what order, and roughly what each section argues — just from the headings?

If the answer is no, the headings are either too vague, out of logical order, or duplicating each other. Fix the headings first. The content structure usually follows.

Strong heading structure also directly improves readability metrics. See the H2 and H3 heading structure guide as a reference for what a scannable outline looks like in practice (you're reading it).

A related signal is how your page title and meta title interact with your H1 — the guide on whether Google rewrites title tags explains why your H1 and <title> tag should be coordinated but don't need to be identical.

How Many H2s and H3s Should a Page Have?

There's no prescribed number. A 1,500-word article might have 5–7 H2s. A 3,000-word technical guide might have 10+ H2s and 20+ H3s. What matters is that the heading count reflects genuine structural divisions in the content, not arbitrary breaks added to hit a target.

The anti-patterns to avoid:

• Too few headings. A 2,000-word article with two H2s is essentially unnavigable. Readers can't scan it, and Google's outline is thin.
• Too many shallow headings. If every 100-word section has its own H2, the document outline becomes noise. Groups of related points should share an H2 with H3 sub-items.
• H3s used as styling, not structure. Every H3 should logically belong under the H2 above it. If an H3 makes more sense as a continuation of a different section, restructure.

Auditing Your Heading Structure

The heading structure tool extracts your page's heading outline and flags: skipped levels, multiple H1s, H3s without a parent H2, and headings that are too short or too generic to carry keyword signal.

Run it on any page before publishing. Then run it on your highest-traffic existing pages — heading structure bugs are common on older content, especially on sites that have changed CMS platforms or design systems over time.

A clean heading hierarchy is low-effort, high-leverage work. It takes ten minutes to audit and fix. The payoff is a page that Google can parse, readers can scan, and featured snippets can extract from. That's three wins for one structural decision.