Link Preview Not Showing on WhatsApp, Instagram, or X? How to Fix It (2026)
Why your link preview isn't showing on WhatsApp, Instagram DMs, X, or Google — the OG tags each platform actually reads, the image-size rules, caching gotchas, and a free checker that shows exactly what's missing.
You drop your link in a WhatsApp group and it lands as bare blue text. In Instagram DMs it's a naked URL. On X it's a link with no card. Every one of those is a conversion leak — previews get tapped; raw URLs get scrolled past. The cause is almost always the same five meta tags, and you can see exactly which one is missing by running your URL through our free link preview checker.
How link previews actually work
When you paste a URL, the platform's bot fetches the page once and reads the Open Graph tags in the HTML head — a standard Facebook created that everything else adopted. The ones that matter:
- og:title — the bold line of the preview. Without it, bots fall back to the <title> tag; without that, no card at all.
- og:description — the grey line. Falls back to the meta description.
- og:image — the picture, and the tag that's missing or broken in 90% of blank previews. Must be an absolute https URL (https://yoursite.com/og.jpg, not /og.jpg).
- og:url — the canonical address, so shares consolidate.
- twitter:card — X-specific: set it to
summary_large_imageor X renders the small thumbnail card even when your og:image is perfect.
Why WhatsApp is the strictest (and the most cached)
WhatsApp generates the preview on the sender's device and has the least patience of any platform:
- The og:image must be https and lightweight — keep it under ~600KB. Oversized images silently fail.
- The page gets roughly 3 seconds to respond. A slow server means no preview — and WhatsApp caches that empty result per exact URL, so it stays blank even after you fix the page.
- The cache-bust trick: append a throwaway query string —
yoursite.com/page?v=2— and WhatsApp treats it as a new URL and re-fetches. That's the fastest way to verify a fix actually landed.
The 1200 × 630 rule
One image size renders correctly everywhere: 1200 × 630 pixels (1.91:1). WhatsApp, X large cards, iMessage, Slack, LinkedIn, and Google Discover all crop it acceptably. Put the subject in the center 80% — X and iMessage shave the edges. Export JPG at ~90%; more sizes and compression details in the 2026 image size chart.
Refreshing a stale preview, per platform
- WhatsApp: new query string on the URL (see above). There is no public debugger.
- Facebook / Instagram DMs: Meta's Sharing Debugger → Scrape Again.
- X: the old card validator is gone; X re-fetches on share within a few minutes of a tag change. Post in a DM to yourself to test.
- LinkedIn: Post Inspector re-scrapes on demand.
- Everything at once: run the URL through the OG checker first — it shows the tags the bots will see and a per-platform preview, so you fix before you re-share, not after.
The checklist
- og:title, og:description, og:image, og:url present in the raw HTML (not injected by JavaScript — most preview bots don't run JS).
- og:image is an absolute https URL, 1200 × 630, under 600KB.
- twitter:card set to summary_large_image.
- Page responds in under 3 seconds from a cold hit.
- Re-share with a fresh query string to bust WhatsApp's cache.
Two minutes of tags for permanently better click-through on every link you'll ever share — including the one in your bio. (If that link is a Creator Lane page, the OG tags are already set correctly — every free bio page ships with a proper preview card out of the box.)