Facebook Sharing Debugger is the tool Meta provides for checking how a link will look when it is shared on Facebook. You paste a page address into it, and it shows the title, description, and image that Facebook has stored for that page. It also shows the tags Facebook read from the page, plus any warnings about what is missing. When a preview looks wrong, this tool is the first place to look, because it shows what Facebook sees rather than what you see in your own browser.
The most common surprise is that a preview does not update when you fix the page. Facebook stores a copy of the preview the first time a link is shared, and later shares reuse that stored copy. Changing the page alone does not change the stored preview, so you need to ask Facebook to read the page again. That is exactly what the debugger is for, and the rest of this guide walks through it step by step.
Contents
- Facebook Sharing Debugger: what it actually does
- Why your preview image is missing or wrong
- Set the four Open Graph tags first
- Refresh the preview with Scrape Again
- When the debugger still shows the old preview
- What not to do with link previews
- Related reads
Facebook Sharing Debugger: what it actually does
Facebook Sharing Debugger lives in the Meta for Developers tools, and you need to be signed in to a Facebook account to use it. You enter the full page address, including the secure prefix, and click Debug. The tool then shows a link preview, the Open Graph tags it scraped from the page, and the time it last scraped that address. If the page has no usable tags, the debugger says so plainly, which saves you from guessing.
The debugger also matters because Facebook’s crawler only reads what it can reach. A page behind a login screen, a page that blocks the crawler, or a page that builds its tags with JavaScript after loading may show missing or guessed data in the debugger. Fix the page, then return to the debugger to confirm the fix.
Why your preview image is missing or wrong
A missing preview image usually has one of a few causes, and they are worth checking in order. The page may have no image tag at all, so Facebook picks whatever image it can find, or none. The image may be too small, so Facebook crops it badly or drops it in favour of something else.
The image address may be relative rather than absolute, so the crawler cannot resolve it. Or the image may have changed while the address stayed the same, so Facebook keeps serving the old stored copy.
Image size deserves special attention because it is the easiest cause to fix. Meta recommends a large image for link previews, commonly described as 1200 pixels wide by 630 pixels tall, which is about a 1.91 to 1 ratio. Smaller images can still work, but they risk awkward cropping on different screen sizes. Use one clear image that reads well at small sizes, and avoid text-heavy graphics that turn to mush in a feed.
Set the four Open Graph tags first
Open Graph tags are short lines of markup in the head section of a page, and four of them carry the preview. The og:title tag sets the preview title, og:description sets the short text beneath it, og:image sets the preview image address, and og:url sets the canonical address of the page. Most WordPress sites set these through an SEO plugin or a social sharing plugin, so check your plugin settings before editing any code. If you edit code directly, keep the tags near the top of the head section and use absolute addresses that start with the secure prefix.
Keep the title and description honest and specific to the page. Once the tags are in place, test them in the debugger before sharing the link anywhere.
Refresh the preview with Scrape Again
Refresh the preview with Scrape Again, which is the button that tells Facebook to discard its stored copy and read the page fresh. After fixing your tags, open the debugger, paste the address, click Debug, and then click Scrape Again. The preview should rebuild from your current tags, and the scraped time should update to the present moment. If the old image persists, click Scrape Again once more, since a single scrape does not always clear every cached layer.
One honest limit matters here: refreshing the cache changes future shares, not posts that are already live. A post published with the old preview keeps that preview, because Facebook stored it at publish time. For a live post with a broken preview, the practical options are to leave it, delete and repost it with the fresh preview, or accept the old one. Check the preview in the debugger before you publish, and this problem rarely appears at all.
When the debugger still shows the old preview
When the debugger still shows the old preview after scraping again, check whether the image address itself changed. If you replaced an image but kept the same file address, Facebook may keep serving the old file from its image cache. The reliable fix is to give the new image a new file address, update the og:image tag to point to it, and scrape again. Do not delete the old image file right away, because existing shares may still point to it.
What not to do with link previews
Do not chase a preview problem by sharing the same link repeatedly to see if it fixes itself. Repeated shares do not force a refresh, and they spam your audience while the stored preview stays unchanged. Do not stuff the description with keywords or promises the page does not keep, since readers judge the page by the preview and leave quickly when it misleads them.
Related reads
- How to Secure a WordPress Site — security settings that block crawlers can also break previews, so keep both in view.
- How to Load Your Site Fastly — a fast page gives the crawler less reason to time out before reading your tags.