Skip to content
ToolBoxGenie

Meta Tag Analyzer

Developer Tools · Added 18 August 2026

Paste a page's HTML and get a straight reading of its meta tags: what is there, what is missing, what is the wrong length, and what the share card will look like on Facebook, LinkedIn and X. It works on a page behind a login, on a staging build and on localhost — because it reads what you paste rather than fetching a URL.

Open the page, press Ctrl+U (Cmd+Option+U on Safari) and paste the source. Parsed entirely in your browser.

How to use the meta tag analyzer

  1. 1Open the page you want to check and view its source — Ctrl+U, or Cmd+Option+U in Safari.
  2. 2Copy the whole document and paste it into the box.
  3. 3Press Analyse to see the checks, ranked as pass, worth checking, or needs fixing.
  4. 4Switch to All tags for the raw values and the heading outline.
  5. 5Switch to Social preview to see the card each platform would build from your tags.

Examples

A title that will be cut off

Input
A 78-character title tag
Result
Flagged at about 660px — desktop results truncate near 600px

Missing Open Graph image

Input
A page with og:title and og:description but no og:image
Result
Warned: most platforms show a bare text link without an image

An accidental noindex

Input
<meta name="robots" content="noindex, follow">
Result
Flagged as needs fixing — the page is asking to stay out of search results

A staging noindex reaching production is one of the most expensive SEO mistakes there is.

About the meta tag analyzer

The tags that still matter

The list is short. A title tag, because it is the clickable line and the strongest single on-page signal. A meta description, because it is the copy underneath. A canonical, because without one every tracking parameter creates a candidate duplicate. A viewport, because without it mobile browsers render the page at desktop width. A charset, because a wrong guess mangles every accented character.

Almost everything else is legacy. The meta keywords tag has been ignored by Google since 2009 and by Bing for nearly as long. Meta author, revisit-after and rating do nothing for search. If they are on your page they are harmless, but adding them is time better spent elsewhere.

Open Graph and why it outgrew Facebook

Open Graph was Facebook's protocol, published in 2010. It became the de facto standard for link previews everywhere: LinkedIn, WhatsApp, Slack, Discord, iMessage and dozens of others read og: tags, and X falls back to them when the twitter: equivalents are absent.

That makes four tags disproportionately valuable — og:title, og:description, og:image and og:url — because they control how a link looks every time anyone shares it anywhere. A page without og:image is shared as a bare text line, which measurably fewer people click. Twitter-specific tags are only worth adding when you want a different image or card type on X specifically.

Reading the heading outline

The outline view lists every heading in document order at its level, which makes two problems visible at a glance: levels skipped for visual reasons — an h1 followed by an h4 because that size looked right — and headings used as styling rather than structure.

Both matter more for accessibility than for search. Screen reader users navigate a page by its headings, and a broken hierarchy makes that navigation misleading. HTML5 permits multiple h1s and Google handles them fine, but a single clear h1 that states what the page is about remains the easiest structure for both audiences to follow.

Frequently asked questions

Why does it not just fetch a URL?
Two reasons, and both favour pasting. Fetching would mean sending the address you are working on to a server, which is exactly the sort of quiet data collection this site avoids. And the pages most worth checking before launch — a staging build, a page behind a login, something on localhost — cannot be fetched from the outside at all. View Source works on every one of them.
Should I paste the source or the rendered DOM?
The source, from View Source, is what a crawler receives first and is the right thing to audit. If your tags are injected by JavaScript they will not appear there — which is itself the finding, since a tag that only exists after hydration is read less reliably. To check what the DOM ends up as, copy the outerHTML of the document element from the browser console instead, and treat any difference between the two as the thing to look into.
What is the ideal title length?
Google truncates by pixel width, not character count, so a title of wide capitals runs out sooner than one of narrow lowercase letters. The practical limit is around 600px on desktop, which is roughly 55–60 typical characters — the tool estimates the pixel width rather than counting characters alone. Worth knowing: Google rewrites titles it considers unhelpful in a large share of results, so an accurate, specific title matters more than an exactly-sized one.
Do meta descriptions affect rankings?
No, and they have not for many years. What they affect is the click-through rate, because the description is the sales copy under the link — when Google uses it, which is roughly a third of the time. The rest of the time it writes a snippet from the page because that matches the query better. A good description is still worth writing; it is just not a ranking lever.
Why does my share card look different on the actual platform?
Two likely reasons. Every platform caches what it fetched the first time a URL was shared, sometimes for days — use the Facebook Sharing Debugger or the LinkedIn Post Inspector to force a refresh after changing a tag. And each platform crops and truncates differently, so the previews here reproduce the fallback logic and the approximate proportions rather than being screenshots.
Are the images loaded?
No. The image URL is shown as text rather than fetched, because loading it would send a request from your browser to that server. What matters for the audit is whether the tag is there and points somewhere sensible; whether the file loads is a job for the platform's own debugger.

Related tools