Meta Tag Analyzer

About the Meta Tag Analyzer

Paste in a page's head section and the analyzer parses it with the browser's native DOMParser, then works through a checklist of on-page fundamentals: title and description length, a mobile viewport tag, character encoding, a canonical link, and the Open Graph and Twitter Card tags that control how the page looks when someone shares it. Each item comes back Good, Warning, or Missing, with the actual detected value shown next to it so it's obvious exactly what was found rather than just a pass-fail flag.

Nothing pasted in gets uploaded anywhere, the parsing happens with a browser API running locally in the tab, which also means there's no waiting on a crawler and no need to grant this tool access to a private staging site or a page that isn't public yet. Pasting the head section from a page still in development works exactly the same as pasting one that's already live.

How the length checks are scored

Title gets marked Good between 50 and 60 characters, Warning between 40 and 70, and Poor outside that. Meta description follows the same shape at 150-160 for Good and 120-180 for Warning. These bands mirror the ranges Google's search results typically display without truncating, they're not a hard technical limit, a 65-character title still renders fine in a browser tab, it's just more likely to get clipped with an ellipsis in a search snippet.

What "Missing" actually means here

A tag flagged Missing wasn't found anywhere in the pasted snippet, DOMParser reads exactly what's provided and nothing else, it doesn't fetch a live URL or wait for any JavaScript on the page to run. That distinction matters for canonical tags, Open Graph tags, or anything else injected client-side by a script after the initial HTML loads, if a tag is added that way, pasting the page's raw view-source output will show it missing here even though a browser eventually renders it. For an accurate read, paste the response actually served by the server, view-source in a browser or a raw HTML export, rather than a snapshot taken from the rendered DOM after scripts have run.

What this catches most often

The most common gap in a quick check like this is a missing og:image, a page can have a solid title and description and still show a blank or broken card when shared on WhatsApp, Slack, or Twitter/X because no image tag was ever added. A missing canonical link is the second most common finding, usually on pages that can be reached through more than one URL, with and without a trailing slash, or with tracking parameters attached.

Twitter Card fallbacks

The Twitter Card section checks for its own twitter:title, twitter:description, and twitter:image tags separately from the Open Graph ones, even though X/Twitter falls back to Open Graph tags when its own aren't present. This tool flags them independently rather than assuming that fallback, since relying on it means the card renders differently, or not at all, on platforms that don't honor the same fallback behavior.

Pairing this with the Meta Tag Generator

The Meta Tag Generator on this site builds the title, description, charset, and viewport tags from a form, and the Open Graph Generator and Twitter Card Generator handle the social tags separately. Running the combined output from all three through this analyzer afterward is a quick way to confirm every tag actually made it into the final page correctly, catching a copy-paste mistake or a tag that got dropped during a template edit before it ships.