Facebook Open Graph (OG) Preview & Debugger
Preview how your link unfurls on Facebook and check the Open Graph tags Facebook reads. Catches missing og:image, relative URLs, WebP issues, and missing og:image:width/height before you share.
Facebook Open Graph Preview & Debugger
Facebook builds its link preview entirely from Open Graph (og:) tags — og:image, og:title, og:description, and og:url. It recommends a 1200 × 630 image (1.91:1) under 8MB, and it caches each preview for roughly a week.
Paste your URL to see the unfurled card and the exact og: tags Facebook reads. When you change an image, force Facebook to re-fetch your page with the official Sharing Debugger's "Scrape Again" button rather than waiting out the cache.
Frequently asked questions
How do I force Facebook to refresh a cached preview image?
Open the Facebook Sharing Debugger at developers.facebook.com/tools/debug, paste your URL, and click "Scrape Again." This forces Facebook to re-fetch your page and update the cached preview immediately, rather than waiting out the roughly 7-day cache. If Scrape Again keeps the old image, it usually means Facebook is still reading a cached or stale og:image URL.
What's the recommended OG image size for Facebook?
Facebook recommends 1200 × 630 pixels (1.91:1) for a large, high-resolution link image, with a maximum file size of 8MB. Images smaller than 600 × 315 will display as a small thumbnail or no image. Stick to JPG or PNG — WebP often fails to render in Facebook previews.
Why won't Facebook pull my image even though the tags are correct?
Frequent culprits are a relative og:image URL (Facebook requires an absolute https:// URL), the image being too large or in WebP, or your og: tags being rendered by JavaScript that Facebook's crawler doesn't execute. The debugger sometimes also shows a blank image when it scraped before your image was deployed — click Scrape Again after deploying, and read the debugger's error messages, which name the exact problem.
Should I include og:image:width and og:image:height tags?
Yes — adding og:image:width (1200) and og:image:height (630) tells Facebook the image dimensions up front, so it can render the large card on the first scrape instead of initially showing a small or blank image. Without them, Facebook has to fetch and measure the image, which sometimes causes the image to be missing on the very first share until it re-scrapes.
Why does my Facebook share image look blurry?
A blurry preview usually means the source image is below 1200 × 630 and Facebook is upscaling it, or the file is being heavily compressed. Use a sharp 1200 × 630 (or 2×: 1600 × 900) image and keep it under 8MB. If it looks fine in the debugger's raw image but blurry in the card, re-scrape — Facebook may have cached an earlier low-res version.
Next step
Previews are one page. Search performance is every page.
Connect Google Search Console to your AI agent with Sequel and ask which pages are actually earning clicks, which rank but get ignored, and what changed this week.
Ask your agent
“Which of my pages rank in the top 10 but get almost no clicks?”