Skip to main content
MetaManager reads a page’s metadata and tells you three things: what tags are there, how the page will look when someone shares it on eight different platforms, and exactly what to change. One GET request returns all of it.

Check a URL

One request, one report. No key, no account, no signup.

Read the report

Score, metadata, previews, issues — what every field means.

Preview on eight platforms

Google, X, Facebook, LinkedIn, Discord, WhatsApp, Slack, Telegram.

Every issue code

The full reference, with what each one means and how to fix it.

​
Base URL

​
The whole API, in one line

That works right now, from any terminal, with no credentials. The checker is free and stays free — see rate limits for the ceilings.

​
What comes back

A single JSON document: The report guide walks through each one.

​
What it is not

MetaManager checks metadata. It does not render pages, run JavaScript, take screenshots, or crawl sites. That last one matters for accuracy: metadata injected by client-side JavaScript will not be seen, because no crawler that reads your tags runs JavaScript either. If a preview looks wrong here, it looks wrong on Facebook too. That is the point.
Metadata is read from the HTML as served. This is the same view Googlebot, Slackbot and Twitterbot get — which is why a page that looks perfect in your browser can still score badly here.