Cache duration

Twitter caches card data for roughly 7 days after the first crawl. During that window, updated meta tags won’t show up in existing tweets, and new tweets sharing the same URL may also pull from the cache.

Forcing a refresh

The Twitter Card Validator lets you preview your card and force a re-crawl. Enter your URL and Twitter fetches fresh data regardless of the cache.

Since the X rebrand, the Card Validator has been intermittently unavailable. If it’s down, you may need to wait for the cache to expire on its own.

Cache busting with query parameters

If the Card Validator is unavailable and you need a fresh preview now, append a query parameter to make Twitter treat the URL as new:

https://example.com/page?v=2

Twitter caches by exact URL, so this works for new shares. The old URL still serves stale data.

Redirects and caching

Twitter caches card data against the final destination URL, not the redirect source. Changing where a 301/302 points effectively busts the cache for new crawls.

Common cache problems

• Updated tags, old preview: wait 7 days or use the Card Validator
• Different previews on different tweets: some were cached before your update, others after
• Preview vanished: your server likely returned an error during a re-crawl, and Twitter cached the error state