Headings are the skeleton of a page. A clean H1 → H2 → H3 outline helps both readers and Google understand what the page is about. It also affects accessibility scores.
This tool fetches the rendered HTML of any URL, extracts every heading and flags the structural mistakes that hurt SEO and screen-reader users the most.
Where this tool actually helps
Quick outline check before publishing
Confirm you have exactly one H1 and the H2s cover the sections you promised in the intro.
Migrating from a legacy CMS
Old templates often stuff branding into H1s. A quick scan reveals which templates need fixing.
Auditing a client's site
Level jumps and empty headings are common. Fixing them is a fast accessibility win.
How to read the result
The count row shows how many of each level exist. One H1, several H2s, and a handful of H3s is the normal shape.
The outline below shows the actual text, indented by level. Look for empty headings (often decorative divs mistagged as headings) and jumps like H2 → H4.
Common mistakes we see
- Wrapping a logo in an H1 on every page. Every page then claims the same brand name as its title.
- Using multiple H1s because the CMS makes it easy. Consolidate.
- Styling H2s to look small and using H1s for callouts. Choose visual weight with CSS, not tag level.
- Leaving empty <h3></h3> tags because a designer used them for spacing.
FAQs
- Does this see JS-rendered headings?
- Yes. Firecrawl renders the page before extracting HTML, so React and Vue apps work.
- What about headings inside iframes?
- Iframe content is a separate document and is skipped, same as Google would.
- Can I audit password-protected pages?
- No, only publicly reachable URLs.
A note from Nimitt
A tool gives you a number. A person tells you what to do with it. If you want a straight answer on your site, send it over. I read every one myself.