Why Link Previews Disappear
A missing link preview usually means the social app could not read clean metadata from your page. The page may load perfectly in a browser, but crawlers still need accessible Open Graph tags, a valid image URL, and a response they can fetch without JavaScript-only rendering.
This is why the same URL can show a full card in one app, a tiny thumbnail in another app, and plain text somewhere else.
Quick Fix Checklist
- Add
og:title,og:description,og:image,og:url, andog:type - Use an absolute HTTPS URL for
og:image - Make sure the image returns a 200 response without login, bot blocking, or hotlink protection
- Use a JPG, PNG, or WebP image instead of SVG as the primary preview image
- Keep the image large enough for rich cards and compressed enough for strict apps
- Avoid redirect chains for the page URL and the image URL
- Check that
robots.txtdoes not block social crawlers - Refresh or cache-bust the URL after fixing metadata
The Tags Most Apps Expect
<meta property="og:title" content="Page title for the preview" />
<meta property="og:description" content="Short preview copy for social cards" />
<meta property="og:image" content="https://example.com/og-image.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />Use the same canonical page URL in your Open Graph tags, canonical tag, sitemap, and internal links. Mixed hosts like example.com and www.example.com can split signals and make debuggers show stale or unexpected results.
Platform-Specific Problems
WhatsApp is often strict about image access, size, and format. If your WhatsApp preview is missing, start by checking og:image, HTTPS access, image file size, and stale cache.
Twitter/X
Twitter/X can use Twitter Card tags and Open Graph fallback data. If the large image card is missing, confirm twitter:card, twitter:image, and the image URL.
LinkedIn commonly shows stale titles or images after metadata changes. Confirm the canonical URL and Open Graph tags, then retest after refreshing cached metadata.
Slack and Discord
Slack and Discord previews usually fail when the page requires JavaScript to expose metadata, blocks crawler access, or has an image URL that cannot be fetched directly.
How to Test the Fix
Use LinkPeek to run a multi-platform preview scan. It renders WhatsApp, Twitter/X, LinkedIn, Slack, Discord, and Instagram-style cards, then gives you an audit of missing tags and copy-paste fixes.
After updating your page:
- Retest the canonical URL
- Retest a cache-busted URL such as
/page?v=2 - Confirm the image URL opens directly in a private browser window
- Share the final URL only after the preview is correct
FAQ: Link Preview Not Showing
Q: Why does my link preview show no image?
A: The most common reasons are a missing og:image tag, a relative image URL, blocked crawler access, unsupported image format, image file size problems, or stale platform cache.
Q: Why does my preview show the old image?
A: Social apps cache preview metadata. Update the image URL or add a versioned query string, then use platform debuggers or a fresh share to retest.
Q: Do Open Graph tags help SEO?
A: Open Graph tags are mainly for social previews, not direct Google ranking. They can still improve click-through and sharing quality, which helps distribution.
Q: Can I test a preview before deployment?
A: Yes. LinkPeek supports localhost preview workflows so you can fix metadata before a public release.