PreviewChecks

PreviewChecks now has a clearer FAQ section for one of the most common social preview problems: why a platform still shows the old image after the page was fixed. The update adds practical guidance for: • checking that your origin server and CDN serve the new HTML and image to crawlers • purging page and image cache before blaming the social platform • using Facebook Sharing Debugger, LinkedIn Post Inspector, and Telegram WebpageBot where refresh tools exist • changing the og:image URL with a versioned filename or query parameter when an image proxy is stuck • making sure the CDN cache key actually includes that query parameter, otherwise the cache-busting URL will not help I also added a compact cache timing table for Facebook, X, LinkedIn, Pinterest, Slack, Discord, Telegram, and WhatsApp. The main takeaway: social preview caches are layered. A page can be fixed while the platform, image proxy, or your own CDN still serves the old asset.

Preview checks now return clearer problems and recommendations faster. The report now flags slow preview HTML and image responses against a 3 second target, so it is easier to see when a page or preview image is likely to feel unreliable for crawlers. We also fixed how multiple og:image entries are read. PreviewChecks now preserves the declared image order and applies Open Graph image prioritization more closely to the opengraph.org specification, including related image properties such as secure URL, width, height, type and alt text. This makes recommendations more accurate when a page has several preview images, redirects or platform-specific image candidates.