Open Graph Troubleshooting Guide

You’ve added Open Graph tags to your site, but something isn’t working. The preview card shows the wrong image, an old title, or nothing at all. Before you start randomly changing tags, work through this systematic troubleshooting guide.

---

Problem 1: No Preview Card Appears at All

Likely Causes

1. Missing required tags — Every page needs at minimum og:title, og:type, og:url, and og:image.
2. Client-side rendering — Social crawlers don’t execute JavaScript. If your OG tags are rendered by React/Vue, they’re invisible to crawlers. See Open Graph JavaScript Implementation.
3. Blocked crawlers — Your robots.txt or firewall may be blocking social media user-agents (facebookexternalhit, LinkedInBot, Twitterbot).

Diagnostic Steps

# Check if OG tags exist in server-rendered HTML
curl -s https://your-url.com | grep 'og:'

# Simulate Facebook's crawler
curl -A "facebookexternalhit/1.1" -s https://your-url.com | grep 'og:'

If the curl output is empty, your OG tags aren’t being server-rendered.

---

Problem 2: Wrong Image Showing

Likely Causes

1. Cached old image — Platforms cache preview data for hours to days. See “Cache Invalidation” below.
2. Image URL returns 301 redirect — Some crawlers don’t follow redirects for image URLs. Use the direct, final URL.
3. Multiple og:image tags — The first og:image tag is used as the primary. Ensure it’s the one you want displayed.
4. Image too small — If your image is below the platform’s minimum size, it may be ignored entirely.

Fix

Verify your image URL returns HTTP 200 directly:

curl -I https://your-url.com/og-image.png

The response should show HTTP/2 200 with content-type: image/png (or image/jpeg).

---

Problem 3: Stale/Cached Preview Data

This is the most common frustration. You’ve updated your tags, but platforms still show old data.

Facebook

1. Open Facebook Sharing Debugger.
2. Enter your URL.
3. Click Scrape Again (click it twice if needed).

LinkedIn

1. Open LinkedIn Post Inspector.
2. Enter your URL and click Inspect.

WhatsApp

WhatsApp caches per conversation. Append a query parameter to force a fresh fetch:

https://your-url.com/page?v=2

Discord & Slack

These platforms typically re-fetch metadata when a new URL is shared. If a cached version persists, clearing your browser cache and resharing usually resolves it.

For detailed platform-by-platform cache invalidation steps, see How to Fix Missing Link Previews on LinkedIn & WhatsApp.

---

Problem 4: Image Cropped Incorrectly

Different platforms crop preview images at different points. If your text or logo is cut off:

1. Use 1200×630 px images — This is the universally safe dimension.
2. Keep important content in the center 80% — Avoid placing text or logos at the edges.
3. Test on multiple platforms — Use our Social Preview Simulator to see how your image renders across all platforms simultaneously.

For detailed sizing requirements, see the Open Graph Image Size Guide.

---

Problem 5: Tags Present But Not Recognized

Check for Syntax Errors

OG tags use property, not name:

<!-- WRONG -->
<meta name="og:title" content="Page Title" />

<!-- CORRECT -->
<meta property="og:title" content="Page Title" />

Check for Duplicate Tags

Having two different og:title tags confuses parsers. Ensure each property appears only once (except intentional arrays like og:image and article:tag).

Check HTML Encoding

Special characters in content values must be HTML-encoded:

<!-- WRONG -->
<meta property="og:title" content="Tom & Jerry's Guide" />

<!-- CORRECT -->
<meta property="og:title" content="Tom &amp; Jerry&#39;s Guide" />

---

Problem 6: Twitter/X Not Showing Card

Twitter has its own tag system. If Twitter cards aren’t rendering:

1. Verify you have <meta name="twitter:card" content="summary_large_image" />.
2. If you rely on OG fallback, ensure your og:title, og:description, and og:image are all present.
3. See Twitter Card Not Showing? How to Fix It for Twitter-specific debugging.

---

Quick Troubleshooting Checklist

• All four required OG tags are present
• Tags use property attribute (not name)
• Image URL is absolute HTTPS
• Image URL returns HTTP 200 (not redirect)
• Image is at least 200×200 px (1200×630 recommended)
• Tags are server-rendered (visible in View Page Source)
• No duplicate tags
• Crawlers are not blocked by robots.txt or firewall
• Platform cache has been invalidated after changes

---

Related Resources

• How to Test Open Graph Tags — Complete testing workflow.
• Open Graph Inspector — Multi-platform preview and audit tool.
• Meta Tag Auditor — Check for missing and misconfigured meta tags.