Meta Tag Generator
Fill four fields and copy a block of head meta tags.
Paste a page's HTML and get its heading outline (H1 to H6), plus a check for a missing or duplicated H1 and for skipped levels. The check runs in your browser.
Your browser is preparing the tool. It runs 100% locally.
Paste a page's HTML and the tool pulls out every heading from H1 to H6, shows them as an indented outline, and flags three common issues: no H1, more than one H1, or a skipped level (such as an H2 jumping straight to an H4). It is a structural check for accessibility and clarity: it reads the heading tags, not the quality of the content. Your browser does all the work.
Paste the HTML of a page and you get its heading skeleton: each H1 to H6 in order, indented by level, so you can see the document outline at a glance. Beneath it, the tool lists any structural warnings, or tells you the structure looks good.
It checks the shape of your headings, not their wording. A clean outline (one H1, then H2s for sections and H3s beneath them, with no jumps) helps screen-reader users navigate and helps search engines understand how the page is organised.
The tool scans the pasted HTML for heading tags, capturing each heading's level and its text (stripping any tags nested inside). It prints them as an indented list, then runs three checks: is there exactly one H1, and does any heading jump more than one level deeper than the one before it.
Going back up the hierarchy is allowed. An H4 followed by an H2 is fine, because that closes a subsection. The warning is only for going down too fast, like an H2 straight to an H4, which leaves a gap in the outline.
No H1 found: the page has no top-level heading Multiple H1s: more than one H1 on the page Skipped level: a heading jumps down more than one rank (e.g. H2 then H4) Otherwise: Structure looks goodGoing back up a level (H4 then H2) is not flagged, because that closes a subsection and is correct.
| Input | pasted page HTML |
|---|---|
| Detects | H1 through H6 tags |
| Output | indented outline + warnings |
| Checks | missing H1, multiple H1s, skipped levels |
| Parsing | regex (not a full DOM parser) |
| Heading text | nested tags stripped |
| Where it runs | In your browser; the HTML is not uploaded |
It reads the HTML with a regular expression, not a full browser parser. Clean, well-formed heading tags are detected reliably, but unusual markup, such as a heading whose opening tag has a stray angle-bracket character inside an attribute, or broken nesting, can be missed or misread. Paste the real rendered HTML for best results.
It checks structure, not substance. It tells you whether the H1 to H6 skeleton is sound, not whether a heading is descriptive, keyword-relevant or a match for the section below it.
The skipped-level warning fires only for downward jumps of more than one rank, like H2 to H4. Going back up (H4 to H2) is correct and is not flagged, since that closes a subsection.
Multiple H1s are flagged as a warning, but this is an accessibility and clarity nudge, not a Google error. Google tolerates several H1s. The warning reflects that screen readers, lacking the never-implemented HTML5 outline, treat every H1 as equally top-level.
It analyses whatever HTML you paste, not the live page. If your headings are added by JavaScript after load, copy the rendered HTML from the browser's inspector rather than the raw source, or they will be missing.
Confirm a logical heading order for screen-reader navigation.
Verify one clear H1 and a tidy section hierarchy.
Catch a layout that skips from H2 to H4 across a page.
See a long article's outline to check its structure.
Need the headings from a live URL automatically? A crawler or browser extension reads the rendered page for you. Want a full accessibility audit? A tool like axe or WAVE checks contrast, labels and ARIA too.
Extracts the H1 to H6 outline with a regular expression and flags a missing H1, multiple H1s or a skipped level. The page explains that this is a structural check (not content quality), that going back up a level is allowed, and that multiple H1s are an accessibility nudge rather than a Google error.
Fill four fields and copy a block of head meta tags.
Top words in your content and the share each one takes.
Add utm_source, utm_medium and utm_campaign to any URL.
Write the og: tags that control link previews on social apps.
See roughly how a title and description could look in Google.
schema.org JSON-LD for articles, products, FAQs and more.
It's free, needs no account, and nothing you enter is sent to a server.