Heading hierarchy H1, H2, H3 — the rules that matter in 2026

Quick frame: One H1 per page, matching the topic. H2s are major sections. H3s nest beneath H2s for detail. Skipping levels (H1 → H3) is bad for accessibility — screen readers announce hierarchy — and weakens the signal Google uses to extract jump links in the SERP.

The contract, in detail

One H1 per page

The H1 is the page's primary headline. Multiple H1s confuse screen readers and dilute the topic signal. Google can rank pages with multiple H1s — they're flexible — but the convention is still one.

For pages auto-generated by CMSes that inject an H1 in the template and then editors add another in the body, this happens silently. Audit with the heading structure extractor embedded above.

H2s as major sections

Each H2 is a top-level section. For a typical long-form post: 4–8 H2s, each starting a distinct sub-topic. H2s often become jump-link candidates in Google SERPs — if you target featured snippets, well-named H2s help.

H3s nested under H2s

When an H2 section has sub-points, use H3 — never H4 directly after H2. The hierarchy reads:

H1 — Page title
  H2 — Section A
    H3 — Sub-point A.1
    H3 — Sub-point A.2
  H2 — Section B
    H3 — Sub-point B.1

Skipping is an accessibility bug

Going H1 → H3 (skipping H2) breaks screen reader navigation — users hear "heading level 3" without context for where it sits. For SEO, the impact is mild but real (Google extracts hierarchy for jump links).

Common antipatterns

Styling headings as not-headings

Designers sometimes use <p class="heading"> with heading-like CSS. This hides the structure from screen readers and SEO. Always use h1–h6 tags for structural headings, even if you style them differently.

Decorative H tags

Using H2 or H3 for sidebar widget titles, footer links, etc. Dilutes the hierarchy signal. Style those as p or span with heading-like CSS.

H1 in the navigation menu

Some templates wrap the site logo in h1. Move the H1 to the actual page content.

Audit checklist

1. Run the heading extractor on 5 representative pages.
2. Confirm exactly one H1 per page.
3. Confirm no level skips.
4. Confirm decorative widgets aren't using H tags.
5. Check accessibility tooling (axe DevTools, WAVE).

For the wider on-page audit, pair with keyword density, anchor text and image alt checkers.

FAQ

Q. Can I have an H1 that's different from the page title? A. Yes — they serve different purposes. Title is for SERPs (compressed, keyword-led); H1 is for readers on the page (more conversational). Close but not identical.

Q. What if my CMS makes it hard to control heading tags? A. Lobby for the fix. The cost of bad heading structure compounds — and modern CMSes (Notion, Webflow, Ghost) handle this well.

Q. Does Google penalise pages without H1? A. Not a penalty. Just suboptimal — accessibility tools flag it, screen readers struggle, jump-link eligibility weakens.