Open Graph & Social Preview Checker — See How Your Links Look on Every Platform
Enter any URL to see exactly how it will appear when shared on Facebook, X, LinkedIn, Slack, Discord, WhatsApp, and iMessage — and get a checklist of missing or broken OG tags with one-line fixes.
Enter any URL above to check its Open Graph tags and social previews.
Works with any public URL — blog posts, product pages, landing pages.
What Are Open Graph Tags?
Open Graph is a protocol introduced by Facebook in 2010 that lets any web page control how it appears when its
URL is shared on social media, messaging apps, or AI tools. You add a handful of
<meta property="og:"> tags inside
your page's <head>, and those tags
tell every platform — Facebook, X, LinkedIn, Slack, Discord, WhatsApp, iMessage, and others — exactly which
title, description, and image to show in the link preview.
Without OG tags, platforms guess. They grab the page <title>,
attempt to extract a description, and pick a random image from the page or show nothing. The result is inconsistent,
often wrong, and frequently unappealing. With properly set OG tags, every share of that URL looks exactly as
intended across every platform.
The four essential OG tags
og:title— the headline shown in the previewog:description— the summary text below the titleog:image— the preview image (most impactful tag)og:url— the canonical URL for this page
Twitter Card tags
X/Twitter reads OG tags as fallbacks but requires at least one Twitter-specific tag to display a rich preview:
twitter:card.
Setting it to summary_large_image tells X to
show a large image card. Without it, X falls back to a compact thumbnail even when your og:image is perfect.
Note: X deprecated their official Card Validator in 2023 — this tool fills that gap.
Open Graph Image Dimensions Guide
The og:image dimension question is one of the most common OG issues, and the answer is platform-specific. The good news: there is one safe universal size.
| Platform | Ideal size | Min / limit | Notes |
|---|---|---|---|
| All platforms (safe) | 1200×630px | 1.91:1 ratio | Universal safe size — use this as your default og:image |
| 1200×630px | Min 200×200px | Images under 200×200 are dropped entirely | |
| X / Twitter | 1200×628px | Min ~280px wide | Requires twitter:card set to summary_large_image for large display |
| 1200×627px | 1.91:1 ideal | Crops to 1.91:1 from top-centre | |
| Slack / Discord | 1200×630px | Fits to ~400×209 | Scale down proportionally from your 1200×630 image |
| WhatsApp / iMessage | Any (square crops) | Max 1MB file size | Large files may not be fetched — compress below 800KB |
Format: JPEG or PNG are universally supported. Avoid WebP and AVIF for og:image — some older platform crawlers do not support next-gen formats.
Platform-by-Platform Reference
Reads og:title, og:description, og:image, og:url, og:type, og:site_name. Falls back to <title> if og:title is missing. Minimum image 200×200px. Facebook caches aggressively — use the Sharing Debugger to force a re-scrape.
𝕏 X / Twitter
Falls back to OG tags, but requires twitter:card explicitly set. Without it, only a small summary card shows even if og:image is perfect. X's own Card Validator was deprecated in 2023 — use this tool instead.
Reads OG tags with the same priority as Facebook. Post Inspector forces a re-scrape but is largely unknown — another reason to verify here before sharing.
💬 Slack
Shows a compact link unfurl: image on the left, title and domain on the right. Reads og:title, og:description, og:image. Slack's crawler (Slackbot-LinkExpanding) must not be blocked in robots.txt for unfurls to work.
🎮 Discord
Very similar embed format to Slack. Reads OG tags. Discord caches aggressively — changing OG tags may not update embeds until the cache expires. No manual re-scrape tool available.
📱 WhatsApp & iMessage
Both show a compact preview with a small thumbnail, title, and domain. Image file size is the main issue here — images over 1MB are often not fetched at all. Title is truncated aggressively.
Related Tools
Robots.txt Validator
Check if social crawlers (Slackbot, Twitterbot) are blocked in your robots.txt.
Server Response Checker
Verify your og:image URL returns 200 OK and check response headers.
Title, Description & H1 Checker
Check how your title and meta description look in Google Search alongside your OG tags.
Frequently Asked Questions
Why is my OG image not updating after I changed it? ▾
All social platforms cache Open Graph data. Facebook, LinkedIn, and X each have different cache durations — anywhere from hours to over a week. To force an update: use the Facebook Sharing Debugger and click "Scrape Again", LinkedIn's Post Inspector, or — for X — change the og:image URL by adding a query string like ?v=2. Discord's cache is particularly stubborn and may require waiting until it expires naturally.
My OG tags look correct in this tool but still don't show on X/Twitter. Why? ▾
The most common cause is a missing twitter:card tag. Even with perfect OG tags, X requires this to be explicitly set to display a rich preview. The second most common cause is that the og:image URL is blocking the Twitterbot user agent in robots.txt or via CDN rules.
Does this tool work for single-page apps (SPAs)? ▾
Only if your SPA uses server-side rendering (SSR) or static site generation (SSG) that injects meta tags into the HTML response. If your OG tags are added by JavaScript after the page loads, this tool will not see them — and neither will most social platform crawlers. Facebook, LinkedIn, and Slack do not execute JavaScript when fetching link previews. This is one of the most common reasons OG tags work in a browser but fail on social platforms.
Do OG tags affect Google SEO rankings? ▾
Not directly. Open Graph tags are not a Google ranking factor. However, og:title and og:description can influence how Google displays your page in certain rich results and AI Overview citations. More practically: pages shared on social media with compelling, correct OG previews generate more clicks and engagement, which can drive traffic and indirectly support SEO performance.