Facebook Link Preview Not Working? Fix It in 2025 (OG Tags + Debugger)
Fix your Facebook link preview: missing image, wrong title, or cached old info. Learn OG tag requirements, image specs, and how to force Facebook to re-scrape.
Facebook Link Preview:
Complete Fix Guide for 2025
Missing image, wrong title, or outdated preview? Here's exactly how Facebook generates previews, what OG tags you need, and how to fix every common problem.
How Facebook Generates Link Previews
When someone pastes a URL into a Facebook post or message, Facebook's crawler — sometimes called the Facebook Scraper or Open Graph Scraper — visits your URL and reads specific HTML meta tags.
This happens before the post is published. Facebook fetches the page within a few seconds of the URL being pasted, extracts the Open Graph (OG) tags, and renders a preview card — title, description, image, and site name — directly in the composer.
The Caching Problem
Here's the catch: Facebook caches the scraped data aggressively. Once Facebook has scraped your page, it stores that preview information and reuses it — sometimes for days or weeks — even if you update your OG tags. This is why you can fix your tags but still see the old preview: you're seeing Facebook's cached version.
The cache is one of the most common sources of confusion. The page looks right if you check it yourself, but Facebook still shows wrong data. The solution is to manually invalidate Facebook's cache — we'll cover that in the re-scrape section.
What Facebook Reads
Facebook reads standard Open Graph protocol tags — a set of <meta> tags in your page's <head>. These tags were designed specifically for social sharing and are now a universal standard across Facebook, LinkedIn, Twitter/X, Slack, Discord, and WhatsApp.
facebookexternalhit/1.1. If your server blocks bots, Facebook can't read your OG tags. Check that your robots.txt or Cloudflare rules don't block this user-agent.
Required OG Tags for Facebook
These are the Open Graph tags Facebook uses to build link previews. Add them to your page's <head> section:
<!-- Required for Facebook --> <meta property="og:title" content="Your Page Title Here"> <meta property="og:description" content="A compelling description under 200 characters."> <meta property="og:image" content="https://yoursite.com/images/preview.jpg"> <meta property="og:url" content="https://yoursite.com/this-page"> <meta property="og:type" content="website"> <!-- Strongly recommended --> <meta property="og:site_name" content="Your Brand Name"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630">
Tag-by-Tag Breakdown
- og:title — The headline of your preview card. Keep it under 60–70 characters to avoid truncation. This overrides your
<title>tag for social sharing. - og:description — The body text under the title. Aim for 100–200 characters. Truncated beyond ~300. Don't duplicate the title.
- og:image — The preview image URL. Must be an absolute HTTPS URL (not relative). This single tag determines whether your post looks professional or terrible.
- og:url — The canonical URL of the page. Helps Facebook resolve redirects and deduplicate share counts. Use your canonical URL, not the current URL.
- og:type — Usually
websiteorarticle. Articles get slightly different treatment (byline, publish date) in some contexts. - og:site_name — Your brand name, displayed as small text below the title. Builds trust and recognition.
- og:image:width / og:image:height — Explicit dimensions help Facebook render the image faster without waiting to download and analyze it. Always include these.
Image Specifications for Facebook Previews
Facebook OG Image Requirements
- Recommended size: 1200 × 630 pixels
- Minimum size: 600 × 315 pixels (small image display)
- Below 600px: No image is shown at all
- Aspect ratio: 1.91:1 (landscape)
- File format: JPG or PNG (JPG preferred for speed)
- Max file size: 8MB (keep under 1MB for performance)
- URL: Must be HTTPS (HTTP images are often blocked)
- Accessibility: No meaningful text in the image (add it to og:description)
Large vs Small Image Format
Facebook uses two image display formats depending on the image's dimensions and the share context:
- Large image format (full-width): Shown when your image is ≥600px wide and meets the aspect ratio. This is the most prominent, attention-grabbing format — and what you should aim for.
- Small image thumbnail (square thumb, left of text): Shown when your image is below 600px or square-ish. Much less visible. Avoid by always using 1200×630.
- No image: If og:image is missing, wrong URL, HTTP only, or the image returns an error — Facebook shows no image. Text-only previews get significantly less engagement.
http://, Facebook's scraper will reject it. Always use https:// in your og:image tag.
How to Fix a Facebook Link Preview That Isn't Showing
Work through these fixes in order. Most problems are solved by steps 1–3.
Step 1: Check Your OG Tags Exist
Right-click your page → View Source. Search for og:image. If you don't see it, your OG tags aren't being output. Common causes: your CMS plugin isn't active, your theme doesn't support OG tags, or the page is a custom type that bypasses the standard template.
Step 2: Verify the Image URL Directly
Copy the URL from your og:image tag and paste it directly into a new browser tab. Does it load? If you get a 404, redirect, or HTTP error, that's your problem. Fix the image URL — make sure it's publicly accessible, HTTPS, and returns a 200 status code.
Step 3: Check Image Dimensions
Use your browser's developer tools (right-click → Inspect → Network tab) to check the image's actual dimensions when it loads. If it's below 600px wide, Facebook won't show a large preview. Regenerate your OG image at 1200×630.
Step 4: Clear Facebook's Cache (Re-Scrape)
If your tags are correct but Facebook still shows old data, you need to force a cache clear. See the section below.
Step 5: Check for Scraper Blocks
If you use Cloudflare, check that the "Bot Fight Mode" or custom firewall rules aren't blocking facebookexternalhit. Also check your robots.txt — it should not disallow Facebookbot or * on the URL being shared.
How to Force Facebook to Re-Scrape Your Page
The Facebook Sharing Debugger (formerly "Open Graph Debugger") is the official tool for clearing Facebook's preview cache and re-scraping your page.
- Go to developers.facebook.com/tools/debug (you need to be logged into Facebook)
- Enter your page URL in the input field
- Click "Debug" — Facebook fetches and displays what it finds in your OG tags, along with any warnings or errors
- If you see outdated info, click "Scrape Again" (appears after first debug). This clears the cache and re-fetches fresh data
- Click "Scrape Again" once more — the first scrape updates the cache; the second shows you the freshly cached result
- Scroll to "Link Preview" to see exactly how your post will appear on Facebook
Common Facebook Preview Errors & Solutions
| Error / Symptom | Most Likely Cause | Fix |
|---|---|---|
| No image shown | og:image missing, HTTP URL, or image <200px | Add HTTPS og:image at 1200×630. Run Sharing Debugger. |
| Wrong / old image | Facebook cache | Use Sharing Debugger → Scrape Again (twice) |
| Wrong title or description | OG tags not present OR cache | Add/fix og:title and og:description, then re-scrape |
| Preview shows for some users but not others | Cache inconsistency across Facebook's CDN | Re-scrape. CDN propagation can take up to 24 hours. |
| "Inferred Property" warning in Debugger | Facebook is guessing your tags because they're missing | Add the missing og: tags explicitly to your <head> |
| Preview shows on mobile but not desktop (or vice versa) | Responsive page serves different <head> to Facebook's scraper | Ensure OG tags are in the same <head> regardless of user-agent |
| Image shows small thumbnail (not full width) | Image width <600px | Use 1200×630 image. Add og:image:width="1200" meta tag. |
| 403 or "Could not retrieve data" in Debugger | Firewall blocking Facebook's scraper IP/user-agent | Whitelist facebookexternalhit in Cloudflare / WAF rules |
| og:image returns redirect (301/302) | Image URL redirects to another URL | Use the final direct URL for og:image (no redirects) |
| JavaScript-rendered page — OG tags not found | Page uses client-side rendering (React/Vue without SSR) | Add OG tags server-side or use pre-rendering / SSR |
JavaScript-Rendered Pages: A Special Case
Facebook's scraper does not execute JavaScript. It reads only the raw HTML returned by your server. If your site uses React, Vue, or Angular with client-side rendering (CSR), your OG tags may not exist in the initial HTML — they're added by JavaScript after page load.
Solutions: (1) Use Server-Side Rendering (SSR) with Next.js, Nuxt.js, or similar. (2) Use a pre-rendering service like Prerender.io. (3) Set OG tags in your framework's document head component that runs server-side. (4) Use a static site generator.
Mobile vs Desktop Facebook Preview Differences
Facebook renders link previews slightly differently across platforms:
Facebook Desktop (Browser)
- Full-width image (large format) when og:image ≥ 600px wide
- Title displayed in large bold text
- Description shown fully (up to ~300 characters)
- og:site_name shown prominently above the title
- Domain shown below site name
Facebook Mobile App (iOS / Android)
- Images slightly cropped differently — horizontal edges may be cut
- Shorter description visible before "...more" truncation (aim for 100 chars)
- Some older Facebook mobile versions show smaller thumbnails even for 1200×630 images — this is a client-side issue, not your tag
- Messenger previews: same OG tags, but smaller display area. Descriptions often hidden.
Facebook Messenger
Messenger uses the same OG tag system but displays previews in a compact format. The image appears as a smaller card thumbnail. The most important element here is the og:image — make sure your image is clear and recognizable even at smaller sizes. Avoid small text in the image.
🔧 Facebook Link Preview Fix Checklist
Work through each item. Check it off as you fix it. Your progress is saved in this browser session.
🏷 OG Tags
🖼 Image
🤖 Scraper Access
🔄 Cache & Verification
🔍 Check Your Link Preview Instantly
Paste any URL into SharePreview to see exactly how it'll look when shared on Facebook, Twitter, LinkedIn, and more — before you post.
Preview My Link →Frequently Asked Questions
How long does it take for Facebook to update a link preview?
After using the Sharing Debugger to re-scrape, the new preview usually appears within seconds to minutes in the Debugger itself. For previously shared posts, the cached preview may persist for existing shares — new shares of the same URL will use the updated scrape. Full CDN propagation can take up to 24 hours.
Can I change the preview image for a Facebook post after it's published?
Yes — sort of. If you shared a link post, Facebook allows the original poster to edit the image directly in the post composer (click the pencil icon on the post). However, this only affects that specific post. Changing your OG tags and re-scraping updates future shares.
Why does my preview work in the Sharing Debugger but not when I share?
The Debugger always fetches fresh data. When you share normally, Facebook may serve a cached version to your audience. Re-scrape via the Debugger, then wait a few minutes before sharing. Also ensure you're not sharing a URL that redirects (the redirected URL may have different OG tags).
Do OG tags affect SEO?
OG tags don't directly influence Google rankings. However, good social previews drive higher click-through rates on shared links, which can indirectly increase traffic and brand visibility. Google reads certain OG tags (like og:image) in some contexts but relies primarily on standard meta tags for search.
What's the difference between og:title and the page <title> tag?
The HTML <title> tag is for browser tabs and search engines. og:title is specifically for social media previews. If og:title is missing, Facebook falls back to <title>. They can have different content — your SEO title might be optimized for keywords while your OG title might be more punchy for social sharing.