SEO Tools·5 min read

Heading Hierarchy for SEO: Fixing Your H1 to H6 Tree

Heading hierarchy for SEO sounds like a solved problem until you pull a real page's outline and find two H1s, no H2s, and a jump straight to H4. Crawlers and screen readers both rebuild your document's structure from those six tags, so a scrambled tree quietly costs you on both fronts. This guide shows how to get the full H1 to H6 outline of any URL with the Heading Tag Checker (H1 to H6), what a healthy tree looks like, and which structural faults are worth fixing this week versus ignoring forever.

Open the free Heading Tag Checker (H1 to H6)All insights

The redesign that scrambles every heading level

A true story, repeatedly.

It usually happens after a redesign. The new component library styles text by class instead of by tag, a developer reaches for whatever level looks right, and six months later the blog's outlines are archaeology: an H1 in the logo, section titles rendered as H4s because the H4 font looked better, and bold paragraphs doing heading work with no tag at all.

Nobody notices visually, because CSS hides the mess. You only see it when you read the actual tags, which is exactly what the checker does: fetch the URL, list every heading in source order, indent each one by level, count them per tag, and list the problems it finds.

Heading hierarchy for SEO: how machines read your outline

Search engines use headings to understand what a page covers and how its subtopics relate. An H2 tells the crawler a new major section began; the H3s under it are its children. Google's guidance is relaxed about strictness, and its representatives have said heading order alone won't make or break rankings. A coherent tree still helps passage ranking, featured snippet extraction, and the section anchors Google sometimes shows under a result.

The practical rule: one H1 stating the page topic, H2s for major sections, H3s nested beneath, and no level skipped on the way down. Skipping on the way back up, closing an H3 run and opening a fresh H2, is completely fine.

A worked heading check, chip by chip

One URL in, six counts out.

Run a typical documentation page through the checker and the count chips might read: Input: one URL. Output: H1: 2, H2: 0, H3: 9, H4: 3, H5: 0, H6: 0. That single line already tells the story. Two H1s means the template promotes something, usually the site name, alongside the article title. Zero H2s with nine H3s means the authors skipped a level for typographic reasons.

The issues list below the chips spells it out: a warning that 2 H1 tags were found, and a skipped level warning where an H1 is followed directly by an H3, with the heading text quoted so you can find it. In the outline, that heading also carries a small 'skipped level' label.

The fix takes minutes in most CMSs: demote the site name out of H1, promote the nine H3s to H2s, and move their three H4 children up to H3. Check again and the chips read H1: 1, H2: 9, H3: 3, which is the shape a healthy article of this kind should show.

Several H1s on one page: does it matter?

HTML5 briefly promised that each section could carry its own top-level heading, and the argument about multiple H1s has run ever since. Google's position is that several H1s won't hurt you. The accessibility community's position is more useful: browsers never implemented the outline algorithm that would have made per-section H1s meaningful, so a single H1 remains the safe convention.

The checker takes the same view. When it finds more than one H1 it raises a warning, not an error, noting that Google copes but one clear H1 keeps the main topic unambiguous. A missing H1 is treated as an error. Treat the duplicate as a nudge rather than an emergency, and fix it the next time you're already touching the template.

Headings and accessibility: the outline screen readers navigate

Heading navigation is one of the most used features in screen readers. WebAIM's user surveys have repeatedly found that most screen reader users move through long pages by jumping between headings. A skipped level there isn't cosmetic; the listener hears the jump and loses track of what nests under what.

This is the strongest argument for repairing a scrambled tree even if rankings never move an inch. The same check that serves your SEO review doubles as a quick accessibility spot check.

Heading structure faults an outline exposes

Five patterns show up constantly once you start checking outlines:

Fake headings: bold or enlarged paragraphs that carry no tag, invisible to the tree and to assistive tech.
Level skipping for looks, like jumping from H2 to H4 because the H3 font seemed too large.
Template H1s wrapped around logos or taglines, doubling the H1 count on every page of the site. When the first heading on the page isn't the H1, the checker adds a note about it.
Heading tags used as design elements for pull quotes or buttons, which pollutes the outline with non-structural text. Headings over 100 characters get a note too.
Empty heading tags left behind by page builders, which read as blank items to a screen reader. The checker flags each one by its position.

Habits worth keeping around heading fixes

Copy the outline before you change it. Copy as text keeps the indentation, Copy as Markdown turns each heading into # lines, and the CSV button gives you the order, level, text and character count of every heading. Pasting the before and after into your ticket makes the change reviewable. Then check the live URL after deploying, not the staging preview; caching and template differences have embarrassed plenty of people who verified the wrong environment.

If you write content briefs, borrow outlines freely. Checking the top three ranking pages for a query hands you their heading skeletons as Markdown, and the gaps between them are your angle.

When the heading outline needs a partner tool

The checker already shows the title tag next to the first H1, each with its character count, so an obvious mismatch between the two is visible straight away. Beyond that it reads structure, not substance. Run the Keyword Density Checker when you suspect the headings repeat the target phrase too aggressively; its Analyze URL option reads the page's full text. The Meta Tag Analyzer covers the title tag and description in more depth. And when the heading findings raise wider concerns, the WCAG Accessibility Checker tests the rest of the page's markup against a full set of automated rules.