Why Open Graph Tags Aren't Working: Complete Troubleshooting Guide 2026

Open Graph tags not showing in previews? Learn common OG tag issues, why Facebook ignores your meta tags, and how to debug and fix broken social previews.

Why Open Graph Tags Aren't Working: Complete Troubleshooting Guide 2026

You've added Open Graph meta tags to your website. But when you share links on Facebook, LinkedIn, or Twitter, the preview still shows the wrong image, title, or description. Here's why it happens and how to fix it.

Table of Contents

  1. Why Open Graph Tags Fail
  2. The 6 Most Common Reasons OG Tags Don't Work
  3. How to Debug Broken OG Tags
  4. Fixing the Issues: Step-by-Step Solutions
  5. Cache Issues & Social Crawlers
  6. Best Practices for Reliable OG Tags
  7. FAQ: OG Tags Troubleshooting

Why Open Graph Tags Fail

When you share a URL on social media platforms (Facebook, LinkedIn, Twitter, etc.), those platforms send a bot (called a "crawler" or "spider") to your website to extract preview information. This bot reads specific HTML meta tags called Open Graph (OG) tags to determine what image, title, and description to display.

If your OG tags are wrong, broken, or not configured correctly, social platforms either:

  • Show generic previews (just the URL, no image or description)
  • Display outdated information (old preview cached from a previous share)
  • Show incorrect meta data (wrong title, image, or description)
  • Ignore your tags entirely (trust their own scraping rules instead)

The 6 Most Common Reasons OG Tags Don't Work

1. OG Tags Are in the Wrong Place (HTML Head)

The Problem: Open Graph tags must be in the <head> section of your HTML, not in the body.

❌ WRONG:

<body>
  <meta property="og:title" content="My Title">
  <h1>Content</h1>
</body>

✅ CORRECT:

<head>
  <meta property="og:title" content="My Title">
  <meta property="og:image" content="https://...">
</head>

2. Missing Required OG Tags

The Problem: Even if tags are in the head, you might be missing critical required tags. Different platforms require different sets of tags.

The 4 Essential OG Tags:

  • og:title — The headline shown in the preview
  • og:description — The description text
  • og:image — The image URL (must be absolute, not relative)
  • og:url — The canonical URL (helps Facebook avoid duplicates)

Example of complete OG setup:

<meta property="og:title" content="Open Graph Tags Troubleshooting">
<meta property="og:description" content="Fix broken previews on social media">
<meta property="og:image" content="https://share-preview.com/images/og-article.jpg">
<meta property="og:url" content="https://share-preview.com/blog/og-troubleshooting.html">
<meta property="og:type" content="article">

3. Image URLs Are Broken or Relative

The Problem: Social crawlers cannot fetch images using relative URLs. Your og:image must be a full, absolute URL that resolves to a real image file.

❌ WRONG (relative URL):

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

✅ CORRECT (absolute URL):

<meta property="og:image" content="https://yourdomain.com/images/preview.jpg">

Also verify:

  • Image actually exists (return 200 status code, not 404)
  • Image is at least 1200x630 pixels (minimum recommended)
  • Image file format is JPG, PNG, or GIF
  • Image is publicly accessible (not behind login or blocked by robots.txt)

4. Server Returns Wrong HTTP Status Code

The Problem: If your page returns a 404, 301 redirect, or other non-200 status code, social crawlers may not index the OG tags.

Before sharing a link, the social platform checks what HTTP status your URL returns. If it's not 200 (OK), the crawler might skip reading your OG tags.

Check your page status with:

curl -I https://yoururl.com/page

The first line should say HTTP/1.1 200 OK or similar.

5. Social Platform Cache Issues

The Problem: Facebook, LinkedIn, and Twitter cache previews. If you updated your OG tags but don't clear the cache, the old preview shows forever.

Each social platform caches previews differently:

6. Invalid or Malformed Meta Tags

The Problem: Syntax errors in your HTML prevent the tags from being parsed correctly.

❌ WRONG (unclosed tag):

<meta property="og:title" content="My Title"

❌ WRONG (missing quotes):

<meta property=og:title content=My Title>

✅ CORRECT:

<meta property="og:title" content="My Title">

How to Debug Broken OG Tags

Step 1: View Your Page Source

Right-click your page → "View Page Source" (or Ctrl+U). Search for "og:" to find your OG tags. Are they in the <head>? Do they have values?

Step 2: Validate with Share Preview

Best tool: Go to Share Preview, paste your URL, and instantly see:

  • What your preview will look like on each platform
  • All detected OG tags and their values
  • Which tags are missing or invalid
  • Image URLs and whether they're accessible

Step 3: Use Official Social Validators

Step 4: Check HTTP Headers

Use curl to verify your page returns HTTP 200:

curl -I https://yoururl.com/page

Or use an online HTTP header checker.

Fixing the Issues: Step-by-Step Solutions

Solution 1: Add Missing OG Tags

Ensure all 4 essential tags are present in your <head>:

<!-- Essential OG Tags -->
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Brief description (50-160 characters)">
<meta property="og:image" content="https://yourdomain.com/image.jpg">
<meta property="og:url" content="https://yourdomain.com/page">
<meta property="og:type" content="website">

