See your page the way an assistant reads it
Headings decide whether a reader can scan your page and whether an assistant can match a question to a section. Paste HTML or Markdown and see the structure laid out by rank.
Paste a page to see its heading structure.
Why does it matter how many headings are questions?
People search in questions. A heading that is literally the question someone typed is a direct match; a one-word label like Pricing is something a system has to infer its way to, and inference is where you lose to a page that did not require any. It is the commonest reason a well-written page never gets quoted.
Should every heading be a question?
No, and a page of nothing but questions reads badly. The test is per section: does this section answer something a person would ask. If yes, make the heading that question. Narrative sections stay as they are.
What is wrong with skipping a heading level?
An H1 followed by an H3 tells a screen reader there is a missing section between them. It is an accessibility problem first and a structure problem second, and it usually happens because a heading was chosen for its size rather than its rank.
Why does it flag headings with little text under them?
Because a heading with nothing beneath it gives an assistant a question and no answer. It is also the signature of a heading used as a label on a design element rather than as the title of a section.
Can I paste Markdown instead of HTML?
Yes. Both are read and whichever produces more headings is used, so you do not have to say which you pasted.
Other tools
This tool checks one page at a time. Visorank does the same work across every page on your site continuously, and shows you which queries people actually search rather than estimates.
What Visorank does