Facebook Debugger

How it works

To use the tool, paste a URL into the Sharing Debugger on Meta for Developers and click Debug. Facebook's crawler fetches the page and displays the scraped data, including the title, meta description, image, and other Open Graph properties. It also shows a preview of how the link will appear in a Facebook post, along with any warnings about missing or malformed tags.

If the page's metadata has been updated, click Scrape Again to prompt Facebook to re-fetch the URL. The interface distinguishes between URLs not previously shared (Fetch new information) and those already shared (Scrape Again). However, the debugger only reads what is publicly accessible; it does not change the page itself. Site caches, plugin caches, or CDN caches can cause the debugger to see old metadata, so clearing those before re-scraping is recommended. Multiple scrape attempts may be needed before the preview updates, as Facebook's caching layer does not always refresh instantly.

Why it matters

When Facebook shares a link with an outdated image, wrong title, or missing description, users are less likely to click. A missing or incorrect og:image can cause Facebook to display a generic placeholder, reducing the likelihood of clicks. Consistent branded previews build trust and can increase traffic from social media. For SEO practitioners, verifying Open Graph tags is a fundamental part of facebook seo, as correct social previews can improve click-through rates from shares and maintain brand consistency across platforms.

The tool also helps diagnose issues such as missing og:title or og:description, which can cause Facebook to fall back to generic text. Because Facebook's crawler may cache data for an unknown period, the debugger provides a way to force a refresh after content changes. This is especially important for pages that are frequently shared, such as blog posts, product pages, or landing pages. Without the debugger, you would have to wait for Facebook to naturally re-crawl the URL, which could take days.

Where it changes your decision

• When Facebook shows an outdated image, title, or description after a page update: use the debugger to verify the current scraped data and click Scrape Again to force a refresh. This is common after changing a blog post's featured image or updating a product title.
• When you have added or modified Open Graph tags: paste the URL into the debugger to confirm the tags are read correctly and the preview matches expectations. For example, after adding og:image or adjusting the meta description, the debugger confirms the new values are being picked up.
• When site caching or plugin caching may be serving old metadata: clear the cache on your site, then use the debugger to re-scrape and check that the latest version is being used. This step is often overlooked but can resolve persistent preview issues.

What it is not

• It is not a tool that modifies your page: the debugger only re-scrapes and previews what Facebook reads from the URL; you must update the actual metadata on your page. Some users mistakenly think clicking Scrape Again will fix the preview without editing the page.
• It is not a substitute for updating Open Graph metadata: clicking Scrape Again without first updating the tags on your page will not change the preview. The debugger reflects what is currently published, not what you intend to publish.
• It is not immune to caching: site caches, plugin caches, or CDN caches can cause the debugger to keep seeing old metadata; clearing those caches is often necessary before re-scraping.
• It does not guarantee instant updates: the first re-scrape may not always update the preview immediately; multiple attempts may be required, and Facebook's internal caching can delay the new preview from appearing in actual shares.