You've added OG tags to your page. But are they actually working? A page can have perfect og:image markup and still render a broken preview — because the platform's scraper hit a cache, a redirect, or a CDN rule that blocked its user-agent. Here's how to check, debug, and fix your Open Graph meta tags across every major platform, in the order you should actually do it.
1. Our Free OG Checker
The fastest way to check: paste your URL into our free OG image checker. It shows your og:image preview plus all meta tags in one place — title, description, image, dimensions, type, and URL. If something's missing, you see it immediately instead of hunting through page source.
2. Platform-Specific Debuggers
Each platform has its own scraper with its own cache. That's why a link can look perfect in one app and broken in another. These are the official debuggers — use them in this order:
Facebook Sharing Debugger
developers.facebook.com/tools/debug/
Paste your URL and click "Debug". Facebook re-scrapes your page and shows exactly what og tags it detected. The killer feature: after you fix tags, click "Scrape Again" to force-refresh the cache — without this, Facebook keeps showing the old preview for days. The debugger also surfaces warnings like missing og:image:width or an image URL that's blocked from crawlers.
Twitter Card Validator
cards-dev.twitter.com/validator
Note: X retired the interactive validator for some accounts; you may need to post a link in a tweet and inspect the card, or use the card preview inside X's composer. If you use twitter:image separately from og:image, the validator is where you confirm the square variant renders.
LinkedIn Post Inspector
LinkedIn is the strictest about dimensions — it wants 1200×627 and will crop aggressively. The inspector shows you the rendered card and any warnings about image size or file type.
Slack and Discord (No Debugger — Test by Pasting)
Neither Slack nor Discord offers a public debugger. The reliable test is to paste the link into a channel or DM and watch the unfurl. Discord has a hard 8MB image cap and skips images that fetch slowly; Slack suppresses duplicate previews within an hour — so if your test "fails," paste a different URL or wait, then re-test.
3. Manual Check
Right-click your page → View Page Source. Look for these tags in the <head>:
<meta property="og:title" content="...">
<meta property="og:description" content="...">
<meta property="og:image" content="...">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">Then confirm the image URL in og:image actually resolves: open it in a browser tab and check that (a) it's not a 404, (b) your CDN doesn't block crawler user-agents like facebookexternalhit or Discordbot, and (c) the file is under the platform's size cap. Most "working tags, broken preview" cases trace back to one of these three.
Common Issues and Fixes
- Image not showing: Facebook cached an old version. Run it through the Sharing Debugger and click "Scrape Again" to force refresh.
- Wrong image: You might have multiple og:image tags. Platforms use the first one — delete the duplicates and keep the one you want.
- Missing dimensions: Without og:image:width/height, Facebook delays image rendering while it re-scans the file.
- Preview works on desktop but not mobile: Some chat apps request a square thumbnail; make sure your image has a usable center crop.
- Everything checks out but the preview is stale: Platform caches. Re-scrape on Facebook, repost the link elsewhere, and give it a few minutes.
The Checklist Before Every Share
Run this once per page, not per share: (1) paste the URL in our checker and confirm all six core tags exist; (2) run Facebook Sharing Debugger and click Scrape Again; (3) paste into Discord or Slack to confirm the unfurl; (4) verify the image file loads directly in a browser. Four steps, under two minutes, and your links will never look broken again.