Why Is My Link Preview Showing the Wrong Image? 6 Fixes

Why Is My Link Preview Showing the Wrong Image? 6 Fixes

by

Share a link on WhatsApp, Facebook, or LinkedIn and a preview card appears — title, description, image. Sometimes it looks perfect; sometimes you are left asking why is my link preview showing the wrong image — a cropped logo, or no image at all. What are Open Graph meta tags? They are the HTML tags that control exactly that preview: you declare the title, description, and image, instead of letting each platform guess.

This beginner’s guide covers the core tags, the right og:image sizes, the difference between Open Graph and Twitter Cards, how to debug broken previews (including the notorious cache problem), and how to verify everything with our free Open Graph preview tool. If meta tags in general are new to you, start with our companion guide on what meta tags are.

Table of Contents

What Are Open Graph Meta Tags? The Simple Version

If you are asking what are Open Graph meta tags at the protocol level: Open Graph is a protocol created by Facebook in 2010 that lets any web page declare how it should look when shared. You add a handful of <meta> tags to your page’s <head>, and platforms that understand the protocol — Facebook, LinkedIn, WhatsApp, Telegram, Slack, Discord, Pinterest — use them to build the preview card.

Without these tags, platforms fall back to guessing: they grab the page <title>, the first chunk of text, and the first vaguely-suitable image they find. That guessing is the source of nearly every broken preview — the wrong image, a 1×1 tracking pixel as your “preview,” or a description cut mid-sentence. Open Graph tags replace guessing with declaring. They do not affect Google rankings at all — they control presentation on social platforms, which affects whether people click, which is arguably more valuable than a ranking tweak.

The Core Tags: og:title, og:description, og:image, og:url

Four tags do 90% of the work of what are Open Graph meta tags in practice. Here they are, with a real example:

