Why your social share preview shows the wrong image.

The day I renamed a blog post and the share preview disappeared

May 1. Late afternoon. I had been rewriting one of my early posts and the title kept evolving. The piece started life under one working title, went through two more, and finally landed somewhere completely different.

I changed the URL to match the new title. Then I regenerated the social share image (the picture that shows when someone shares the post on Facebook or LinkedIn). Pushed everything live.

Then I did the basic test. Pasted the new URL into a Facebook post composer to see what the preview would look like before sharing.

Blank.

No image. No description. Just the URL sitting there like a broken link, even though the page itself loaded fine in a browser.

I checked the image file. There. I checked the page tags. There. I checked the URL. Live. Everything that was supposed to be on the page was on the page. Facebook just refused to show it.

The cause turned out to be cache. Facebook had seen the URL before. The first time it saw it, the post had a different title and a different image. Facebook stored that version. When I shared the new URL, Facebook served the stale version it already had on file. The new version was sitting on my site, ignored.

This post is the explanation, the fix, and the rule I now follow every time I rename a post or update a featured image.

What is actually going on

When you share a link on Facebook, X, LinkedIn, or any major platform, the platform does not fetch your page fresh every time. It would be expensive at scale. Instead, the first time the platform’s crawler sees a URL, often when someone pastes it into a share composer or publishes a post with it, the platform reads your page, grabs the title, description, and featured image, and stores that information.

After that, every time someone shares the same URL, the platform may show the stored copy instead of fetching the page fresh. The cache can last for days or weeks depending on the platform. Facebook tends to hold onto previews the longest. LinkedIn can usually be refreshed with its Post Inspector. X has no dependable official refresh tool anymore, so you often have to wait or share a slightly different URL.

That works fine 99% of the time. The trap is the 1%, when you change the post.

Three things trigger the trap:

1. You renamed the post URL (the slug)
2. You updated the featured share image
3. You changed the post title or description

Any of those changes only show up to your readers if you tell the platform to refresh its cache. Without that nudge, the old version sticks around for weeks.

The fix is the same on every platform. It takes about thirty seconds per platform.

The Facebook fix

Facebook tends to hold onto previews the longest. It is the cache that bites hardest in practice. Fortunately, Facebook also has the best refresh tool.

Go to developers.facebook.com/tools/debug/. Paste your URL. Click Debug. Then click Scrape Again.

That second click is the one that matters. Debug shows you what Facebook currently has stored for that URL. Scrape Again tells Facebook to throw out the old copy and fetch your page fresh.

The page updates while you watch. The new preview shows in the debugger right away and starts flowing to anyone sharing the link from that point forward. The full propagation to every Facebook server can take up to a day, but the change is live the moment you click.

Repeat for every URL you renamed or updated. Each URL has its own cache. The debugger only refreshes the URL you tell it to.

The LinkedIn fix

LinkedIn’s cache is usually shorter than Facebook’s, but still long enough to ship a broken preview for a stretch of days.

Go to linkedin.com/post-inspector/. Paste your URL. Click Inspect.

That single click does both jobs. It shows you the current preview, and it tells LinkedIn to clear its old cache for that URL. There is no separate “scrape again” button. Inspecting IS the refresh.

One important caveat: LinkedIn’s refresh only affects future shares of that URL. If someone already posted the broken preview before you ran the fix, that specific old post keeps showing the broken preview. The fix is for new shares going forward.

What to do for X (formerly Twitter)

X used to have a Card Validator, but there is no longer a dependable official tool for forcing a fresh scrape the way Facebook and LinkedIn allow.

X’s cache is usually short compared with Facebook’s. Honest advice: post and wait. The preview normally corrects itself once the cache expires.

If you really need a fresh preview on a specific share before then, share the URL with a tiny query string addition at the end, like ?v=2. X treats that as a different URL, so it may fetch the page fresh. The downside is the visible URL now has the extra bit on it, which most people will not love. For most personal brand work, just wait.

When to actually do this

The rule is short. Any time you rename a post’s URL, update its featured share image, or change its title or description after the page has already been shared or crawled anywhere, run the URL through the Facebook debugger and the LinkedIn inspector.

If you changed the slug, refresh both URLs, the old one and the new one. The old URL may already be cached, and if it still redirects somewhere (to the new URL or to a 404 page), that cached preview can keep showing up for anyone who has the old link saved.

If a URL has never been seen by any platform yet, you can skip the step. The cache is usually empty until the platform’s crawler sees the URL for the first time, often when someone pastes it into a share composer or publishes a post with it.

A practical workflow: any time you rename a slug or update a share image, keep a quick list of the URLs that changed that day. When you finish the day’s edits, paste each one into the Facebook debugger and the LinkedIn inspector. Three minutes total. The site stays current to everyone seeing it from the outside.

A bonus rule from the same trap

For social share images, use PNG or JPEG. Do not rely on WebP, SVG, or AVIF for the preview image. Even if some platforms occasionally handle newer formats, PNG and JPEG are the safe formats for share previews everywhere.

This trips people up because I just wrote a separate post about converting your inline blog images to WebP for performance. That move is right for inline blog images, the photos and screenshots inside the body of each post. It is wrong for the share image.

Even if your site uses WebP everywhere else, the share preview image needs to stay PNG or JPEG, ideally at 1200 by 630 pixels.

Inline blog images = WebP. Featured share image = PNG. Two different jobs. Two different formats.

Put This Into Practice

If you renamed posts or updated featured images recently and your social previews are showing the wrong thing, paste this into Claude or ChatGPT.

The prompt walks you through both platforms one URL at a time. No technical detail required. The AI handles the troubleshooting.

Cache is a quiet enemy

Most personal brand site problems are loud. Something breaks, you see it, you fix it. Cache is the opposite. The site looks right to you, because you are looking at the fresh version. The cache is showing your readers the old version. You only find out when someone shares a link and the preview is wrong, or when you happen to check a debugger and see the old data still sitting there.

The rule is the fix. Every slug change. Every featured image update. Three minutes through the two debuggers. The site stays current to the people seeing it from the outside, not just the people building it.

Come build with me.

~ Anthony