<!-- Additional Recommended Tags -->
<meta property="og:site_name" content="Your Site Name">
<meta property="og:locale" content="en_US">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="Brief description">
<meta name="twitter:image" content="https://yourdomain.com/image.jpg">

Solution 2: Fix Image URLs

Replace all relative image URLs with absolute URLs:

❌ Before:

<meta property="og:image" content="/assets/social-preview.png">

✅ After:

<meta property="og:image" content="https://yourdomain.com/assets/social-preview.png">

Pro tip: Verify the image URL works by visiting it directly in your browser.

Solution 3: Clear Social Platform Cache

Solution 4: Fix HTTP Status Code

Ensure your page returns HTTP 200. Common issues:

  • 404 errors: Make sure the URL is correct and the page exists
  • 301 redirects: Use the final URL after redirect for sharing
  • Robots.txt blocking: Ensure social crawlers can access your page

Cache Issues & Social Crawlers

How Social Platforms Cache Previews

When someone shares a link on social media, the platform:

  1. Sends a crawler bot to your website
  2. Reads your HTML and extracts OG tags
  3. Caches the preview to avoid repeated crawls
  4. Returns the cached preview when others click the link

Important: If you later change your OG tags, the old cached preview still shows to everyone until you manually refresh the cache.

How to Force Refresh Caches

Facebook Cache:

  1. Go to Facebook Sharing Debugger
  2. Paste your URL
  3. Click "Scrape Again"

LinkedIn Cache:

  1. Go to LinkedIn Post Inspector
  2. Paste your URL
  3. Click "Inspect"

Best Practices for Reliable OG Tags

1. Always Use Absolute URLs (Not Relative)

Social crawlers can't fetch resources using relative paths.

  • ✅ https://yourdomain.com/image.jpg
  • ❌ /image.jpg

2. Test Every OG Tag Change Immediately

After updating OG tags, use Share Preview or the official validators to verify changes are detected.

3. Use Proper Image Dimensions

  • Minimum: 1200x630 pixels
  • Aspect ratio: 1.91:1 (width:height)
  • Maximum: 5MB file size
  • Format: JPG, PNG, or GIF (not SVG or WEBP)

4. Set Canonical URLs

Always include og:url to avoid duplicate preview issues:

<meta property="og:url" content="https://yourdomain.com/page">

5. Include Twitter Card Tags Too

Twitter doesn't use OG tags by default. Add Twitter Card tags for Twitter previews:

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Title">
<meta name="twitter:description" content="Your description">
<meta name="twitter:image" content="https://yourdomain.com/image.jpg">

6. Monitor Using Share Preview

Use Share Preview regularly to audit your OG tags and catch issues before users see them.

FAQ: OG Tags Troubleshooting

Q: I updated my OG tags, but the old preview still shows. Why?

A: Social platforms cache previews. You need to manually clear the cache using the platform's debug tool:

Q: My OG image shows as broken (X icon). What's wrong?

A: The image URL is inaccessible or returns 404. Check:

  • Image URL is absolute (https://domain.com/image.jpg, not /image.jpg)
  • Image file actually exists (visit URL in browser)
  • Image is not behind login or password
  • Robots.txt doesn't block image crawling
Q: Do I need separate Twitter Card tags if I have OG tags?

A: Not exactly. Twitter can use OG tags as fallback, but for best control, add Twitter Card tags specifically. They override OG tags on Twitter. 

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Title">
<meta name="twitter:image" content="https://...">
Q: My page is dynamic (built with JavaScript). Will OG tags work?

A: No, not automatically. Social crawlers don't execute JavaScript. They only read static HTML. Solutions:

  • Server-side rendering (SSR): Generate OG tags on the server before sending HTML
  • Pre-rendering: Generate static HTML files ahead of time
  • API alternative: Use a service like Share Preview to preview generated content
Q: How often do social platforms re-crawl pages?

A: Varies by platform:

  • Facebook: ~24 hours (or immediate if you use Sharing Debugger)
  • LinkedIn: ~7 days (or immediate if you use Post Inspector)
  • Twitter: On-demand (depends on Expires header)

To force immediate crawl, use the platform's debug tool.

Test Your OG Tags Instantly

See exactly how your links will preview on Facebook, LinkedIn, Twitter, and other platforms.

→ Open Share Preview Tool

Summary: Quick Checklist

  • ☐ All 4 essential OG tags present: og:title, og:description, og:image, og:url
  • ☐ Image URL is absolute (https://domain.com/image.jpg)
  • ☐ Image file exists and returns 200 status code
  • ☐ Image dimensions at least 1200x630 pixels
  • ☐ All OG tags are in the <head> section
  • ☐ No syntax errors in meta tags (all properly closed)
  • ☐ Page returns HTTP 200 OK status
  • ☐ After updates, clear cache using platform debug tools
  • ☐ Twitter Card tags included for Twitter previews
  • ☐ Validate with Share Preview before sharing
← Back to Blog Next: Twitter Cards Guide →

Related Articles

See How Your Page Looks When Shared

Test your OG tags across Twitter, LinkedIn, Facebook, Slack, and WhatsApp instantly.

Test Share Preview Free →