What This Heading Tags SEO Tool Does
Paste a URL into the box above and this heading tags SEO tool fetches that page, pulls out every H1 through H6 tag in the exact order they appear in the HTML, and checks whether the levels nest correctly under WCAG 1.3.1 (Info and Relationships) - the accessibility rule that says a heading level shouldn't skip a step going deeper, such as an H2 followed directly by an H4 with nothing in between. What you get back is a full heading outline, a count for each level, and a plain-language list of anything that's wrong: a missing H1, more than one H1, or a level that got skipped.
It's built for the people who actually have to check this by hand otherwise: SEO consultants running an on-page audit, developers validating a new template or CMS theme before it ships, content editors cleaning up an old post that's grown messy over several rewrites, and accessibility reviewers verifying WCAG 1.3.1 specifically. This is one of AudEsto's free SEO utilities, alongside tools for meta tags, orphan pages, and domain lookups - no account is needed to run a check.
How to Use the Heading Tags SEO Tool
- Enter the URL. Paste the full address of the page you want to check, including the protocol (https://).
- Verify you're human. Click Check Heading Tags and complete the quick reCAPTCHA check - this keeps the tool from being scripted and abused, so it stays free and fast for everyone.
- Review the outline. Every H1-H6 tag appears in document order, indented by level, with per-level counts above it.
- Fix what's flagged. Skipped levels, a missing H1, or duplicate H1 tags are called out individually, in plain language, so you know exactly what to change - then run the check again to confirm the fix worked.
Each browser or IP gets a set number of checks per day. That's enough for auditing a handful of pages in one sitting; if you're reviewing an entire site, work through your priority pages first - usually the homepage, top landing pages, and any templates that generate many URLs at once, like product or category pages.
How the Check Works
Under the hood, the tool requests the page's HTML directly - the same markup a browser would receive before any client-side JavaScript runs - and parses every <h1> through <h6> element it finds, in the order they appear in the source. It then walks that list and compares each heading's level to the one before it: if a level jumps by more than one step (H2 to H4, H3 to H6, and so on), that's flagged as a nesting error. Separately, it counts how many H1 tags exist and checks whether the very first heading on the page is an H1.
One honest limitation worth knowing up front: because the check reads the initial HTML response, it won't see headings that a JavaScript framework injects into the page after it loads - a common pattern on React, Vue, or Angular single-page apps that render content client-side. If a page is built that way, the tool may show fewer headings (or none) than what a visitor's browser actually renders. For those pages, check the server-rendered or prerendered version if one exists, or inspect the live DOM in your browser's dev tools alongside this tool's result.
Reading Your Results
The results panel breaks down into four parts, and each one answers a different question:
- The compliance banner tells you, at a glance, whether the page passes the WCAG 1.3.1 nesting rule specifically - not a full accessibility audit, just this one structural check. Green means no skipped levels and an H1 is present; red means at least one nesting error was found.
- The count chips show how many H1 through H6 tags exist on the page, plus a total. The H1 count deserves the closest look - zero or more than one is worth a second glance even if nothing else is wrong.
- The heading outline lists every heading in document order, indented by level, so you can see the actual shape of the page's structure rather than just a count.
- The issue cards explain each problem in plain terms. Errors (missing H1, no headings at all, a skipped level) break the WCAG 1.3.1 rule directly. Warnings (multiple H1s, starting below H1) are best-practice concerns rather than nesting violations - worth fixing, but not what the compliance check itself is measuring.
Why Heading Structure Matters for SEO
It's worth being precise here rather than treating every heading warning as a Google ranking factor, because it isn't one in any direct sense. Google's own guidance on headings describes them mainly as a way to help both readers and crawlers understand how a page is organized - not a lever you pull to move up the results. Where heading structure actually earns its keep is more layered than that:
- Diagnostic signal. A broken heading outline - skipped levels, no H1, three H1s stacked on top of each other - is rarely an isolated problem. It usually points to a rushed content update, a page builder that let someone pick heading levels for their visual size, or a template bug that's repeating across every page built from it. Fixing the symptom is worth doing regardless of any ranking effect, because the underlying cause is usually worth fixing too.
- Indirect effect on visibility. Google generates featured snippets, "jump to section" links, and some sitelinks directly from heading text and the content beneath it. A page with a clear, well-nested outline gives that process more to work with; a page with a broken one makes it harder for those extra placements to happen, even though there's no direct penalty for getting it wrong.
- Accessibility compliance. WCAG 1.3.1 is a real, independently defined standard, not something invented for SEO purposes. Screen reader users navigate by heading level constantly, and organizations bound by legal accessibility requirements (ADA in the US, EN 301 549 in the EU, and similar rules elsewhere) need this correct on its own merits.
- Best practice, not a hard rule. One H1 per page and no skipped levels isn't enforced by Google penalizing violations - modern HTML5 even tolerates multiple H1s inside separate sectioning elements. It's a convention that keeps a page's outline legible to algorithms, assistive technology, and the next person who has to edit the content, which is reason enough to follow it.
A Practical Example
Example input: a product category page URL from an online store.
Result: 1 H1, 5 H2s, 11 H3s, and one error - "A heading level was skipped (H2 → H4)" - pointing to a filter sidebar labeled "Refine Your Search."
What it means: whoever built the sidebar picked H4 because it matched the smaller font size the designer wanted, not because it structurally belonged four levels deep. The outline now has a gap: a screen reader user landing on that H4 has no way to know an H3 was supposed to come before it.
Recommended action: change the sidebar heading to H3 (or add a wrapping H3 if the visual hierarchy genuinely needs one), then style the font size with CSS instead of the heading level. Re-run the check - the banner should turn green once the gap is closed.
Real-World Use Cases
- Pre-launch and post-migration audits. Confirm that a redesign or CMS migration didn't quietly rewrite the heading order across your key templates.
- Agency QA checklists. Add a heading structure check alongside meta tag and broken link checks before a client site goes live.
- Template and theme validation. Check one representative page from a template - a single fix there corrects every page built from it, which is usually a better use of time than checking pages one by one.
- Accessibility reviews. Verify WCAG 1.3.1 specifically as part of a broader accessibility pass, especially for sites with legal compliance obligations.
- Legacy content cleanup. Old blog posts edited by several people over the years often end up with headings chosen for how they looked in the editor rather than where they belong in the outline.
Common Mistakes with Heading Tags
- Picking a heading level by font size. A heading should describe its place in the outline; its visual size is a CSS decision, not an HTML one.
- Two H1s from a theme plus a content editor. Some page builders auto-insert an H1 for the site title or page title, and an author adds a second one inside the content - producing a duplicate-H1 warning neither person intended.
- Skipping a level for a "smaller" look. Jumping from H2 to H4 to get a subtler-looking subheading is the single most common nesting error this tool catches.
- Treating any bold, large text as a heading. Visually heading-like text that isn't actually marked up as an H1-H6 tag won't appear in a screen reader's heading navigation at all, and won't show up in this tool's outline either.
- Not re-checking after a redesign. Heading structure is far more likely to break silently when a new page-builder block gets dropped into an existing template than when a page is first written by hand - it's worth re-running this kind of check specifically after a template or theme change, not just after content edits.
Expert Recommendations
Sketch the outline before writing the content: decide what the H1 says, what the H2 sections will be, and roughly what falls under each one. Writing headings after the fact tends to produce decorative labels; planning them first tends to produce a structure that actually organizes the page. Keep the H1 unique, specific to that page, and aligned with what the page is actually about - not a generic template string repeated site-wide.
When in doubt about which level a heading belongs at, ask what it would look like as a bullet-point outline on paper, ignoring how it's currently styled. If the answer doesn't match the current markup, that's the fix - not a font-size adjustment.
Related SEO Concepts
Heading structure sits alongside a few other on-page fundamentals worth checking together: title tags and meta descriptions (what shows up in the search snippet itself), overall content structure and topical depth, and the broader overlap between accessibility and SEO that WCAG compliance sits inside. None of these fix each other automatically - a clean heading outline doesn't compensate for a missing meta description, and vice versa.
Limitations to Keep in Mind
- The tool checks structural nesting - heading levels and counts - not whether heading text is well-written, keyword-relevant, or grammatically sound.
- Headings added to the page by client-side JavaScript after the initial load won't be seen, since the check reads the server-delivered HTML.
- It checks one URL per run, not an entire site - for site-wide issues, check your key templates individually.
- A "pass" on the compliance banner means the WCAG 1.3.1 nesting rule specifically is satisfied, not that the page meets every WCAG success criterion.
Run the heading tags SEO tool above against any live URL to see its outline and WCAG 1.3.1 status in a few seconds - it's free, and no account is required.