Heading Structure Analyzer
Analyze your page's heading hierarchy for SEO and accessibility. Detect missing H1 tags, skipped levels, and get recommendations for better structure.
Heading hierarchy is mostly an accessibility problem dressed up as an SEO problem.
Most of the heading advice you read online is wrong, or at least wildly out of date. The classic rule was: one H1 per page, then H2s, then H3s, never skip a level. That rule comes from the HTML4 outline, which browsers and screen readers still rely on. It does not come from Google. Google has been on record for years saying multiple H1s are fine and that they treat headings as one signal among many, not as a strict outline they walk top to bottom.
The reason heading structure still matters is screen readers. People who use VoiceOver, NVDA, or JAWS navigate a page by jumping heading to heading with a single keystroke. If your H2 is followed by an H5 because the H5 happened to be styled the way the designer wanted, that user lands somewhere confusing and bounces. WCAG 2.2 Success Criterion 1.3.1 covers this directly, and your legal exposure on accessibility has gone up sharply in the last few years.
The other reason to care is that headings are how you signal subtopic structure to whatever is parsing your page next, and right now that includes more than Googlebot. AI overviews, Perplexity, ChatGPT browsing, and every other extractor reads headings as section boundaries. They use them to decide which chunk of your page answers a given query. Get the hierarchy wrong and they grab the wrong paragraph, or skip your page entirely in favor of one that is easier to chunk.
What this tool does is pull the rendered DOM, walk every heading from H1 through H6, and flag the patterns that actually matter: more than one H1, skipped levels, empty headings, headings used purely for font sizing, and headings buried inside elements that screen readers ignore. It does not lecture you about ideal length. It tells you what is structurally broken, what is borderline, and what is fine but worth a second look before you publish.
One last thing worth saying out loud. The HTML5 outline algorithm, the one that was supposed to let you nest sections and reset heading levels per section, was never implemented by any browser or assistive technology. So even though your spec-purist friend insists it is fine to have five H1s wrapped in five article tags, in practice the document outline that screen readers and bots see is still the flat one. Build for that.
When the Heading Structure Analyzer is the right tool
Before launching a new landing page
You wrote the copy in a doc, the designer styled it in Figma, and somewhere between those two steps the H2 became a span with a class of heading-2. Run the page once before launch to catch the gap between what looks like a heading and what is actually marked up as one.
After a CMS or theme migration
WordPress to Webflow, Shopify theme swap, headless rebuild. Heading structure is the first thing that breaks because templates handle the wrapper element differently. You usually find out months later when an accessibility audit lands on your desk.
When debugging an AI overview that picked the wrong paragraph
If Google or Perplexity is quoting a sentence from your page that is not the answer you wanted them to surface, your section structure is the first place to look. The extractor walks headings to decide what a section is about. Bad headings, wrong chunk picked.
On long-form content with multiple subtopics
Pillar pages, guides, anything over 2000 words. The risk of skipped levels and stylistic heading abuse goes up linearly with length, and so does the cost of getting it wrong because more of the page depends on the structure being legible.
During a quick competitor teardown
Drop a competitor URL in and you get a clean outline of their page in about three seconds. It is the fastest way to see how they structured a topic, which subheadings they prioritized, and whether their hierarchy is actually as tight as the SERP snippet suggests.
How to use the Heading Structure Analyzer
Audit H1–H6 hierarchy for accessibility and SEO.
Submit the page URL
Enter any URL to extract its full heading tree.
Review the outline
See all H1–H6 in document order with warnings for skips and duplicates.
Fix structural issues
Re-arrange headings so each level descends logically from the H1.
Mistakes we see all the time
Using heading tags for visual weight
A standalone callout in the sidebar that says "Free shipping" should not be an H3 because the designer wanted it bold and 22 pixels. Use a span or a paragraph with the right class. Heading tags are structural, not decorative.
Skipping from H2 straight to H4
Usually happens because someone deleted the H3 above it and never adjusted the level. Google will not penalize you, but a screen reader user lands on the H4 expecting it to be a subsection of an H3 that does not exist. Confusing and fixable in 30 seconds.
Putting your logo or nav inside an H1
Common in older themes. Your H1 ends up being your site name on every single page, which means every page tells Google the same thing about its primary topic. The H1 should describe the page, not the brand.
Empty or icon-only headings
An H2 wrapping an SVG icon with no text alternative. The DOM has a heading element but there is nothing for a screen reader or extractor to read. Either add visually hidden text or do not use a heading at all.
Heading Structure Analyzer — Frequently Asked Questions
- What does the heading analyzer check?
- It extracts every H1–H6 on a page and flags missing levels, multiple H1s, and skipped hierarchy.
- Can a page have more than one H1?
- HTML5 allows it, but most SEO and accessibility audits expect a single primary H1 per page.
- Why does heading order matter?
- Screen readers and search engines use heading order to map document structure — skipped levels confuse both.
- Does Google actually use H1 tags as a ranking signal?
- Google has said H1s are a useful signal but not a strong one, and that they will work out what a page is about from the body copy even if the H1 is missing or weak. Think of H1 as a clarity nudge, not a lever you pull for rankings. The bigger gains come from getting the title tag right.
- Is it bad to have the same H1 on every page of my site?
- Yes, but more for clarity than for rankings. If every page H1 says "Acme Corp" you are wasting the most prominent piece of structural copy on the page. Make the H1 describe what is on that specific page. Google is smart enough to figure it out either way, but you are throwing away a free signal.
- How many headings should a page have?
- There is no right number. Short landing pages can live with an H1 and two H2s. A 4000-word guide might have 30 headings and still be fine. The question is whether someone scanning the page can understand the structure from the headings alone. If yes, you have the right amount.
- Do I need to worry about heading order for SEO if my site is for screen reader users a lot?
- Yes, and the accessibility case is stronger than the SEO case. WCAG 2.2 expects logical heading order. ADA and EAA enforcement has picked up since 2024 and skipped heading levels show up in almost every automated accessibility scan. Fix them once and you check two boxes at once.
- What about pages built with React, Vue, or other JS frameworks?
- The analyzer pulls the rendered DOM, so it sees what the user actually gets after hydration. The classic problem with JS frameworks is that developers reach for div with role of heading instead of an actual heading tag, which works for some screen readers and not others. Use the real tag whenever you can.
- Should section titles inside a tab or accordion be headings?
- Yes, and they should be at the level that fits the surrounding outline. The fact that the content is collapsed does not change its place in the document structure. Search engines read collapsed content, screen readers expose it, and your outline should reflect it.
- Will fixing my headings move my rankings?
- Probably not on its own. Heading fixes alone rarely show up in Search Console as a ranking change. What they do is make the page easier for everything downstream (Google, AI extractors, screen readers, your own writers) to understand. That compounds over time even if it does not spike a chart.
Headings are cheap to fix and expensive to ignore. The team that takes 20 minutes to clean up a page outline tends to be the same team that catches the broken canonical and the missing alt text on the way through. Treat this tool as a quick sanity check, not a rankings lever, and you will get the right amount of value out of it.