Headings are how a page explains its own structure. Readers scan them, screen readers navigate by them, search engines use them to understand what a section covers, and assistants lift individual sections out of a page when they answer a question. A page with one vague H1 and nothing else is hard for all four.
The Sorank Heading Structure Analyzer pulls the complete outline of any page and shows where the hierarchy breaks.
What a healthy outline looks like
- One H1 that states the subject of the page. Not the site name, not a slogan: the thing this page is about.
- H2 sections that each cover one idea, phrased the way someone would ask about it.
- H3 levels used only to break down an H2, never to jump a level for styling reasons.
- No empty headings, and no headings used purely to make text bigger.
The problems this finds
- Missing H1: common on template driven pages where the title lives in a styled div instead of a heading tag.
- Several H1 tags: valid HTML, but it dilutes the signal and usually means the template is fighting the content.
- Skipped levels: an H2 followed directly by an H4 leaves a hole in the outline that screen readers announce as a missing section.
- Headings that say nothing: "Introduction", "More", "Our approach". They occupy the structure without describing anything.
- Headings stuffed with keywords: a signal of low quality for readers and engines alike.
Why the outline matters for AI answers
Generative assistants do not quote whole pages. They lift passages. A clear heading followed by a self contained answer is exactly the shape of content they can lift with confidence, because the heading tells them what the passage is about and the passage stands on its own. Long unbroken prose forces them to guess where an idea starts and ends, and guessing usually means choosing another source.
The practical version of this: write H2s as the question a reader would type, then answer that question in the first two sentences under it. The rest of the section can add nuance.
How to use the analysis
- Run it on a page that ranks below where you expect and compare its outline with the pages above it. Missing sections show up immediately.
- Run it on your own template once, to catch structural issues that repeat across hundreds of pages.
- Run it before publishing long content, as a last check that the outline reads like a table of contents.

























