FreeToolsHub
Back to Blog
Tutorial

How to Fix og:image Not Showing on WhatsApp, Facebook & LinkedIn

SEO & Web Team (Technical SEO Specialist) June 8, 2026 6 min read

The Problem: You Share a Link and the Image Is Missing

You paste your link into WhatsApp or Facebook and instead of a beautiful preview card, you get a bare URL or a blank gray box. This is one of the most common technical SEO problems on the web — and it almost always comes down to a handful of fixable issues with your og:image tag.

Before changing anything, run your URL through our free Open Graph Checker to see exactly what platforms can read from your page right now.

Fix 1: Use an Absolute URL

The single most common mistake. This fails:

<meta property="og:image" content="/images/banner.png" />

This works:

<meta property="og:image" content="https://example.com/images/banner.png" />

Social crawlers do not resolve relative paths. Your og:image URL must start with https://.

Fix 2: Check the Image Size and Format

  • Dimensions: Use 1200 × 630 pixels (1.91:1 ratio). Images smaller than 200 × 200 are rejected by Facebook entirely.
  • File size: Keep it under 1 MB. WhatsApp is especially strict — very large images are silently dropped.
  • Format: Use JPG, PNG, or WebP. Avoid SVG — most platforms will not render it.

If your image is too heavy, compress or convert it with our Image Converter before uploading.

Fix 3: Clear the Platform Cache

Platforms cache link previews aggressively. If you fixed your tags but still see the old (or missing) image:

  1. Facebook & WhatsApp: Open Facebook's Sharing Debugger, enter your URL, and click "Scrape Again".
  2. LinkedIn: Use the LinkedIn Post Inspector to force a refresh.
  3. X (Twitter): Cards refresh roughly weekly; re-checking the URL in the composer usually triggers a re-crawl.

Fix 4: Make Sure the Image Is Publicly Accessible

The crawler must be able to download your image without logging in. Check that:

  • The image URL opens in an incognito browser window.
  • Your robots.txt does not block the image folder.
  • The image is not behind a redirect chain (serve it directly).
  • Your server or CDN does not block bot user agents like facebookexternalhit.

Fix 5: Declare Image Dimensions

Adding width and height tags lets Facebook render the card correctly on the first share, instead of after the first crawl:

<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

Fix 6: Only One og:image (or Put the Best One First)

If your page declares several og:image tags, platforms pick the first one. Audit your page source — many CMS themes and plugins inject a default og:image before your custom one.

Fix 7: Add Twitter Card Tags for X

X (Twitter) prefers its own tags and falls back to Open Graph. For a large preview card, add:

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:image" content="https://example.com/images/banner.png" />

Verify the Fix

After making changes, test your page again with the Open Graph Checker. It previews your link card for Facebook, X, LinkedIn, and WhatsApp side by side, so you can confirm the image renders everywhere before you share the link publicly.