> ## Documentation Index
> Fetch the complete documentation index at: https://metamanager.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MetaManager

> Check how any page looks when it is shared, see what is missing, and copy the fix.

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.

<CardGroup cols={2}>
  <Card title="Check a URL" icon="bolt" href="/docs/getting-started/quickstart">
    One request, one report. No key, no account, no signup.
  </Card>

  <Card title="Read the report" icon="file-code" href="/docs/guides/the-report">
    Score, metadata, previews, issues — what every field means.
  </Card>

  <Card title="Preview on eight platforms" icon="share-nodes" href="/docs/guides/previews">
    Google, X, Facebook, LinkedIn, Discord, WhatsApp, Slack, Telegram.
  </Card>

  <Card title="Every issue code" icon="list-check" href="/docs/guides/issues">
    The full reference, with what each one means and how to fix it.
  </Card>
</CardGroup>

## Base URL

```text theme={null}
https://metamanager.dev
```

## The whole API, in one line

```bash theme={null}
curl 'https://metamanager.dev/inspect?url=https://example.com'
```

That works right now, from any terminal, with no credentials. The checker is free and stays free — see [rate limits](/docs/operations/rate-limits) for the ceilings.

## What comes back

A single JSON document:

| Field       | What it holds                                                              |
| :---------- | :------------------------------------------------------------------------- |
| `score`     | 0–100, weighted by how much each missing tag actually costs you            |
| `metadata`  | Every tag found: title, description, canonical, Open Graph, Twitter, links |
| `previews`  | How the page renders on each of eight platforms                            |
| `issues`    | What is wrong, how much it matters, and the exact fix                      |
| `redirects` | The chain followed, if any                                                 |

[The report guide](/docs/guides/the-report) 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.

<Note>
  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.
</Note>