Open Graph Checker screenshot

Open Graph Checker

Check a public URL's title, meta description, canonical, robots, Open Graph and Twitter tags from the raw server response, with a SERP-style preview.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
No account needed
Private addresses refused
Nothing stored from the response

What this Open Graph checker does

It fetches one public URL on the server and reports the head metadata a crawler without a JavaScript engine receives: the title, the meta description, the canonical link, the robots rule, and the og:* and twitter:* tags the page actually spells. Missing tags are named in their own block rather than left as blank rows, because "there is no og:image" is the finding that changes what you do next.

The report also measures the title and description against the character budgets this site itself enforces, and builds a search-result preview from the page's own values.

How to use it

Enter a public https:// URL and press Check tags. You get the status code and any redirects that were followed, every tag that was found, every required tag that was not, the character count of the title and description against the budget, and the preview.

It does not run JavaScript, and that is the finding

The checker reads the raw server response. A single-page application ships an empty shell and writes its head from script, so it will look empty here. That is not a defect in the report: it is exactly what a crawler that does not execute script receives, and it is the most common reason a page's cards look wrong when someone shares the link.

When a page has no title, no description, no Open Graph tags and at least one external script, the report says possible_client_rendered is true and tells you why, instead of claiming the page has no title.

What a complete card needs

A page that unfurls well publishes og:title, og:description, og:type, og:url and og:image, plus twitter:card with its own title, description and image. The report names whichever of those is absent. Some parsers fall back from twitter:* to the matching og:* value, but this report only counts tags the page spells out, so the missing list is what the page itself is missing.

A real capture

This is the recorded output for https://208.67.222.222/, a host that answers 404 with a title and no other metadata — the shape this tool exists to name:

{
  "status_code": 404,
  "document": { "title": "404 Not Found", "description": null, "canonical": null, "robots": null },
  "missing": {
    "core": ["description", "canonical", "robots"],
    "open_graph": ["og:title", "og:description", "og:type", "og:url", "og:image"],
    "twitter": ["twitter:card", "twitter:title", "twitter:description", "twitter:image"]
  },
  "budgets": { "title": { "characters": 13, "budget": 60, "over_budget": false } }
}

Privacy and safety

The server fetches the URL you name, so this page does not claim to run in your browser. Private, loopback and reserved addresses are refused before a connection is opened, and every redirect hop is checked again, so a public URL cannot redirect onto a private one. Redirects are capped, the connection and the whole request each have a timeout, and at most 512 KB of the response is read. The response is parsed in memory and is never written to disk or logged.

Enter a public URL and this page fetches its raw server response and reports the head metadata a crawler reads: title, description, canonical, robots, the Open Graph tags, the Twitter card tags, which required tags are missing, and a search-result preview.

It does not execute JavaScript. A single-page application served as an empty shell therefore reports an empty head, which is a true finding about what a non-executing crawler receives rather than a defect in the check.

The request is made by the tool server, so the page is explicitly asking a third party for a page on your behalf. Private and reserved network addresses are refused at the first URL and at every redirect hop.

What the report contains

The core tags are title, meta description, canonical and robots, each present or named as missing. The Open Graph set requires title, description, type, url and image; the Twitter set requires card, title, description and image. Missing members are listed by name.

Title and description lengths are compared with character budgets supplied by this site's own SEO rules rather than a number invented inside the checker, so the report cannot drift from the limit the site enforces.

  • Title, description, canonical and robots
  • Open Graph and Twitter card tags, with the missing ones named
  • A SERP-style preview and a scope note about JavaScript

How the fetch is bounded

Redirects are followed by hand so each hop can be validated, and the chain is capped. Connect and total timeouts are both set, and the response read is capped, so a slow or huge page cannot hold the request open indefinitely.

A refusal, a transport failure or a non-HTML response produces a message rather than a fabricated report. Nothing from the response is written to disk or logged.

How to use the URL field

Enter the public URL and press Run. The tool server fetches the raw server response, never executing JavaScript, and reports the head metadata a crawler reads: title, description, canonical, robots, the Open Graph tags, the Twitter card tags, the required tags named when missing, and a search-result preview with title and description checked against the site's own budgets.

A single-page application served as an empty shell reports an empty head, which is a true finding about non-executing crawlers rather than a defect. Private and reserved network addresses are refused at the first URL and at every redirect hop; redirects are followed by hand under connect, total and size caps.

What to Expect

Best for

  • Checking which social-card tags a page actually serves
  • Finding out why a shared link shows no image or title
  • Confirming a canonical or robots tag in the raw response

Not ideal for

  • Checking a client-rendered page's tags, which require JavaScript
  • Anything behind a login or on a private network address
  • Guaranteeing how a specific social network will render the card

What this tool keeps

  • The values the raw response contains, with missing ones named
  • The final URL after the redirect chain
  • A scope note stating that no JavaScript was executed

What may need cleanup

  • An empty head that belongs to a client-rendered shell
  • A preview that differs from a live search result, since engines rewrite titles
  • A redirect to a URL you did not expect

Common errors

  • Reading an empty report as a tool failure rather than a true finding
  • Expecting the checker to execute the page's scripts
  • Testing a localhost or private address, which is refused

Example use cases

  • Debugging a link preview before publishing
  • Auditing a page's canonical and robots tags
  • Checking the title and description lengths against this site's budgets

Sample input

Enter the public URL of a product page and run the check.

Sample output

A report naming the present title and description, the og:image found, any missing Twitter tags by name, the final URL and a search-result preview.

Who this is for

  • SEO and content teams debugging a card
  • Developers checking a page's head
  • Anyone whose shared link looks wrong

Frequently asked questions

What does the Open Graph checker report?

The raw head metadata a crawler reads: title, description, canonical, robots, Open Graph and Twitter tags, missing required tags and a search-result preview.

Does it run JavaScript?

No. It reads the raw server response, so tags injected by a client-rendered page will be missing.

Does it guarantee how a social network renders the card?

No. It reports the values the response contains; a platform may still render them differently.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.