Tool
What the Heading Tag Analyzer does
Heading Tag Analyzer: checks Headings found and H1 count from Page HTML.
Supply Page HTML and you get Headings found and H1 count back. The result recalculates on every keystroke without a button press or a page reload.
It is mostly used by people publishing a page. Small on-page details decide whether a listing gets clicked or scrolled past.
There is no back end here. The calculation runs where you are sitting, not on a server somewhere.
The rest of this page documents each field, the method, and a worked example built from the values the heading tag analyzer loads by default.
What do the Heading Tag Analyzer fields mean?
The Heading Tag Analyzer uses 1 input. The defaults are there to be replaced. They exist so the tool is never showing an empty result.
| Field | What to enter | Default |
|---|---|---|
| Page HTML | paste or type any amount of text | <h1>Choosing a mortgage</h1> <h2>Fixed vs variable</h2> <h3>When fixed wins</h3> <h2>What lenders check</h2> |
How does the Heading Tag Analyzer work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same check.
Checks happen up front, so errors surface next to the form instead of hiding in the output.
What a typical run looks like
You provide: Page HTML
What happens: the file is read into memory by your browser, processed locally, and offered back as a download. It is never uploaded.
You get back: the result as a file you can save, with a one-line summary beside it.
Nothing queues behind a server, so the wait is your device working, and the size limit is set by memory rather than by an upload cap.
The one-H1 rule is convention, not a technical requirement
The HTML5 specification technically permits multiple h1 elements, one per sectioning root, but SEO and accessibility practice have both settled firmly on exactly one h1 per page regardless of what the spec allows.
Worth knowing
- Screen reader users commonly navigate by jumping between headings, relying on heading level to convey structure the way a sighted user relies on font size and position. A single clear h1 followed by a logical h2/h3 hierarchy is what makes that navigation work.
- Skipping a heading level (h2 straight to h4) breaks that same navigation model: a screen reader user jumping by level has no way to know a level was skipped versus never present in that section.
- An empty heading, present in the markup with no text, is worse than no heading at all for a screen reader and a crawler alike, since it creates a landmark that leads nowhere.
- Multiple h1 elements carry no directly documented ranking penalty, but they do muddy the single clearest signal available for "this is what this page is about." There is little upside to using more than one.
How to use it
- Paste your content into Page HTML.
- The tool reacts immediately rather than waiting for you to finish the form.
- The results panel then shows Headings found and H1 count.
- Both Copy Link and Print capture the current state, so pick whichever suits how you file things.
What this tool does not do
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- This inspects the markup you supply; it cannot see server headers or your live rankings.
- It cannot detect a typo that happens to fall inside the valid range.
Frequently asked questions
One thing: Page HTML. A starting value is in place for each, letting you treat it as a what-if tool rather than a data-entry form.
Not at all: the whole thing runs offline once the page has loaded, which tells you nothing is being sent.
It costs nothing, and there is no limit on repeat use.
It implements the published definition directly, without shortcuts or approximations.