Your link, unfurled before you share it.
Paste a URL and get the preview card WhatsApp, Instagram DMs, X, and Google will actually render — fetched server-side with no JavaScript, the same way their bots do it — plus a prioritized fix-list for every missing or broken tag.
The five tags that decide every preview.
Every platform builds its card from the same handful of Open Graph tags in your page's head. In order of how badly their absence hurts: og:image (no image, no card on most chat apps), og:title, og:description, twitter:card (X won't render the large card without it, even with a perfect og:image), and og:url. The full walkthrough — per-platform quirks, cache busting, the 1200 × 630 rule — is in the link preview fix guide.
OG checker FAQ.
- What does this OG checker actually test?
- It fetches your page exactly the way preview bots do — server-side, no JavaScript, a 5-second budget, first 512KB of HTML — and reads the Open Graph and Twitter Card tags out of the raw markup. Then it renders the card each surface would build and lists what's missing, in order of how badly it hurts.
- Why does my preview work on X but not WhatsApp?
- WhatsApp is stricter on two axes: the og:image must be an absolute https URL under roughly 600KB, and the page must respond in about 3 seconds. X tolerates heavier images and slower pages. If X shows a card and WhatsApp shows bare text, start with image weight and response time.
- My tags are correct but the preview is still blank. Why?
- Caching. Platforms cache the first fetch per exact URL — including a failed one. Share the link with a throwaway query string (yoursite.com/page?v=2) and WhatsApp treats it as a new URL. For Facebook and Instagram, use Meta's Sharing Debugger and hit Scrape Again.
- Why doesn't the checker see tags my browser shows in dev tools?
- Because your browser ran JavaScript and the bots don't. If og: tags are injected client-side (common with single-page apps), preview bots — and this checker — see the pre-JS HTML with no tags. The fix is server-side rendering or static generation of the meta tags.
- What size should the og:image be?
- 1200 × 630 pixels (1.91:1), https, under 600KB. That one file renders correctly on WhatsApp, X large cards, iMessage, Slack, LinkedIn, and Google Discover. Keep the subject in the center 80% — some surfaces shave the edges.
- Can I check localhost or a staging URL behind a VPN?
- No — the checker only fetches public https URLs, same as the real bots. Private addresses, IP literals, and internal hostnames are refused. If a preview bot can't reach the page, its preview will be blank anyway, so test on a public URL.
Go deeper.
Per-platform rules, WhatsApp's cache-bust trick, and the exact checklist behind this tool's fix-list.
Missing a 1200 × 630 og:image? Make one from any image, in-browser.
Preview fixed — now count the clicks it earns.
Tag the link so you know which share drove the traffic.
Run this on your Instagram — free.
Connect your account in 2 minutes and Creator Lane will fire this DM automatically when someone comments your keyword. Unlimited DMs, no watermark, no card — the free ManyChat alternative built for creators.
Official Meta Graph API · Tech Provider · 2-min setup · No credit card