Heading Checker

Why heading structure matters for SEO

A heading checker catches the H1–H6 structure issues a quick manual scan often misses. Headings aren't just visual formatting. They tell Google what a page covers and which sections belong together, and screen reader users navigate by them. A missing H1 won't get a page dropped from the index. But Google lists <h1> among the sources it uses to build a page's title link, so without one that hint is gone.

This H1 checker scans every heading tag (H1 through H6) and maps out the full hierarchy tree. Duplicates, skipped levels, and empty tags: all flagged instantly. If your heading structure has SEO problems, this tool makes them impossible to miss.

Heading hierarchy and SEO

Google uses headings to understand how a page is organized, but it's more relaxed about order than most SEO checklists. Its own SEO Starter Guide says heading order doesn't matter from a Search perspective, and that there's no ideal number of headings. So why check order at all? Screen readers depend on it, and a jumbled outline usually means headings were picked for their font size, not their meaning. Where headings count directly for Google is the title link: it can pull the title from <h1>, and several equally prominent headings make that choice harder.

Accessibility and heading structure

For screen reader users, headings are the navigation. In NVDA and JAWS the H key jumps to the next heading, and many users pull up a list of all headings to skim a page first. If the page jumps from H1 to H4, that list suggests sections that don't exist. WCAG 2.1 success criterion 1.3.1 asks that structure shown visually is also in the markup, and headings are part of that. Since June 28, 2025 the European Accessibility Act applies to a defined set of products and services in the EU, e-commerce and banking among them, and its harmonised standard EN 301 549 builds on WCAG 2.1 AA. A skipped level alone isn't a WCAG failure. A heading structure that doesn't match what the reader sees can be.

Common heading errors this tool finds

The big ones. Multiple H1s on a single page. Heading tags used for styling (H4 for "make this small and bold"). Skipped levels where the HTML jumps from H2 straight to H5. Empty heading tags left by a broken template. Every issue shows up in the hierarchy tree for quick review.

How to check headings across a whole site

One page at a time is fine when you already know which page is broken. The harder question is which of your 300 pages has no H1 at all, and a per-page checker cannot answer that. Switch the tool to Batch, give it a sitemap URL, and it runs the same rules over every URL it finds, up to 250 per run.

What comes back is a sortable table: score, H1 count, total headings, and the single biggest problem on each page. Sort by score and the worst pages rise to the top. Export the lot as CSV if you would rather work through it in a spreadsheet. No sitemap? Paste the URLs by hand instead.

Batch reads the raw server HTML rather than starting a headless browser for every URL, which is what keeps a 250-page crawl down to a couple of minutes. Pages that come back with no headings at all get a second pass through the renderer, so a client-rendered page still reports what single mode would say.

Explore more tools

FAQ