What is Heading Structure Analyzer?

A heading structure analyzer parses HTML and visualizes the H1–H6 hierarchy as a tree. It shows skipped heading levels, duplicate H1 tags, and structural issues that hurt SEO rankings and screen reader navigation.

Paste a full HTML document or a single article and the analyzer extracts every h1 through h6 tag in document order. It flags skipped levels (h2 jumping straight to h4), more than one h1 on the page, empty headings, and headings hidden inside scripts. The tree visualization makes broken hierarchies obvious at a glance.

How to use

1. Step 1 — Paste your HTML source, or Markdown using # for headings.
2. Step 2 — The tool extracts all heading tags and displays them as a nested tree with level indicators.
3. Step 3 — Review flagged issues like skipped levels or missing H1, then export the analysis report.

When to use

• Auditing a blog post before publishing so screen readers and crawlers parse the outline cleanly.
• Reviewing a competitor's article structure to understand how they organize on-page topics.
• Catching WordPress or CMS theme bugs that wrap sidebars in stray h2s outside the main flow.

Result

Paste your blog post's HTML and spot where the sidebar jumps from H2 straight to H4. That gap trips up screen readers and search crawlers.

FAQ

Do skipped heading levels actually hurt SEO?

Indirectly. Google itself says heading order isn't a ranking factor, but skipped levels confuse screen readers, hurt readability, and often signal a poorly structured page. Pages that are easier to read tend to perform better on intent matching and dwell time.

Is it bad to have more than one h1 on a page?

HTML5 technically allows multiple h1s inside sectioning elements, but most CMS templates and SEO tools still expect a single h1 that names the page. Two h1s usually indicate a template bug or a misused widget rather than intentional structure.

Can headings inside hidden or collapsed elements still count?

Yes. As long as they're in the HTML, crawlers and screen readers see them. Accordion content, mobile-only sections, and tabs all contribute to the outline even when the user can't currently see them on screen.

Does the analyzer work for AMP, MDX, or JSX source?

It parses raw HTML, so AMP works directly. For MDX or JSX, view the rendered output (DevTools > Elements > copy outerHTML of body) and paste that. Component tags like Heading are invisible to the parser until they render as real h1-h6 elements.

How can I export the report for a content audit spreadsheet?

Use the Export Report button to download a plain-text outline you can paste into a spreadsheet column, or copy the tree directly. The report lists each heading by level, text, and any issues detected, ready to share with editors.

Related Tools