HandyBench

Website Meta Tag Checker

See exactly what meta tags, OG data and SERP snippet any page sends.

This check runs through this site's own server, so it works for any public URL — no CORS or browser restrictions.

How to use the Website Meta Tag Checker

  1. 1 Enter any public page URL and click Check meta tags.
  2. 2 Review the title, description, canonical, robots and other core tags with length hints.
  3. 3 Check the Open Graph and Twitter Card tables and the SERP and social share card previews.

What happens when you click Check

Unlike the generator tools on this site, this one does not run in your browser alone. Your URL is sent to this site's own /api/page-meta endpoint, a Cloudflare Pages Function that fetches the page server-side, follows redirects and parses the returned HTML with HTMLRewriter. The results come back as structured data and are rendered in sections. Because the server does the fetching, you avoid browser cross-origin limits and can inspect any public page. The same request is also guarded so it cannot be pointed at private or internal addresses.

What you get back

  • Google SERP preview using the page's title, description and hostname.
  • Title and description each with a character count, a pixel width measured in your browser, and a "likely truncated" flag past 600px (title) or 920px (description). Colors are red when over the pixel limit, amber when outside the suggested range of 30 to 60 characters for titles or 70 to 155 for descriptions, and green otherwise.
  • Core tags: canonical, robots, lang, charset, viewport, favicon, the final URL after redirects and the HTTP status code.
  • H1 headings: the first three found on the page.
  • Open Graph and Twitter Card tables and an Other meta tags table for everything else.
  • Social card preview that falls back from og:title and og:description to the plain title and description when the OG versions are missing. The image URL is displayed as text, not loaded.

Worked example

Checking a blog post might return a title of 78 characters, flagged red as likely truncated, a canonical pointing at the same URL without a trailing query string, a robots value of index, follow, a status of 200, and two H1s. That tells you three things to fix: shorten the title, remove the duplicate H1, and add an og:image because the OG table has none. A final URL different from the one you typed means the page redirected, for example from http to https or to a trailing-slash version, which is worth confirming is intended.

Reading the key tags

FieldWhat to look for
CanonicalAbsolute URL, normally pointing at itself
RobotsUnexpected noindex on a page you want ranked
HTTP status200 expected; 3xx, 4xx or 5xx need investigating
ViewportPresent for mobile-friendly rendering
H1Exactly one, matching the page topic
og:imagePresent, ideally 1200x630

Limits and common mistakes

  • JavaScript-rendered tags are invisible here. The tool reads the initial server HTML. If a framework injects the title or canonical after loading, they appear missing even though Googlebot, which renders JavaScript, may see them. Compare with a "view source" check.
  • Some sites block automated requests. A firewall or bot protection may return an error or a challenge page instead of your content, so a failure does not always mean your tags are wrong.
  • Only the first three H1s are listed. Several H1s is a sign to review your template, though it is not a penalty on its own.
  • Pixel widths are approximations measured with Arial, as in the SERP snippet checker.

For a step-by-step audit routine, see the guide to checking meta tags. To dig deeper into duplicates, use the canonical checker, and to fix what you find, build replacements with the meta tag generator.

Examples

  • ▸ A title over roughly 60 characters or 600px is flagged "likely truncated" in the SERP preview, just as Google would cut it off.
  • ▸ A page with no og:image shows "No og:image set" in the social card preview and an empty Open Graph table row, so you know to add one.
  • ▸ A final URL of https://www.example.com/ for an entered http://example.com shows the redirect your visitors and crawlers actually follow.

Frequently asked questions

What does this tool actually check?

It fetches the page and parses the server-rendered HTML: the <title>, meta description, canonical link, robots and viewport tags, charset, favicon, the first three <h1>s, and all Open Graph / Twitter Card meta tags.

Does it work on any website, or only ones I own?

Any public URL — the check runs through this site's own server, not your browser, so there are no CORS or same-origin restrictions like a client-side fetch would hit.

Why don't you load my og:image directly in the preview?

The image URL is shown as text instead of being embedded, since it may point to a slow, private or unreachable host. You can open it yourself to confirm it loads.

Does this see JavaScript-rendered meta tags?

No — it reads the initial HTML response, the same way most crawlers and link-preview bots do. Tags injected client-side after hydration will not show up here even though a browser (or Googlebot, which does render JS) might see them.

What do the red, amber and green length hints mean?

Red means the text is wider than 600px (title) or 920px (description) and will probably be truncated. Amber means it fits but is outside the suggested range of 30 to 60 characters for titles or 70 to 155 for descriptions. Green means it is within both.

Why does the final URL differ from the one I entered?

The server follows redirects, so the final URL and HTTP status show where the request ended up. A change from http to https or to a trailing-slash version is normal, but unexpected redirect targets are worth investigating.

Related guides