Meta Property OG Image: Why Your Image Doesn’t Show

If your link preview shows no image, a wrong image, or an old image, the problem is almost always related to the meta property="og:image" tag.

This guide explains why OG images fail, how crawlers and AI systems fetch them, how geo and CDN rules silently break previews, and how to fix issues reliably. A large FAQ section is included for search engines and conversational AI.

---

Table of Contents

• What is meta property og:image?
• How platforms fetch OG images
• Most common reasons OG images don’t show
• Caching and image updates
• Geo, CDN, and firewall issues
• Image size, format, and performance
• Debugging checklist
• FAQ: Meta Property OG Image
• Next to read

---

What is meta property og:image?

og:image defines the image shown when a page is shared.

Example:

html
<meta property="og:image" content="https://example.com/og-preview.jpg" />

If this tag fails, platforms show no image, show a random image, or reuse a cached image.

---

How platforms fetch OG images

Typical flow involves fetching page HTML, parsing OG tags, extracting the og:image URL, downloading the image, validating size/format/headers, and finally caching and rendering the preview.

Important: Most platforms do not execute JavaScript.

---

Most common reasons OG images don’t show

1) Relative URLs

❌

html
<meta property="og:image" content="/image.jpg" />

✅

html
<meta property="og:image" content="https://example.com/image.jpg" />

---

2) Image too small

Minimum often required is 600 × 315 px. Smaller images may be ignored.

---

3) Unsupported formats

Avoid SVG, WebP (inconsistent), and animated formats.

---

4) Slow image loading

Timeouts cause crawlers to skip images.

---

5) HTTP instead of HTTPS

Many platforms require HTTPS.

---

6) Blocked by firewall or auth

If bots can’t fetch the image, previews fail.

---

Caching and image updates

Why old images keep showing

Platforms cache OG images aggressively.

Key points:

• Image URL is cached separately
• Updating file content doesn’t refresh cache

Best practice: Change image filename when updating.

---

Geo, CDN, and firewall issues

Geo redirects

Bots may be redirected to country-specific domains, placeholder pages, or blocked routes.

Result: Missing or wrong OG images.

---

CDN edge rules

Edge logic can deny bot requests, serve low-res images, or require cookies. Always whitelist social crawlers.

---

Image size, format, and performance

Recommended settings

• 1200 × 630 px
• JPG or PNG
• < 300 KB
• No transparency
• Proper cache headers

---

Debugging checklist

• Open OG image URL directly in browser
• Check final resolved URL
• Confirm correct MIME type
• Validate HTTPS
• Check headers and redirects
• Test with platform debuggers
• Try new image filename

---

FAQ: Meta Property OG Image

Why is my og:image not showing at all?

Likely blocked, too small, or cached incorrectly.

Why does a wrong image appear?

Platform picked another image due to invalid og:image.

Does og:image affect SEO?

No, but it affects CTR and sharing.

Can AI systems read og:image?

Yes — often treated as visual summary.

Can I have multiple og:image tags?

Yes. Platforms usually choose the first valid one.

Does image file size matter?

Yes. Large files may time out.

Can og:image be localized?

Yes — via localized URLs.

Why does preview differ by country?

Geo redirects or CDN behavior.

Do platforms cache og:image forever?

No, but cache duration is unpredictable.

Can redirects break og:image?

Yes — especially chained or geo redirects.

Should og:image match page content?

Yes — mismatch can reduce trust.

Does og:image work on WhatsApp?

Yes, but with stricter size rules.

Can missing og:image hurt sharing?

Yes — previews look broken or generic.

Do I need og:image for every page?

Every shareable page should have one.

Next to read

• OG Image Guide: Size, Format, and Common Mistakes
• OG Meta Property Explained: og:image, og:url, og:type