Social Media Preview Tool

The most common reason is a missing or invalid og:image. Social platforms usually need a public, absolute image URL such as https://example.com/image.jpg, not a relative path like /image.jpg. The image also needs to be reachable without login, firewall blocks, hotlink protection, or bot protection.

For best results, use an image around 1200×630px, make sure it returns HTTP 200, and include both og:image and twitter:image.

First clear your website cache and CDN cache. Then use the platform tools to force a fresh scrape or check what each crawler sees:

If the tools still show old metadata, check for duplicate Open Graph tags, stale server cache, CDN cache, or a plugin/theme outputting old values.

Facebook caches previews aggressively. Even after you fix the page metadata, Facebook may keep showing the old version until it recrawls the URL. Clear your website cache, CDN cache, then use Facebook Sharing Debugger to scrape the page again.

X usually needs twitter:card set to summary_large_image. It can also use twitter:title, twitter:description, and twitter:image. If Twitter-specific tags are missing, X may fall back to Open Graph tags, but the card may not look the way you expect.

LinkedIn relies heavily on Open Graph metadata. Check og:title, og:description, og:image, and og:url. If you recently changed them, LinkedIn may still have the old version cached. Clear your site/CDN cache and refresh the URL in LinkedIn Post Inspector.

Bluesky usually reads Open Graph tags. Make sure the page has og:title, og:description, and og:image. The image must be public and accessible to crawlers. If the page blocks bots, requires JavaScript, or serves different HTML to crawlers, the preview may be incomplete.

Slack and Discord commonly use Open Graph tags. Missing og:image, bot-blocking security rules, redirects, login walls, private pages, or slow server responses can prevent a preview. Make sure the URL and image are public and return a normal HTTP 200 response.

Check the featured image, SEO plugin social settings, cache plugins, CDN cache, hotlink protection, and whether your theme has wp_head(). Also check if another plugin is outputting duplicate Open Graph tags, because platforms may choose the first or last tag unpredictably.

After fixing it, clear WordPress cache, purge CDN cache, and refresh the URL in the platform debugger tools.

Each platform has its own crawler, cache, image rules, and fallback behavior. Facebook, LinkedIn, Bluesky, Slack, and Discord mostly depend on Open Graph. X also prefers Twitter Card tags. A page can look fine on one platform and broken on another if some tags are missing or cached differently.

Platforms may use og:title and og:description instead of your normal <title> and meta description. If Open Graph tags are missing, they may guess from the page content. If there are duplicate tags, caching, or SEO plugin conflicts, the wrong text can appear.

Yes. Too many redirects, HTTP-to-HTTPS problems, www/non-www loops, geo redirects, cookie consent redirects, or redirects to login pages can stop social crawlers from reading the final metadata. The shared URL should end at a public page that returns HTTP 200.

Yes. Social crawlers can be blocked by bot protection, WAF rules, country blocking, rate limits, hotlink protection, or WordPress security plugins. If a crawler cannot access the HTML or image, the preview may be missing or incomplete.

Not always, but it can be a warning sign. A noindex page may still generate a preview on some platforms, but if the page is private, blocked, password-protected, or intentionally hidden from crawlers, previews may fail.

No. It checks the HTML returned by the server. That is what most social crawlers prefer, too. If your metadata only appears after JavaScript runs, previews may fail. Put social metadata directly in the initial HTML response.