WikiPlus

Why Is My Link Preview Not Showing Correctly? Causes and Fixes

A link preview not showing correctly on social media is one of the most frustrating content marketing problems because the cause can be any of a dozen different issues. WikiPlus OG Preview tool at wikiplus.co is the fastest way to diagnose exactly what is wrong — it shows you what tags the platform reads and how they render as a card. This article maps every common cause of a broken or incorrect link preview to its specific solution.

Cause 1: Missing or Incorrect OG Tags

The most straightforward cause of a broken preview is that the og:image, og:title, or og:description tags are missing from the page head. If og:image is absent, every platform falls back to its own image selection logic, which usually produces an irrelevant result. If og:title is missing, the platform uses the HTML title element, which may include your brand name in a format unsuited for social cards. Run WikiPlus OG Preview on your URL and check which tags appear in the results. If any required tag is missing, use WikiPlus Meta Tag Generator to generate the complete tag set and add it to your page head.

Cause 2: Stale Platform Cache

After fixing your OG tags and confirming they are correct in WikiPlus OG Preview, the social platform may still show the old broken preview because it cached the page data before you made the fix. Facebook caches up to 30 days, LinkedIn up to 7 days, X up to 7 days, Slack a few hours. To force an immediate refresh: Facebook — use the Sharing Debugger and click Scrape Again. LinkedIn — use the Post Inspector. X — use the Card Validator. After clearing the cache, newly shared instances of the URL will show the updated preview; existing posts will generally continue showing the old cached version.

Cause 3: Image Accessibility and Format Issues

The platform scraper fetches your og:image URL in the background. If the image URL requires authentication, is behind a CDN that blocks non-browser user agents, or points to a locally hosted URL, the scraper will fail and the image will not appear. Check: is the og:image URL an absolute HTTPS URL? Does it resolve directly to an image file rather than a redirect or HTML page? Is the image accessible without cookies or authentication? Can you open the URL in a private browser window and see the image? Image files larger than 8 MB may also be rejected by some platform scrapers — compress to under 300 KB.

Cause 4: Dynamic Rendering and JavaScript-Only Content

Some Single Page Applications render their content including meta tags via JavaScript on the client side. Social platform scrapers typically do not execute JavaScript — they read only the initial HTML response. If your meta tags are injected by JavaScript after page load, the scraper receives an empty head section. Solutions: implement Server-Side Rendering or Static Site Generation so OG tags appear in the initial HTML. For Next.js, use the metadata export in App Router. Alternatively, use a pre-rendering service that serves a cached, fully-rendered HTML version to scrapers while serving the JS app to browsers.

Frequently Asked Questions

Why does my link show no image on LinkedIn?
LinkedIn will not show an image if: og:image is missing from the page head; the og:image URL is not absolute (must start with https://); the image is smaller than 200x200 pixels; the image URL is inaccessible to LinkedIn scraper; or LinkedIn is displaying a cached version from before you added the image. Fix: confirm the og:image tag is present and correct using WikiPlus OG Preview, then clear the LinkedIn cache using the Post Inspector.
Why does my link preview look different on different platforms?
Each platform has different card dimensions, title length limits, and description character limits. Facebook uses a 1.91:1 image ratio; WhatsApp crops to a square; LinkedIn shows shorter descriptions than Facebook. The underlying OG tags are the same — the platforms render them differently. WikiPlus OG Preview shows platform-specific rendering side by side so you can see exactly how the same tags look on each platform.
How do I stop Facebook from showing the wrong image?
Specify the og:image tag explicitly with a 1200x630 pixel image at an absolute HTTPS URL. Without an explicit og:image tag, Facebook picks a random image from your page. After adding the og:image tag, use the Facebook Sharing Debugger to clear the cache and confirm Facebook now reads the correct image. For existing posts, the preview cannot be changed retroactively — only new shares will show the updated image.