How to Refresh URL Unfurl Link Previews — Clear Cache Guide (2026)

You updated your page's title, description, or image — but when you share the link, the old URL unfurl still appears. This happens because every major platform caches link previews, sometimes for hours or days.

Updating your metadata on the page is only step one. You also need to force each platform to re-fetch it.

This guide covers what URL unfurl and platform caches actually are, how long each platform holds a cached URL unfurl, the exact refresh workflow for Facebook, X/Twitter, LinkedIn, Slack, Discord, WhatsApp, iMessage, Telegram, Microsoft Teams, and Instagram, a quick-reference table, and the best practices that keep your URL unfurls from going stale in the first place.

→ Verify your metadata on TryUnfurl first

What Is URL Unfurl and Why Previews Cache

URL unfurling is the process every social network and chat app runs when someone shares a link — it fetches your page, reads Open Graph and Twitter Card tags, and renders a preview card. Once built, that preview is cached against the URL so the platform doesn't re-fetch your page every time the link is shared.

Caching is why link previews are fast, but it's also why a broken preview keeps appearing even after you've fixed your tags. To get the fix in front of readers, you have to force the platform to re-run the URL unfurl.

Why Link Previews Get Stuck

When a platform first sees a URL, it fetches the page metadata and stores it in a cache. The next time someone shares that URL, the platform serves the cached version instead of fetching fresh data — it's faster and reduces server load.

The downside: if you update your og:title, og:description, or og:image, those changes won't appear until the cache expires or you manually force a refresh.

Cache lifetimes vary by platform — from a few hours (Slack) to several days (Facebook, LinkedIn).

Before You Refresh: Check URL Metadata

First, confirm your metadata is actually correct on the live page. Use TryUnfurl — it always fetches the live page with no internal cache, so if your update is showing there, the page is ready for re-scraping. Then use the platform-specific steps below to clear each platform's URL unfurl cache.

If TryUnfurl doesn't show your new tags, fix those first. Refreshing caches on platforms when the page still serves old tags just re-caches the old preview.

How to Refresh Link Previews by Platform

Facebook / Meta

Use the Facebook Sharing Debugger:

Go to developers.facebook.com/tools/debug
Paste your URL and click Debug
If old data is shown, click Scrape Again
Repeat until the correct metadata appears
Share the link again — Facebook will now use the fresh URL unfurl

Facebook often requires two scrapes: the first re-fetches your page, the second reads the freshly cached data.

Twitter / X

Use the Card Validator:

Go to cards-dev.twitter.com/validator
Paste your URL and click Preview Card
X re-fetches the metadata on each validation — effectively clearing the cache
Your next tweet with the URL should show the updated card

Use the Post Inspector:

Go to linkedin.com/post-inspector
Enter your URL and click Inspect
Click Regenerate preview to force a fresh fetch

LinkedIn's cache can be slow to clear — if the preview still looks wrong after regenerating, wait 5–10 minutes and try again. LinkedIn ignores Twitter Card tags; your Open Graph tags are what's being refreshed.

Slack

Slack has no public cache-clearing tool. Your options:

Delete the original message and re-share the link — Slack fetches metadata fresh each time a link is first shared in a channel.
Append a query string (e.g. ?v=2) — Slack treats the new URL as a brand-new resource.
In some workspaces, hovering over an unfurl preview shows a refresh icon — click it to force a re-fetch.
Wait — Slack's cache typically expires within a few hours.

Discord

Discord has no cache-clearing tool either. Options:

Add a query parameter to the URL when re-sharing: https://example.com/page?v=2 — Discord treats this as a new URL and fetches fresh metadata.
Wait — Discord embed caches typically expire within a few hours to a day.
Re-share the link in a new message after the cache has expired.
Check for angle-bracket suppression — <https://example.com> disables the embed.

WhatsApp caches per URL on its servers and per message on the recipient's device:

Delete the message and resend.
Append a query-string cache-buster (?v=2) when re-sharing to force WhatsApp to fetch fresh.
The recipient may need to update WhatsApp or clear their local cache if they still see the old preview.
Server cache typically expires within 24–72 hours.

iMessage / Apple

iMessage caches previews on the recipient's device. There's no server-side cache to clear. The recipient can:

