Free, no account
Open Graph Checker
See the link preview a page will get before you share it: its og:image, title and description, its X card tags, and which tags are missing — read from the page the way a link-preview bot reads it.
Any public page — a home page, a blog post or a launch page. Each page has its own tags, so the path counts.
How the checker reads a page
When a link is pasted into a chat or a post, the app sends a bot to fetch the page and reads the meta tags in its <head>. The checker does the same: it requests the page, follows up to five redirects, and reads the og: and twitter: tags from the HTML the server sends, without running any JavaScript.
It then draws a large link card from those tags, falling back to the page’s <title> and meta description where most apps do, and lists every tag that is missing or will not work: an og:image that is not a full URL, a missing twitter:card, a page that answers bots with a challenge.
The checker identifies itself as the same metadata bot that reads every site submitted to the ranking, so a firewall that challenges bots usually challenges it too. How to let the crawler through covers Cloudflare. The DR checker shows the Ahrefs Domain Rating every site on the ranking is ordered by.
Open Graph questions
What are Open Graph tags?
Meta tags in a page's <head>, such as <meta property="og:title" content="…">, that tell apps how to draw a link to the page: its title, a short description, an image and the address to credit. Facebook introduced the protocol, and LinkedIn, Slack, Discord, iMessage, WhatsApp and most other apps read it. X reads its own twitter: tags first and falls back to Open Graph.
Which Open Graph tags does a page need?
The protocol lists four as required: og:title, og:type, og:image and og:url. In practice og:description matters as much, and for X a twitter:card tag picks the card type — summary_large_image for a wide image. og:image:alt describes the image, and og:image:width and og:image:height let an app lay it out before downloading it.
Why is my og:image not showing?
The usual causes are an og:image that is a relative path instead of a full https:// address, an image that needs a login or blocks bots, a page that answers link-preview bots with a challenge instead of the HTML, or an app that is still showing a copy it saved before the tag was fixed. The checker reports the first and third; the preview below the result loads the image in your browser, so a broken image shows there too.
I fixed my tags. Why does the old preview still show?
Apps keep their own copy of a preview for a while after they first read a page. This checker reads the page fresh every time, so it shows what the tags say now. To refresh an app's copy, use its own tool where it has one, such as Facebook's Sharing Debugger or LinkedIn's Post Inspector, or share the URL with a harmless query string added.
Is the preview exactly what Facebook, X or LinkedIn will show?
No. It is drawn from the same tags, with the same fallbacks to the page's <title> and meta description most apps use, but every app crops images and trims text in its own way, and some draw a small card instead of a large one. Treat it as a check of the content, not a pixel-perfect copy of any one app.
What does the checker fetch?
Only the page you enter, the way a link-preview bot would: one request per redirect, to public addresses only, reading the HTML up to 2 MB. It does not run the page's JavaScript, so tags added by scripts after load are not seen — most link-preview bots do not see them either. The preview image loads from the site's server in your own browser. Nothing about the check is stored.