How to Fix an Outdated Open Graph Image

Social platforms cache link previews so they do not have to visit your site every time someone shares the same page. That is useful until you replace an Open Graph image and Slack or LinkedIn keeps showing the old one.

The steps below are for a preview that works but is out of date. If the preview has no image at all, start with How to Fix a Missing Open Graph Image.

TL;DR: Replace an Outdated Open Graph Image

1. Read the source of the live page and confirm that og:image points to the image you expect.
2. Publish the replacement image at a new URL instead of overwriting the file at the old URL.
3. Update og:image, deploy the page and verify the new tag without relying on your browser session.
4. Run the page through the platform's preview debugger so it fetches the metadata again.
5. Test with a new draft or message. Existing posts may keep the preview they had when they were created.

Step 1: Confirm Which Image the Page Publishes

Open the source of the public page and search for every og:image tag. Make sure the first one contains the current image URL:

<meta property="og:image" content="https://example.com/images/balcony-tomatoes.png">

Use View Page Source, not only the browser's Elements panel. You want to see the HTML returned by the server before JavaScript changes it.

There are a few faster ways to grab the current image URL:

1. Open the browser console and run:

   document.querySelector('meta[property="og:image"]')?.content
   

   This returns the first og:image value, which is also the one you should check first when the page declares several images.

2. Use a browser extension that displays Open Graph or social-preview metadata.

3. Paste the page URL into a third-party checker such as the Social Card Previewer. It shows the URL alongside the image it was able to load.

These are convenient ways to inspect a page, but the console and some extensions read the live DOM. Check View Page Source or the raw response as well so you know the new tag was present before JavaScript ran.

The same check works from a terminal:

curl -L -sS https://example.com/guides/balcony-tomatoes \
  | grep -i 'og:image'

If the old URL is still there, the social platform is doing exactly what the page asked. Update the metadata and deploy it before trying to clear any caches.

If the new URL is present alongside an older one, remove the unintended duplicate or put the preferred image first. The Open Graph protocol gives the first image preference when a page declares more than one.

Step 2: Give the Replacement Image a New URL

Overwriting balcony-tomatoes.png with new bytes does not guarantee that every copy of the old image disappears. Your CDN may have it cached, and the social platform may have downloaded its own copy.

Publish the replacement with a version in the filename or path:

https://example.com/images/balcony-tomatoes-v2.png

Then update the tag:

<meta property="og:image" content="https://example.com/images/balcony-tomatoes-v2.png">

A query string such as balcony-tomatoes.png?v=2 can work, but a new path is easier to reason about. CDNs and social platforms do not all handle query strings the same way, and some configurations ignore them when choosing a cache key.

If the image comes from a dynamic renderer, you do not have to invent filenames forever. Use a stable public route that understands a content version or has an explicit refresh policy. OG Images for Every Page explains how HCTI separates page metadata, rendered-image caching and refreshes.

Step 3: Verify the Deployed Tag and Image

After deploying, repeat the source check from Step 1. It is common to update an image in a CMS but forget that the page metadata comes from a separate field, template or SEO plugin.

Open the new image URL in a private window too. This makes sure the file is public and that you are not looking at a copy from your signed-in browser session.

You can check the response directly:

curl -L -sS -o /dev/null -D - \
  https://example.com/images/balcony-tomatoes-v2.png

Confirm that the final response is successful and its Content-Type is an image. If your CDN still returns the old bytes at the new URL, clear or correct that cache before asking social platforms to refresh theirs.

Step 4: Refresh the Platform’s Copy

The page and image can both be correct while the link preview remains stale. At that point, use the platform's own tool:

• Facebook Sharing Debugger
• LinkedIn Post Inspector

Enter the exact page URL people will share. Watch for differences such as www, a trailing slash or a redirected campaign URL. Preview caches may treat those as separate addresses even when they end up on the same page.

Adding a query string to the page URL can be a useful diagnostic. If ?preview=2 shows the new image while the plain URL shows the old one, caching is almost certainly involved. It is not a great permanent fix because platforms may normalize the URL or use the page's og:url as its canonical identity.

Trying a different account is less useful. These caches are generally shared by the platform, not kept separately for each user. A second account may create a fresh post, but it does not necessarily force a fresh fetch.

Step 5: Test a New Share

Create a new draft, message or post after the debugger shows the new image. Do not use an existing post as the test.

LinkedIn specifically notes that Post Inspector refreshes the preview for new posts. Anything already published keeps the image and text it had before the refresh. Other apps may behave similarly.

If a new draft still shows the old image, give the platform some time before making another round of changes. Preview crawlers are intentionally conservative about repeatedly fetching the same sites, and their cache timing is not always documented.

Frequently Asked Questions

Why Is LinkedIn Still Showing My Old Open Graph Image?

First check LinkedIn Post Inspector. If it shows the new image, create a new draft or post to test it. Existing LinkedIn posts keep their original preview after a refresh.

Should I Replace the Existing Image or Change Its URL?

Change the URL. Replacing the file in place leaves both CDN and social-platform caches free to serve the old bytes. A new filename or versioned path is clearer.

Will Adding a Query String Refresh an Open Graph Image?

Sometimes. It is useful for confirming that a cache is involved, but it should not be the main fix. Publish the image at a new path, update og:image and use the platform's debugger.

Will Sharing From a Different Account Clear the Cache?

Usually not. Link-preview caches are generally platform-wide rather than tied to one account. Test with a new post after refreshing the URL, but do not expect the account change itself to trigger another crawl.

How Long Does an Open Graph Image Stay Cached?

There is no single cache duration across platforms. Their refresh tools are the quickest way to request another crawl. Even after a refresh, an existing post may keep its original preview.