Skip to content

Meta Tag Checker

See what a page tells search engines and social platforms about itself — title, description, canonical, Open Graph, Twitter cards and favicons.

About Meta Tag Checker

Paste a URL and see exactly what the page tells search engines and social platforms about itself: the title and description with their real character counts, the canonical, the Open Graph and Twitter card tags, the declared language and charset, and every favicon it links. Each result comes with notes — a title that will be truncated, a canonical pointing somewhere else, a missing og:image that leaves shared links without a preview. It reports what the page declares rather than what it should declare, because a canonical pointing elsewhere is sometimes correct and always worth knowing about.

  • Title and description with the character counts that actually get truncated
  • Canonical, robots, viewport, language and charset
  • Open Graph and Twitter card tags, read from both name= and property=
  • Every declared favicon and apple-touch-icon, resolved to absolute URLs
  • Notes that say what to change, not just what is missing

How to check a page's meta tags

  1. 1Paste the URL of the page you want to check.
  2. 2Select Check page.
  3. 3Read the notes first — they flag anything that will cost you a click.
  4. 4Expand the tag list to see everything the page declares.

Frequently asked questions

What is a meta tag checker for?
Seeing what a search engine or social platform reads from your page, without opening dev tools. It is the fastest way to confirm a deploy actually shipped the tags you wrote.
Why does it say my canonical points elsewhere?
Because the canonical link on the page names a different URL than the one you checked. That is sometimes deliberate — a print version pointing at the main page, for instance — but it is also the most common reason a page never gets indexed.
What length should my title and description be?
Titles are usually cut around 60 characters and descriptions around 160. Below roughly 70 characters a description wastes the space it was given. The tool reports the real counts so you can judge.
Does it check pages behind a login?
No. It sends a plain GET with no cookies or credentials, so it sees what an anonymous visitor and a search crawler would see — which is usually the point.
Why can it not check my localhost site?
Private and local addresses are blocked deliberately. The request comes from our server, so allowing them would let anyone use this tool to probe machines on our network.

Other developer tools