Meta Tags Checker

Read the live title, description, robots, canonical, H1s and social tags on any public URL, then draft a snippet against a SERP-style preview.

A meta tags checker reads the metadata that is live on a public URL right now, so you act on the real tags instead of a cached copy that might be a week stale. Paste a URL and it reads the title tag, the meta description, robots directives, the canonical, your H1s, and the Open Graph and Twitter fields server-side, scores them against the page role you pick, and flags the issues that matter. The snippet lab lets you draft a title and description and set them next to the live version before you ship. It is built for the morning after a theme swap, an SEO plugin change or a migration, when the body changed but the old snippet signals just sat there going stale and nobody noticed for weeks.

Queries run through the PeopleAreGeek lookup service. We log nothing.

Live metadata audit and snippet workshop

Paste a public URL. I'll go read what's actually live on it right this second: the title tag, the meta description, robots directives, the canonical, your H1s, plus the Open Graph and Twitter fields. No guessing from some cached copy that might be a week old. Then you get a snippet draft, a live preview, and a fix list that's wired straight to what the page is really sending back.

The audit reads the page server-side, so these are the real tags. One caveat, and I'll repeat it all day: Google rewrites snippets whenever it feels like it. So treat the preview as a sanity check on your copy. Not a screenshot of what'll actually show up out there.

What a meta tags checker actually does

A meta tags checker reads the metadata that is live on a public URL right now and lays it out so you can act on it: the title tag, the meta description, robots directives, the canonical, your H1s, and the Open Graph and Twitter fields. Because it reads the page server-side, you see the real tags, not a cached copy that might be a week stale. Most metadata tools shrink this down to two character counters. The questions that matter are bigger than that: does the title tell a searcher what they are getting, does the description give them a reason to click, is the canonical pointing at the version you want to keep, and do the robots directives match what this page is supposed to be in the first place.

Title tags and descriptions are editorial work

A title tag writes for two readers at once. The search engine wants a clear topic signal. The human wants a reason to pick your result over the five crowding it. The titles that work put the real task up front and drop the filler. The description plays a different game entirely. It is not a ranking slogan, it is a small promise about what you get when the page answers your question. Counters help, but they do not finish the job, which is why the snippet lab on this page lets you draft a title and description and set them right next to the live version before you ship.

Robots, canonical and headings change the meaning

The prettiest snippet will not save a page that is quietly flagged noindex. A canonical aimed at a different URL might be exactly what you wanted for duplicate content, or it might be a leftover from a template you copied months ago. Two H1s usually means the theme and the article body are shouting the same heading at each other. None of these show up when the page looks fine in the browser, which is the whole point of reading them off the live response.

  • Robots directives tell you whether something is throttling your indexing, your snippet, or both.
  • Canonical URL is the page saying which version it would rather you kept.
  • H1 structure shows whether your topic is focused or accidentally said twice.
  • HTTP context keeps the status code and headers sitting next to the tags.
  • Social metadata tells you if a share looks like the same page people found in search.

A practical metadata workflow

Test the real public URL, not a staging preview or a link with tracking junk on the end. Check the status and the robots line first, then the canonical, because there is no point polishing a title on a page that is quietly noindexed. Say the title, the H1 and the page's actual job out loud, and if they disagree the title is wrong. Write a description that names the task and the payoff, then run the audit again once you publish, because plugins and themes love to quietly overwrite your tags on the way out the door.

Frequently asked questions

Does a good meta description guarantee that Google uses it?

No. If a chunk of your page body matches the search better than your description does, Google grabs that instead and stitches its own snippet. It is still worth writing one, because it is the default Google falls back on, and the act of writing it forces you to figure out what the page is actually about.

Should every page have one H1?

For articles and tools, one clear H1 is the easiest setup to keep sane over time. It is not a hard rule, but multiple H1s usually mean your theme and your content are both stamping out a heading without talking to each other. The audit counts them so you can spot the duplication.

What is the ideal title and meta description length?

Aim for titles around 50 to 60 characters and descriptions around 150 to 160. That keeps both from getting cut off with an ellipsis in the results. Google can still rewrite either one, but a tag that fits cleanly tends to be left alone far more often than one that overruns.

Why does Google show a different title than mine?

Because Google decided yours was not pulling its weight. Usually that means it read as vague, stuffed with keywords, or it promised something the page did not deliver. The fix is to write one title that is short, accurate and genuinely unique to the page. Google mostly leaves that kind alone.