SEO Tools

Open Graph Checker

Open Graph checker that fetches any URL and shows its og: and twitter: tags, Facebook, X and Slack previews, and warnings for missing tags.

Open Graph Checker

This Open Graph checker fetches a page from our server and reads the tags that decide how a link looks when it is shared on Facebook, LinkedIn, X and Slack: the og: and twitter: meta tags, plus the page title, meta description and canonical link. The results show a preview card for each platform, the og:image on its own, a table of every tag found with a Copy button for each value, and a list of warnings.

Facebook says that when Open Graph tags are missing, its crawler makes a best guess at the title, description and preview image. Setting og:title, og:description, og:image and og:url yourself decides what people see in the card. The guide to Open Graph tags explains what each one does.

How to use the Open Graph checker

  1. Paste the full address of the page into the box. If you leave out http:// or https://, the tool adds https:// for you.
  2. Press Check or Enter. The server fetches the page with a 10-second timeout, follows up to 5 redirects and reads the first 1 MB of HTML.
  3. Read the og:title, og:description, og:image and og:type values in the Detected Meta Tags table, and switch between the Facebook / LinkedIn, Twitter / X and Slack tabs to compare the cards.
  4. Look for tags that are missing, too long or pointing at the wrong image.
  5. Update the tags in your CMS or HTML, then check the page again to confirm the change is live. Each IP address can run 10 checks a minute.

OG tags check: what the warnings mean

CheckShown as
og:title, og:description, og:image or og:url missingError
og:type or twitter:card missingWarning
og:title over 60 characters, og:description over 160, twitter:title over 70Warning
No title tag or no meta description on the pageWarning
og:site_name or canonical link missingInfo

Each of the four core og: tags that is present gets a green tick, so a clean page shows four ticks and no errors.

Where each preview gets its text

The Facebook / LinkedIn and Slack cards use og:title, then fall back to the page title, and og:description, then the meta description. The X card looks for twitter:title, twitter:description and twitter:image first and uses the og: values when they are absent. The domain line comes from og:url, or from the address you checked.

Using it as an OG image checker

The OG Image Preview section shows og:image, or twitter:image when there is no og:image, with its full URL. A relative path such as /img/card.jpg is turned into a full address on the page's domain. The checker does not download the image to measure it: it prints the size only when the page sets og:image:width and og:image:height. If the image fails to load in your browser, it drops out of the cards, which usually means the URL is wrong or the image host refuses the request.

Facebook recommends at least 1200 x 630 pixels. If your image is a different size, the image resizer can crop or scale it, and the article on Open Graph image size lists the sizes each platform uses.

Example: a page with half its tags

Say https://example.com/workshop has only these tags in its head:

<title>Spring Pottery Workshop | Clayhouse</title>
<meta name="description" content="A two-hour wheel class for beginners.">
<meta property="og:title" content="Spring Pottery Workshop">
<meta property="og:image" content="/img/workshop.jpg">

The Open Graph checker reports og:title and og:image as present and shows the image URL as https://example.com/img/workshop.jpg. It flags og:description and og:url as errors, warns about the missing og:type and twitter:card, and adds info notes for og:site_name and the canonical link. The Facebook card still shows a description, because it falls back to the meta description. The fix is four more tags; the meta tag generator writes them from a form.

Limits of this Open Graph tester

  • It reads the HTML exactly as the server sends it, so tags that JavaScript adds after the page loads are not detected.
  • It cannot reach localhost or private network addresses, which the server refuses for security. To test a staging site, it needs a public URL.
  • If a tag appears twice, the table shows the last copy only.
  • It shows how the tags will be read; each platform still applies its own cache and layout.

The checker sits with the other SEO tools on this site, most of which run in your browser.

Frequently Asked Questions

What are the most important Open Graph tags to set?
The Open Graph protocol lists four properties every page needs: og:title, og:type, og:image and og:url. Facebook's sharing guide puts og:description in its basic set as well. This Open Graph checker treats og:title, og:description, og:image and og:url as the core four and marks a missing one as an error, while a missing og:type gets a warning.
What image size is recommended for Open Graph images?
Facebook recommends images of at least 1200 x 630 pixels for link previews and won't use one smaller than 200 x 200. LinkedIn's help page gives 1200 x 627 as its minimum, with a 1.91:1 ratio. A 1200 x 630 image meets both. If the page also sets og:image:width and og:image:height, the checker prints the dimensions under the image preview.
Why is my social media preview not updating after I changed the tags?
Platforms keep a cached copy of the preview. Facebook's Sharing Debugger fetches the page again and updates the card, and LinkedIn's Post Inspector does the same for LinkedIn. Facebook caches images by their URL, so a replacement image needs a new file name or URL before it shows up.
Are Open Graph tags the same as Twitter Cards?
They are separate sets of tags. X has its own twitter: tags, such as twitter:card, twitter:title and twitter:image. The X preview in this Open Graph checker uses those where they exist and falls back to the og: title, description and image when they don't. Open Graph has no property for the card type, which is why the checker warns when twitter:card is missing.
Why does the OG checker say a tag is missing when my page has it?
The usual causes are a tag added by JavaScript after the page loads, a tag with an empty content value, or attributes written without quotes, which the parser skips. Some sites also send different HTML to unknown visitors. View the page source in your browser and compare it with the Detected Meta Tags table.