Header Structure: H1 to H6, Done Right

Heading tag advice from 2015 has calcified into SEO folklore that's mostly wrong in 2026. "One H1 per page!" gets repeated despite the HTML5 spec explicitly allowing multiple H1s. "Keyword-stuff your H2s!" gets repeated despite quality systems learning to discount that pattern. "H6 helps SEO!" gets repeated despite Google having never used H6 for anything ranking-relevant.

The real story is less dramatic. Headings signal document structure to search engines and assistive technology. Good heading hierarchy helps Google understand your argument's shape. Bad hierarchy isn't penalized directly — it just wastes an organizational signal you could have used.

This article covers what heading tags actually do in 2026, how to structure H1-H6 semantically, and where the accessibility and SEO advice converge (usually) or diverge (occasionally).

What headings do for SEO

Three things, in decreasing importance:

1. Structure the document's argument — Google's ranking systems parse heading hierarchy to understand what the page covers and how it's organized. A page with clear H1 → H2 → H3 structure signals "here's a topic, here are its subsections, here are sub-subsections."
2. Support snippet generation — headings become anchor points for featured snippets, passage ranking, and table-of-contents displays.
3. Minor ranking signal as secondary relevance indicator — keywords in H2/H3 provide supplementary topical signals. Not a big factor, but not zero.

What headings don't do in 2026:

• They're not a major ranking factor directly. Passage content matters more than passage headings.
• H1 specifically is not a special magic tag. Its "specialness" is mostly convention, and Google treats it as one more heading with slightly elevated semantic weight — not a ranking multiplier.

The H1 question: how many per page?

Old rule: exactly one H1 per page.

HTML5 spec: multiple H1s are allowed within <article>, <section>, and similar semantic sectioning elements. Each section can have its own H1.

Google's actual behavior (confirmed by John Mueller multiple times): Google handles multiple H1s fine. The old "one H1" rule was always more about human convention than crawler limitation.

Practical recommendation for 2026:

• For most sites, still use one H1 per page. It's clearer for writers, clearer for accessibility, and aligns with broad SEO conventions. Not a ranking fix — just less mental overhead.
• If your CMS or framework renders multiple H1s naturally (a blog listing page where each article excerpt gets an H1), don't panic. Google ranks them fine. Your accessibility audit might flag it, but it's not an SEO emergency.
• Pages where multiple H1s clearly match the semantic structure (category pages listing sections, each titled with an H1) are not penalized. Just ensure the hierarchy makes sense.

H2 structure: the load-bearing layer

H2s do more SEO heavy lifting than any other heading level. They:

• Divide the page into scannable sections.
• Signal subtopics within the main topic.
• Serve as anchor points in a table of contents.
• Get picked for "People Also Ask" matches when the H2 matches common questions.

Good H2 practice:

• Descriptive and honest — "How to prioritize crawl budget" beats "Crawl Budget Prioritization" (more natural), which beats "Crawl Budget SEO" (keyword-stuffed and vague).
• Parallel structure — if one H2 is "How X works," the next shouldn't be "Implementing X" (mixing how-to and explanatory). Pick a pattern and stay consistent.
• Front-load the key concept — "Fixing crawl chains on large sites" starts with the action verb. Users scanning the page see action.
• 5-10 H2s per long article, 3-5 on shorter pieces. Fewer means the page has too little structure; more means the article is too fragmented or too broad.

H2s where keyword stuffing used to be recommended (2013-era "include the keyword in H2") no longer matter. A descriptive H2 that doesn't contain the exact keyword is fine if the section content is clearly about the keyword.

H3 and below: when to go deeper

H3s appear under H2s when the H2 has genuinely distinct subparts. If you have H3 "A" and H3 "B" under an H2, they should really be two different concepts within that H2's umbrella, not just "first paragraph" and "second paragraph."

Test: can a section stand alone as its own article? If yes, it's probably an H2 (or its own article). If no but it's a distinct subtopic within the H2, it's an H3.

H4, H5, H6 are rare. Mostly they show up in:

• Extensive technical documentation with deep hierarchy
• Tables of contents for ebook-length content
• Programmatically generated listings

If you're reaching for H5 or H6 in an article, it's usually a signal to restructure — the hierarchy is too deep, and the content should be split into separate pages or flattened to H3.

The table-of-contents interaction

H2/H3 headings are the natural anchor points for a table of contents at the top of long articles. For SEO, this has two benefits:

