You shared the link and the preview came out wrong: old headline, stretched image, or no image at all. This og checker fetches any URL and shows how the card renders on Facebook, Twitter / X, and LinkedIn, each in its own tab, next to a Raw tags view listing every og: and twitter: value the page actually serves. Because it reads the live HTML rather than a platform's cache, it tells you whether the problem is your markup or a stale scrape, which are two very different fixes. Use it as an open graph checker before a campaign goes out, or as evidence when someone insists the preview is broken and you suspect it isn't.
Enter the page address and click Inspect OG card. The tool fetches the live page and extracts every Open Graph and Twitter Card tag it finds in the head.
02
Flip through the platform tabs
Check the Facebook, Twitter / X, and LinkedIn tabs one by one. Each renders a card from your tags, and a warning appears when no og:image exists to fill it.
03
Verify values in the Raw tags tab
Open Raw tags to see each og: and twitter: property with its exact content, plus a copy button per row. This is where typos and truncated URLs become obvious.
Why Open Graph Inspector
See exactly how your URL renders on Twitter, Facebook, and LinkedIn.
Inspects og: + twitter: meta tags side by side.
Catches missing or oversized images before you post.
Common questions
Why does the og image checker show a different picture than Facebook does?
Because this tool reads your live HTML while Facebook serves whatever its scraper cached, sometimes days ago. If the og image checker here shows the right picture and Facebook shows the old one, your markup is fine and the cache is stale. Re-scrape the URL in Facebook's Sharing Debugger to force a refresh.
What does the Raw tags tab of the og tag tester list?
Two groups: every og: property and every twitter: property found in the head, each with its full content value and a copy button. Empty groups say no tags were found, which is itself the diagnosis. An og tag tester earns its keep in this tab, since previews can look plausible while a single property holds a typo.
Which values does the preview fall back to when og tags are missing?
The title comes from og:title, then twitter:title, then the plain title tag. Description follows the same chain, and the image tries og:image then twitter:image. That mirrors what most platforms do, and it's why a page with zero og markup still produces a card, just not the one you'd have chosen.
Can a social preview checker inspect pages behind a login?
No, and neither can the platforms. The fetch arrives as an anonymous request, exactly like Facebook's or LinkedIn's scraper. If your page redirects logged-out visitors, the social preview checker sees the login screen's tags, which is precisely the broken card your audience would get.
Does the open graph checker render exactly what LinkedIn will show?
It's a faithful approximation built from the same inputs LinkedIn reads, but LinkedIn applies its own typography, image processing, and caching on top. Treat matching titles, descriptions, and images here as necessary rather than sufficient, then spot-check one real share for high-stakes links.
Is the Twitter / X tab reading twitter: tags or og: tags?
It merges them the way X does: og values take priority in this preview, with twitter: values filling gaps. To see which source each value actually came from, switch to the Raw tags tab, where the two tag families are listed separately and unmerged.
How often should I run the og checker on important pages?
After every change to templates or head markup, and always before a paid or scheduled share. Thirty seconds in the og checker is cheaper than a campaign that goes out with a missing image, because platforms cache the first scrape and the bad card can outlive your fix.