Heading outline
auditor
Your h1-h6 headings are the skeleton of the page - screen readers, featured snippets and AI answers all read it. Paste your HTML and see the outline as a tree, with every broken bone flagged.
What does your page
outline look like?
Every page Yetty builds gets one h1 and a proper heading tree from the start - and stays auditable as you and your AI edit it.
Three very different readers,
one skeleton
Screen readers jump by heading
Blind visitors do not scroll - they pull up the heading list and jump. A skipped level or an empty heading is a broken staircase for them.
Featured snippets quote your h2s
Google builds "People also ask" answers and list snippets from heading + paragraph pairs. Clear question-shaped h2s are snippet bait.
AI assistants read the tree
ChatGPT, Perplexity and Google AI answers chunk your page by its headings. A scrambled outline means your best point gets attributed to the wrong topic - or skipped.
One h1, always
The h1 answers "what is this page about" in one line. Zero h1s means nobody knows; two means everybody guesses.
Never skip a level
h2 to h4 with no h3 between them reads like chapter 2 followed by section 2.1.1. Nest one level at a time and the hierarchy explains itself.
Headings are not font sizes
Picking h4 because it "looks right" is the root of most broken outlines. Choose the level by meaning and restyle it with CSS.
People also ask
How many h1 headings should a page have?
One. HTML5 technically allows more, but screen readers, featured snippets and AI assistants all treat the h1 as "what this page is about" - give them two and they have to guess. Keep a single h1 that states the page topic, then structure everything under it with h2 and h3.
Is it really a problem to jump from h2 straight to h4?
Yes, and it is not about rankings first - it is about people. Screen reader users navigate by heading level, and a skipped level reads like a missing chapter. Search engines and AI answer extractors use the same hierarchy to understand which point belongs under which; a skipped level scrambles that map.
Do headings inside my nav and footer count?
They are part of the document outline, which is why this tool shows them - marked with their context - instead of hiding them. A heading inside site chrome is usually fine, but if your only h1 lives in the header logo, or your footer h2s outrank your content h2s, the outline of your actual content gets drowned out.