Open Graph Image Not Showing? Here's How to Fix It

Open Graph image not showing is one of the most common and most frustrating SEO problems — you update the tag, share the link, and the old broken image still appears. Or no image appears at all. The fix depends on which of five distinct causes is responsible, and each has a different solution. This guide walks through every cause with a concrete example and tells you exactly how to fix it.

The 5 most common reasons your Open Graph image is not showing

Before diving into fixes, here is a quick diagnostic table. Find the symptom that matches your situation — then jump to that section.

Step 1 — Check that your og:image tag exists and is correct

The most common cause of no image preview is a missing or incorrectly formatted og:image tag. To check, open your page in a browser, right-click anywhere, and choose View Page Source. Press Ctrl+F (or Cmd+F) and search for og:image.

Here is what a correct og:image meta tag looks like:

<!-- Correct ✅ -->
<meta property="og:image" content="https://yoursite.com/images/page-preview.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

<!-- Wrong — relative URL ❌ -->
<meta property="og:image" content="/images/page-preview.jpg" />

<!-- Wrong — HTTP not HTTPS ❌ (Facebook requires HTTPS) -->
<meta property="og:image" content="http://yoursite.com/images/page-preview.jpg" />

The three most common mistakes: using a relative URL (starting with /) instead of an absolute URL (starting with https://), using HTTP instead of HTTPS, and missing the property="og:image" attribute entirely (some templates use name= instead of property=, which is wrong for Open Graph).

If your tags are missing or broken, use our free Open Graph Generator to produce correctly formatted og: and twitter: tags for any page.

Step 2 — Verify the image URL is accessible

Even with a syntactically correct tag, the image will not show if the URL itself is broken or blocked. Test this by pasting the exact value of your og:image into a browser address bar. The image should load directly.

Real example: A Next.js site had this tag:

<meta property="og:image" content="https://example.com/og/mortgage-calculator" />

The URL was a dynamic OG image route — which worked in the browser. But the robots.txt file had Disallow: /og/, blocking Facebook's crawler from fetching it. Result: no image in any share preview. The fix was adding Allow: /og/ to robots.txt.

Common access blocks to check:

• robots.txt Disallow — use our Robots.txt Generator to check your rules
• Auth-protected CDN — image URLs that require cookies or signed tokens cannot be fetched by crawlers
• Incorrect file path — typo in the path, wrong directory, or case mismatch on Linux servers
• Large file size — Facebook has a 8MB file size limit; LinkedIn has a 5MB limit

Step 3 — Check your image dimensions

Each platform has its own minimum image size and preferred aspect ratio. An image that is too small will either not display at all or display as a tiny thumbnail rather than a full preview card.

Practical example: A blog post used a 400×300 thumbnail as the og:image. On Facebook, it appeared as a small inset image next to the text — not the large card format. On LinkedIn, it did not appear at all. The fix was creating a dedicated 1200×630 preview image for the post.

Note the Twitter/X difference: Twitter crops images to a 2:1 ratio, meaning it shows 1200×600 of a 1200×630 image — cutting 30px from the bottom. Keep important content (text, logos) centred and away from the very bottom edge of your OG image.

Step 4 — Clear the platform cache

This is the cause behind most "I already fixed it but it still shows the old image" reports. Social platforms crawl your URL once and cache the result aggressively — sometimes for days. Updating your og:image tag does nothing to existing cached previews.

Each major platform has a dedicated tool to clear the cache and force a fresh crawl:

• Facebook: Go to developers.facebook.com/tools/debug → paste your URL → click Debug → click Scrape Again. You may need to click Scrape Again twice for stubborn caches.
• LinkedIn: Go to linkedin.com/post-inspector → paste your URL → click Inspect.
• Twitter/X: Go to cards-dev.twitter.com/validator → paste your URL → click Preview card.
• WhatsApp: No cache clearing tool exists. Add a query parameter to the URL — ?v=2 — to make it look like a different URL to WhatsApp's crawler.

Example: After updating the og:image on a mortgage calculator page, shares on Facebook still showed the old image for 3 days. Running the Sharing Debugger and clicking "Scrape Again" forced a fresh crawl and the new image appeared within minutes.

Why your og:image is not showing on LinkedIn specifically

LinkedIn is the strictest of the major platforms. Even when Facebook shows your image correctly, LinkedIn may not — because it has different minimum requirements.

A 600×315 image that displays fine on Facebook will often fail to render on LinkedIn. Always create OG images at 1200×630 — it meets or exceeds the requirements of every major platform simultaneously.

How to generate and test Open Graph tags

If you need to create or fix your Open Graph tags from scratch, our free Open Graph Generator produces correctly formatted og: and twitter: tags for any page — with the correct property names, absolute URL format, and recommended dimensions. Paste the output into your page <head> and you are done.

After adding or updating your tags, always test with the Facebook Sharing Debugger before announcing. It shows exactly what Facebook sees and catches formatting errors that look correct in source but fail in practice.

Key takeaways

• Check that og:image uses an absolute HTTPS URL — relative URLs like /images/og.jpg will not work.
• Open the image URL directly in a browser to confirm it loads — crawlers need public access to fetch it.
• Use 1200×630px images to meet the requirements of Facebook, LinkedIn, and Twitter simultaneously.
• After fixing tags, clear the platform cache using the Sharing Debugger, Post Inspector, or Card Validator — otherwise the old image keeps showing.
• LinkedIn has stricter size requirements than Facebook — a 600×315 image often fails on LinkedIn even when it works elsewhere.

Frequently asked questions

Why does my Open Graph image work on Facebook but not Twitter?

Twitter requires twitter:card meta tags in addition to Open Graph tags. Without a twitter:card tag set to summary_large_image, Twitter falls back to a small thumbnail or no image. Add these tags alongside your og: tags:

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:image" content="https://yoursite.com/images/og.jpg" />

How do I add Open Graph tags in WordPress?

Install Yoast SEO or RankMath — both add og:image, og:title, and og:description automatically to every page and post. You can set a custom social image per post in the Social tab of each post's SEO settings panel.

How long does the Open Graph cache last?

Facebook caches previews for up to 7 days by default. LinkedIn caches for approximately 7 days. Twitter/X caches for approximately 30 minutes to 1 hour. Running each platform's cache-clearing tool overrides the cache immediately — do not wait for it to expire naturally.

Can I have different images for Facebook and Twitter?

Yes — set og:image for Facebook/LinkedIn/WhatsApp and twitter:image separately for Twitter/X. If twitter:image is absent, Twitter falls back to og:image. This lets you use a 1.91:1 image for Facebook and a 2:1 cropped version for Twitter.

My og:image shows correctly in the debugger but not in actual shares. Why?

The debugger and live shares use different cache layers. Run the Sharing Debugger, click "Scrape Again", wait 2 minutes, then test a new share in a private/incognito browser window. If it still shows the old image, click "Scrape Again" a second time — stubborn caches sometimes require two refreshes.