Twitter Card Preview Not Updating: Separate Deployment, Crawler, and Cache Problems
Troubleshoot an X/Twitter Card preview that will not update by comparing deployed raw HTML with image delivery, redirect resolution, canonical signals, and cache behaviour.
Deployments can update the browser before the crawler path
A local build, a browser session, or an edge cache can all make a page look updated before the public crawler response is updated. Test the final production URL rather than a preview deployment and inspect the captured raw head HTML. The new title, description, image URL, canonical, and og:url must be visible there.
Compare the values that control a preview
The validator labels every detected Twitter and Open Graph value with its source. Use that evidence to find a stale fallback: for example, a missing twitter:title can leave X using an old og:title, while a new twitter:image may still be shadowed by an inaccessible asset. Record the final URL and redirect chain too; a redirect to another path can make you inspect the wrong document.
Make update events easy to observe
Use stable canonical and og:url values, but version social image files when their visual content changes. Do not add cache-busting query strings randomly to a URL that has not been deployed correctly. First make the intended HTML and asset response verifiably live; then allow the platform to recrawl the same final URL.
If the validator still sees the previous metadata, the problem is in deployment, routing, or server-side rendering—not an X cache refresh.