1. Passage ranking — each TOC anchor targets a specific part of the page. Google can index and show these as jump links in the SERP.
2. On-page navigation — users can jump to sections, reducing bounce on long pages.

Implementation: auto-generate TOC from H2/H3 headings, with IDs on each heading. Most CMS and blog engines do this automatically; if yours doesn't, the implementation is trivial.

<h2 id="what-h1-does">What the H1 does</h2>

Becomes a jump link at https://yoursite.com/article#what-h1-does.

Accessibility overlap

Heading hierarchy is also how screen readers navigate pages. A user with a screen reader can press "H" to jump between headings, or "2" to jump between H2s specifically. Bad hierarchy (skipping levels, illogical order) breaks this navigation.

Rules that serve both SEO and accessibility:

• Don't skip levels. An H1 followed directly by an H3 (no H2 between) breaks screen reader navigation and confuses semantic parsers.
• Match visual hierarchy to semantic hierarchy. If something looks like a section heading, use a heading tag — not a <p> styled to look like one.
• Don't use headings for styling. An H2 chosen because it looks big is a misuse. Use CSS for styling; reserve headings for semantic structure.

The rare case where SEO and accessibility diverge: visually emphasized subheadings that aren't structurally meaningful (a pull-quote styled large). Accessibility says don't make it a heading; SEO is neutral. Use CSS.

Front matter: the intro before the first H2

The paragraphs between the H1 and the first H2 are special SEO real estate. They:

• Often become the snippet when Google pulls a passage for non-meta-description snippets.
• Contain the terms Google uses to establish topical relevance.
• Set user expectations for what the article delivers.

Treat them as premium. First 100 words should:

• Contain the primary keyword naturally.
• State what the article delivers (claim, framework, number-of-things).
• Hook the reader past the first paragraph.

"In this post, we'll discuss..." is the single worst opening, for both SEO and engagement. Replace it with a claim, a fact, or a counter-intuitive observation.

Common mistakes

H1 that matches the title tag exactly. Fine when warranted, but often wasteful — the H1 can be longer and more descriptive than the title. Use the extra real estate.

All H2s keyword-stuffed. "H2: Crawl Budget Basics. H2: Crawl Budget for Large Sites. H2: Crawl Budget Tools. H2: Crawl Budget Conclusion." Google learns the site is keyword-stuffing. Hurt more than helped.

Heading tags on layout elements. Sidebar links wrapped in H3 because it fits the visual size. Misuse. Headings belong to document structure.

H1 inside <main> wrapper but different H1 in <nav> or <footer>. Some CMS themes do this. Fine by spec; confusing for maintenance. Audit if you see it.

Missing H1. Article page with <h2> as the main heading, no H1. Google handles it but it's weird for assistive tech and breaks the outline tools. Add an H1.

Headings as buttons. <h2 onclick="...">Toggle</h2> — a heading should never be an interactive element on its own. Wrap it in a <button> if it needs to be interactive.

Frequently asked questions

Does having my primary keyword in the H1 help rankings?

Directly: minimally. The H1 is a weak relevance signal — Google notices, but it's not a big multiplier. Descriptive H1s that happen to contain the keyword outperform keyword-stuffed H1s that contradict the content. Write for users; keyword inclusion often happens naturally.

Can I use multiple H1s?

Technically yes (HTML5 spec allows it), practically still better to use one per page for clarity. Multiple H1s aren't an SEO penalty; they're a convention choice.

Do I need to use H4, H5, H6?

Rarely. Most articles only need H1 (title), H2 (main sections), and occasional H3 (subsections). H4+ suggests the content is too deeply nested and might benefit from restructuring.

Should my H2s contain the target keyword?

Naturally, yes — if the H2 is about the target concept, the keyword often fits. Forcing it in unnaturally hurts readability without helping rankings. Use H2s to describe sections honestly.

What about aria-level for visual headings?

aria-level lets you assign a heading level to non-heading elements (e.g., a <div role="heading" aria-level="2">). Valid for accessibility in specific cases but doesn't replace actual heading tags for SEO — Google doesn't parse aria-level the same way it parses <h2>.

What to read next

• On-Page SEO Checklist 2026 — heading structure in the overall on-page picture.
• Writing title tags that rank AND get clicks — the title tag vs H1 relationship.
• Featured snippet optimization — how heading structure affects snippet eligibility.