Long-press the message and delete it, then ask you to resend.
Or wait — the cache usually expires naturally.
Re-send using a query-string cache-buster to force a new fetch.

Telegram has no public cache-clearing endpoint. Workarounds:

Append a query parameter (?v=2 or ?ref=tg) — Telegram treats it as a new URL.
Re-share in a new chat — the preview is fetched fresh when a URL is first shared in a new conversation.
Wait — cached failed fetches may persist for hours before Telegram retries.

Microsoft Teams

Teams doesn't expose a cache-clearing tool either. Workarounds:

Re-paste the URL in a new message or chat.
Append a query-string cache-buster if the URL is stuck.
If the preview still fails, confirm Teams' unfurl bot can reach your page (no authentication, no WAF block).

Instagram

Instagram pulls metadata when you paste a link in bio or swipe-up. There is no debugger tool — Instagram re-fetches on each paste. Update your Open Graph tags, then re-add the link in your profile/bio.

Quick Reference — How to Refresh URL Unfurl by Platform

Platform	Typical cache	How to refresh	Tool available?
Facebook	24h–several days	Sharing Debugger → Scrape Again	Yes
X / Twitter	Hours	Card Validator	Yes
LinkedIn	Hours–days	Post Inspector → Regenerate	Yes
Slack	Few hours	Delete & re-share / `?v=2`	No
Discord	Few hours–24h	Append `?v=2` query param	No
WhatsApp	24–72h	Delete & resend / `?v=2`	No
iMessage	Per-device	Delete & resend	No
Telegram	Varies	`?v=2` cache-buster / new chat	No
Microsoft Teams	Varies	Re-paste / `?v=2`	No
Instagram	Per-paste	Re-add link in bio	No

If the Preview Still Won't Update

If you've cleared the platform cache but the old preview persists:

Check your CDN. If you use Cloudflare, Fastly, CloudFront, Vercel, or Netlify, it may be serving a cached HTML response. Clear the CDN cache for the affected URL before re-running the platform debugger.
Check your redirects. If the URL redirects, make sure the final destination has the correct metadata.
Verify tags are server-rendered. JavaScript-injected Open Graph tags are invisible to every platform crawler. curl -sL https://example.com/page | grep og: should show every OG tag.
Check for duplicate OG tags. A theme + plugin combo sometimes injects two og:image tags. Inspect the rendered HTML.
Watch for signed-URL expiry. If og:image is a signed CDN URL, the cached copy breaks when the signature expires.
Verify with TryUnfurl. Paste the exact URL (including any redirects) into TryUnfurl to confirm the live page is actually serving the updated tags.

Best Practices for Link Preview Management

Ship tags server-rendered. Never inject Open Graph via client-side JavaScript.
Set a site-wide default og:image so no page launches naked.
Use permanent image URLs for og:image — avoid short-lived signed URLs.
Keep redirects short (1–2 hops max) so platform crawlers don't give up.
Test before every share with a multi-platform checker. See how to test URL unfurl.
Audit monthly with the bulk URL unfurl checker to catch silent regressions.
Automate in CI/CD with the TryUnfurl API so broken OG tags never ship.

Frequently Asked Questions

Why hasn't my link preview refreshed yet?

Either the platform's cache hasn't expired, the debugger tool hasn't been run yet, or your CDN is still serving old HTML. Check all three.

How long does it take for a URL unfurl to refresh?

Most platforms update immediately after their debugger is run (Facebook, X, LinkedIn). Slack and Discord can take a few hours without intervention. LinkedIn sometimes needs 5–10 minutes after Regenerate preview.

Can I refresh a URL unfurl without a platform tool?

Yes — appending a query string (?v=2 or similar) creates a new URL from the platform's perspective, forcing a fresh fetch. Works on Slack, Discord, WhatsApp, Telegram, and Teams.

Why does the preview look fine on some platforms and stale on others?

Each platform has its own cache. Facebook may refresh in seconds while LinkedIn still shows old data for hours. Run each platform's debugger separately.

Does refreshing a URL unfurl affect SEO?

No. Refreshing the platform cache is a social media action; it doesn't touch Google's index.

Check What Your Page Is Serving Now

→ Check your live metadata on TryUnfurl · → Bulk-check up to 100 URLs

Check How Your Links Unfurl for FREE!