Refresh a link preview cache
Fixing the tags does not update a card a platform already stored. A few of them publish a tool that fetches the URL again. The rest make you wait, or share a URL they have not seen. Check the tags with the tool above, then refresh the platform that is still showing the old card.
What actually refreshes
- Facebook. The official tool is the Sharing Debugger at developers.facebook.com/tools/debug. You need to be logged in. Paste the URL and scrape again. That scrape updates the preview Facebook has stored for that URL. Facebook also caches each image by the image URL, so a replaced file at the same address can stay stale — point og:image at a new URL when the picture itself changed. Posts already shared do not rewrite themselves. This checker shows the tags your server sends. It does not clear Facebook's cache.
- LinkedIn. LinkedIn's tool is Post Inspector at linkedin.com/post-inspector. You need to be logged in. Enter the URL and inspect it. LinkedIn's help says that refresh applies to new posts, messages, and articles that include the URL. Anything already published keeps the preview it had.
- X. X does not publish a scrape-again tool. The old Card Validator no longer shows a preview, and X does not say how long a card stays cached. A query string such as ?v=2 is a different URL, so it is fetched on its own. The original URL updates when X fetches it again.
- Slack. Slack does not publish a debugger for a classic unfurl. It caches the crawl for around 30 minutes, for the same URL, across the service. Share a URL Slack has not cached — add a query string such as ?v=2 — or wait for that cache to expire. A message already posted keeps the unfurl it got.
- Discord. Discord's link-preview docs say a preview is cached for about 30 minutes, and resharing the same URL in that window shows the old card. The way they document for seeing a change immediately is a new query string, such as ?v=2. The Embed Debugger at discord.com/developers/embeds shows the tags Discord read and the layout it chose. An embed already posted in a message stays as it was.
- Telegram. Send the page URL to @WebpageBot. The bot fetches the page again and updates the cached preview for that URL. Telegram does not publish how long a preview lives. A message already sent can keep its old card, so share the link again after the bot confirms the update. A query string is a different URL, not a refresh of the original one.
- iMessage. Apple does not publish a cache-busting tool for Messages. A rich link is built from the Open Graph tags in the HTML, and a preview already shown on a device can stick. There is no official way to push a new card into a conversation that already has one. A new URL is a new fetch. Confirm the tags with the checker above before you send it.
Tags covered: og:title · og:description · og:image · og:image:url · twitter:card
More checkers
Twitter Card ValidatorOpen Graph CheckerLinkedIn Link Preview CheckerDiscord Embed PreviewWhatsApp Link Preview CheckerSlack Link Preview CheckeriMessage Link Preview CheckerFacebook Link Preview CheckerOpen Graph Image SizeTelegram Link Preview CheckerReddit Link Preview CheckerNext.js Open GraphAll platforms
What each platform reads
- X / Twittertwitter:card, twitter:* → og:* fallback1200×630 (min 300×157), < 5 MB
- Facebookog:title, og:description, og:image1200×630, 1.91:1
- LinkedInog:title, og:image (og: only)1200×627, 1.91:1
- Discordog:site_name, og:*, theme-color, twitter:cardLarge image needs summary_large_image
- Slackog:site_name, og:title, og:description, og:image1200×630
- WhatsAppog:title, og:description, og:imageKeep < 300 KB
Guidance based on each platform's public documentation and observed behavior. Platforms change their rules without notice.
FAQ
+Is Peekly free?
Yes. Checking a single URL is free forever — no signup and no limit on one-off checks. Batch watching and monitoring may arrive later as a paid Pro plan; the free single-URL tool stays.
+Why does my link show no image when I share it?
Usually one of four things: there's no og:image tag, the image URL is relative instead of absolute, the image is behind a login, firewall or bot block, or the file is too big or in an unsupported format like SVG. Peekly checks all four and tells you which one it is.
+What size should my og:image be?
1200×630 pixels (a 1.91:1 ratio) as a PNG or JPG under about 300 KB. That size works for large cards on X, Facebook, LinkedIn, Discord, Slack and WhatsApp.
+Do I need twitter: tags if I already have Open Graph tags?
X reads og:title, og:description and og:image as fallbacks, but you still need twitter:card set to summary_large_image if you want the big image card. Without it, X shows a small thumbnail.
+I fixed my tags but the old preview still shows. Why?
Platforms cache link previews, sometimes for days. Facebook and LinkedIn let you force a refresh with their own debugging tools. On X, Slack and Discord the cache usually expires on its own, or you can add a query string such as ?v=2 to the URL.
+Do you store the pages I check?
No. We fetch the page once to read its <head>, show you the result, and don't save the page or the result. We only fetch public http(s) URLs, and private or internal addresses are blocked.
+Are the previews pixel-perfect?
They're close approximations of each platform's current card layout, built from the same tags the platforms read. Platforms change their designs from time to time, so treat them as a very good guide rather than a screenshot.
$9
One time
A written fix for the batch.
Up to 25 URLs. We check og:image, Twitter cards, size, redirects, and cache, then send copy-paste meta tags within 48 hours. The free single-URL check stays free.