<meta property="og:title" content="What Are Open Graph Meta Tags? A Simple Guide">
<meta property="og:description" content="Control how your links look when shared — titles, descriptions, and preview images explained.">
<meta property="og:image" content="https://example.com/preview-image.jpg">
<meta property="og:url" content="https://example.com/what-are-open-graph-meta-tags/">

  • og:title — the preview headline. Can match your page title or be punchier for social. Keep it under ~60 characters so it does not truncate.
  • og:description — one to two sentences. This is ad copy for the click: write it like a meta description (our meta description guide applies here too).
  • og:image — the preview image. Must be an absolute URL (https://…, not a relative path) — the #1 beginner error. See sizing below.
  • og:url — the canonical URL of the page. Tells platforms which URL the shares, likes, and comments belong to, even if the page is reachable via multiple URLs.

Useful extras: og:type (website for most pages, article for blog posts — article unlocks article:published_time and article:author), og:site_name (your brand), and og:locale (e.g. en_US). Note the syntax: Open Graph uses property=, not name= — a common copy-paste error when mixing them with regular meta tags.

og:image Size: Getting the Preview Image Right

When people ask what are Open Graph meta tags, they usually mean these four — and the image makes or breaks the preview card, which is where most people go wrong on sizing:

  • Recommended: 1200 × 630 pixels. This is the size Facebook and LinkedIn document, and it renders crisply on high-density screens. It is the safe universal choice.
  • Minimum: 600 × 315 pixels. Below this, some platforms refuse to render a large preview and fall back to a small thumbnail layout.
  • Aspect ratio: 1.91:1 (the 1200×630 ratio). WhatsApp crops aggressively to roughly this shape; off-ratio images get center-cropped, often decapitating text or faces.
  • Format: JPG or PNG. Keep it under ~1 MB — some platforms time out fetching huge images and show nothing. (WebP support in scrapers is inconsistent; stick to JPG/PNG for preview images.)
  • Safe zone: keep critical text and logos in the center. Different platforms crop differently — design for the middle 80%.

If your image is not already 1200×630, our image resizer will get it there in the browser. And a design tip from experience: preview images with 3–7 words of large text outperform plain photos for click-through, because most social feeds are scanned, not read.

Open Graph Tags vs Twitter Cards: What’s the Difference?

A common follow-up to “what are Open Graph meta tags” is how Twitter Cards fit in. Twitter (X) created its own variant called Twitter Cards (twitter:card, twitter:title, twitter:image…). The good news: Twitter falls back to Open Graph tags when Twitter-specific ones are absent. In practice, most sites today set Open Graph tags plus exactly one Twitter tag:

<meta name="twitter:card" content="summary_large_image">

That single tag tells X to render the large-image card layout; X then reads the title, description, and image from your og: tags. You only need the full twitter:title / twitter:description / twitter:image set if you want different content on X than everywhere else — rare. One platform-specific note: X’s image handling has its own quirks (it historically preferred 1200×675 / 16:9), but 1200×630 works acceptably everywhere, so do not maintain two images unless you enjoy pain.

Why Is My Link Preview Showing the Wrong Image?

If you are asking why is my link preview showing the wrong image, the usual causes — in order of likelihood — are:

  1. No og:image tag at all. The platform guessed — and guessed badly. Add the tag.
  2. Relative image URL. content="/images/preview.jpg" means nothing to a scraper with no page context. Always absolute: https://yoursite.com/images/preview.jpg.
  3. Image too small or wrong ratio. Under ~600×315, platforms downgrade to thumbnail or skip the image.
  4. Image blocked. Hotlink protection, robots.txt blocking the image path, or requiring login — the scraper is not logged in as you.
  5. HTTPS mixed content. An http:// image on an https:// page gets refused by strict scrapers.
  6. The platform cached the old version. You fixed everything and it still shows the old image — the classic reason why is my link preview showing the wrong image even after a fix. That is the cache problem, next section.

The Cache Problem (and How to Fix It)

Here is the trap behind why is my link preview showing the wrong image even after you fixed everything: the first time anyone shares your URL, each platform’s scraper fetches your tags and caches them — for days or weeks. Update your og:image afterward and shares keep showing the old preview, because nobody re-fetches. This is not a bug in your tags; it is by design (scrapers cannot re-fetch the entire web on every share).

The fix is to force a re-scrape with each platform’s debugger (next section) — every debugger has a “scrape again” / refresh function that busts the cache for that URL. The pragmatic workflow: finalize your Open Graph tags before the first public share. For URLs already shared widely, the debugger refresh is the only lever — there is no global cache purge. WhatsApp is the stubborn one: it caches aggressively on-device, so even after a debugger refresh, individuals may need to wait or clear the chat cache to see the update.

Debugging Tools: See What Platforms See

Do not guess at why is my link preview showing the wrong image — these tools show you exactly what each scraper extracts:

  • Facebook Sharing Debugger — enter the URL, see the scraped tags, warnings, and the preview; the “Scrape Again” button busts Facebook’s cache.
  • LinkedIn Post Inspector — same idea for LinkedIn’s scraper.
  • X Card Validator — previews the Twitter Card rendering.
  • Our Open Graph preview tool — paste a URL and see the extracted tags and a simulated preview card instantly, no platform login required. Ideal for a quick pre-publish check.

Run every important page through at least the Facebook debugger before launch. It catches the relative-URL mistake, the undersized image, and the missing tags in seconds — the top answers to why is my link preview showing the wrong image, diagnosed free.

Try It: Open Graph Preview Tool

Now that you know what are Open Graph meta tags and how to debug them, before you share your next article, paste its URL into our free Open Graph preview tool and confirm the title, description, and image are what you intended — it is the thirty-second check that stops you from ever asking why is my link preview showing the wrong image again. Need to generate the tags themselves? Our meta tags generator builds the full head section including Open Graph and Twitter Card tags. The protocol specification is documented at ogp.me and MDN’s meta element reference covers the underlying tag mechanics.

Frequently Asked Questions

What size should my og:image be?

1200 x 630 pixels (1.91:1 aspect ratio), in JPG or PNG under 1 MB, referenced by absolute https:// URL. That is the documented recommendation from Facebook and LinkedIn and renders well on WhatsApp, Telegram, and Slack too. Keep key content centered — platforms crop edges differently.

Why is my link preview showing the wrong image on WhatsApp?

Usually a missing or relative og:image URL, an undersized image, or WhatsApp’s aggressive caching showing a stale preview. Fix the tags (absolute URL, 1200×630), force a re-scrape via Facebook’s Sharing Debugger, and note that individual phones may cache the old preview until the chat cache clears.

What is the difference between Open Graph tags and Twitter Cards?

Open Graph (og: tags) is the cross-platform standard from Facebook; Twitter Cards (twitter: tags) are X’s variant. X falls back to og: tags, so most sites only need Open Graph tags plus one twitter:card tag set to summary_large_image for the big-card layout on X. That is the short version of what are Open Graph meta tags versus Twitter Cards: one cross-platform standard, one platform-specific variant.

Do Open Graph tags affect SEO?

Not directly — Google does not use Open Graph tags as a ranking factor. Their value is click-through: a good preview card gets more clicks when your link is shared on social platforms and messaging apps, which drives real traffic regardless of rankings.