Facebook Debugger
Shows how Facebook will crawl and preview a URL, helping you diagnose Open Graph tag issues and force a re-scrape after page changes.
If you have ever updated a page's meta description and image only to see the old preview in a Facebook share, you already know the debugger does not fix the page itself.
Key points
- Paste the URL and click Debug to see exactly what Facebook scraped from your page.
- Click Scrape Again to force a re-fetch after updating Open Graph tags or images.
- Clear your site cache before re-scraping, or the debugger may keep seeing old metadata.
- The tool only re-scrapes your URL; it does not change your page's metadata or content.
- Multiple re-scrapes may be needed before Facebook updates its cached preview.
- Check the debugger after any change to title, description, or image that affects social sharing.
The same URL, two different previews
You update a blog post's title and image, then share the link on Facebook. The old headline and a blurry photo appear. You paste the URL into the Sharing Debugger, click Debug, and see Facebook still holds the old scraped data. You click Scrape Again, clear your site's cache, and re-scrape twice. The preview now shows the new title and a crisp 1200x630 image. The debugger did not change your page; it forced Facebook to re-read the updated metadata.
Three situations where this changes your decision
- After a page update You change the title, meta description, or image. The debugger lets you verify Facebook sees the new data before you share the link publicly.
- When a preview looks wrong A shared link shows an outdated image or wrong description. Use the debugger to check what Facebook scraped and trigger a re-scrape.
- Before launching a campaign You plan to promote a page on Facebook. Run the URL through the debugger first to confirm the preview matches your intended branding.
Four ways it goes wrong
- Assuming it edits your page The debugger only re-scrapes and previews what Facebook reads. You must update the actual Open Graph metadata on your page first.
- Forgetting site caches A plugin or server cache can serve old metadata to the debugger, causing it to show outdated previews even after you update your page. Always clear your site cache before re-scraping to ensure the debugger sees the latest content.
- Expecting instant updates The first re-scrape may not update the preview. Some URLs need multiple attempts before Facebook refreshes its cache.
- Ignoring the interface changes Older tutorials call it the Facebook Debugger or mention Fetch new information. The current tool is the Sharing Debugger with a Scrape Again button.
What to check before you act
- Your Open Graph tags Ensure og:title, og:description, and og:image are present and correct in your page's
<head>. The debugger will show what it found. - Your site cache Clear any caching layer — plugin, CDN, or server — that might serve stale metadata to the scraper.
- Your image dimensions Facebook recommends a 1200x630 pixel image. Smaller or oddly sized images may be cropped or ignored in the preview.
- Your SEO and analytics setup Confirm that your meta description and open graph tags support your SEO optimisation goals, and check Hotjar sessions for how users behave after clicking the shared link.
Common questions
How do you use the Facebook Debugger?
Go to the Sharing Debugger on Meta for Developers, paste your URL, and click Debug. The tool shows what Facebook scraped and a preview.
Why does the debugger show old data even after you update your page?
Your site cache or Facebook's cache may still hold the old version. Clear your cache and click Scrape Again, possibly multiple times.
Does the debugger change your page's metadata?
No. It only re-scrapes and displays what Facebook reads. You must update the actual Open Graph tags on your page.
Sources
- Meta for Developers — Sharing Debugger The official tool for debugging and re-scraping URLs.
- Meta Open Graph documentation Covers Open Graph tag requirements and best practices.