Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchIf a social post still displays an old image, changing the file on your website is not enough. The platform may be reusing a previously fetched preview. Refresh the URL in that platform’s own inspector when one exists, verify that your page serves the intended Open Graph metadata, and publish a new post only after the inspector shows the corrected card. For LinkedIn, use Post Inspector; its refresh applies to future posts, not previews already attached to existing posts.
Why an old Open Graph image keeps appearing
When a user shares a URL, a social network crawler fetches the page and stores a preview containing the title, description and image. Later shares can reuse that stored result. Replacing an image at the same filename or editing your page does not necessarily trigger an immediate fetch, so the platform can continue showing its earlier copy.
The cache belongs to the platform displaying the card. Clearing a content-delivery network or image-service cache does not automatically clear LinkedIn, Facebook or another network’s stored preview. Cache duration is not universal, and a refresh that fixes a future share does not rewrite an existing post.
The reliable refresh sequence
- Confirm the page metadata. Inspect the HTML delivered to crawlers and verify that it contains the intended
og:title,og:description,og:urlandog:image. Do not rely only on what a browser renders after JavaScript runs; a crawler may read the server response before client-side code executes. - Check the image URL. Open the exact URL in
og:imageand confirm it returns the new asset, without an authentication wall, redirect loop or temporary error. If you replaced pixels under an unchanged URL, consider publishing the image at a new URL, such as a new filename or a versioned query string. This can prompt a fresh fetch on some services, but it is not a guaranteed purge everywhere. - Run the page URL through the relevant inspector. Submit the complete canonical URL, including its protocol and path. Review the returned title, description and image rather than assuming a successful submission means the card is correct.
- Check the result before sharing again. Create a new post only after the inspector displays the desired image. Existing posts generally retain the preview that was stored when they were published.
- Allow for propagation. If the card is still stale after a correct inspector result, wait for the platform’s documented propagation period and test again. LinkedIn’s troubleshooting guidance says to allow 48 hours after sharing a URL or updating site tags; that is LinkedIn guidance, not a cross-platform promise.
LinkedIn: refresh a URL with Post Inspector
LinkedIn provides the clearest documented workflow. Open linkedin.com/post-inspector, sign in if prompted, enter the page URL and submit it. Inspect the resulting card and correct your page or image URL if the displayed data is wrong.
What the LinkedIn refresh changes
LinkedIn states that changes made through Post Inspector affect the URL’s preview image and information for new posts that include it. The preview for existing posts remains unchanged. Therefore, editing a published LinkedIn post is not a way to replace its old thumbnail; create a new post after the inspector shows the update.
How long to wait
LinkedIn’s general sharing troubleshooting page recommends allowing 48 hours after a URL was shared or its site tags were updated. Treat that as a platform-specific recommendation. There is no established universal cache lifetime that applies to every social network.
Facebook, X and other networks
OG Kit lists Facebook Sharing Debugger as the platform tool for refreshing a URL. Meta’s interface and requirements can change, so verify the current controls when you open the debugger. Submit the page URL, review the fetched image and metadata, then make a new post if the preview is correct. A debugger refresh should not be described as rewriting cards already embedded in published posts.
X (formerly Twitter)
OG Kit lists a Twitter Card Validator. Current availability and workflow were not established here, so do not assume that the listed validator still exists or behaves as described. If X offers a current preview tool in your account or documentation, use it; otherwise, test a new share after confirming your server-rendered tags and image URL.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteNetworks without a confirmed inspector
Each service controls its own crawler and cache. When no current inspector is available, you can try a new page URL or a new image URL, then share that URL. This workaround may cause a refetch, but it does not guarantee that every cache or previously published card will change.
Page URL versus image URL: choose the least disruptive change
| Change | What it can do | Limits |
|---|---|---|
| Run the existing page URL through an official inspector | Requests that the platform refetch its preview and lets you verify the card before a new share. | Availability and effects differ by platform; existing posts can remain unchanged. |
| Publish the image at a new URL | Gives crawlers a different asset address, which can avoid a stale copy at the old address. | Some platforms still reuse the page preview; it is a workaround, not a purge guarantee. |
| Share a versioned page URL | Creates a distinct page address that a crawler may fetch independently. | Splits analytics and canonical-link handling, and can leave multiple URLs indexed. |
Prefer the official inspector first. Change the image URL when the page metadata is correct but the old asset is demonstrably being reused. Use a new page URL only when you accept the SEO, analytics and sharing consequences.
Metadata and crawler checks when the preview is still wrong
Check the actual HTTP response
- Request the page without relying on a logged-in browser session.
- Confirm the response is successful and contains the intended Open Graph tags in the server-rendered HTML.
- Ensure the tags are not blocked by a robots rule, firewall, authentication challenge or geolocation restriction.
- Check that the
og:imageaddress is absolute, publicly reachable and returns an image with the expected content type.
Look for conflicting tags
Multiple og:image tags, a stale canonical URL, or template logic that emits different metadata for bots can make the crawler choose an unexpected asset. Keep one deliberate primary image, place it in the document head, and verify the final response for the exact URL you intend to share.
Confirm redirects and variants
Test both HTTP and HTTPS, trailing-slash and non-trailing-slash forms, and any tracking-free canonical URL. A redirect can lead the crawler to a different document whose tags still reference the old image. Submit the final URL that users and the platform will actually receive.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Common symptoms and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Inspector shows the old image, but your browser shows the new one | The crawler fetched a cached asset, a different URL, or server-rendered HTML with old tags. | Check the raw response and exact og:image URL; publish a new image URL if necessary, then rerun the inspector. |
| Inspector shows the new image, but an existing post is old | The platform preserves the preview captured when that post was created. | Publish a new post; do not expect the old card to change. |
| Only some networks show the update | Each network has independent caches and refresh rules. | Use each network’s confirmed inspector and treat URL versioning as a platform-specific workaround. |
| The image is missing or blank | The crawler cannot retrieve the asset, or the response is not a valid, publicly accessible image. | Remove authentication and blocking rules, verify redirects and content type, and test the image URL from an unauthenticated request. |
| The page never refreshes | Firewall, bot protection, timeout, malformed metadata or a crawler-incompatible response. | Review server logs, allow the platform crawler where appropriate, simplify the HTML response and resubmit after the page is reachable. |
| Different images appear for different URL forms | Canonical, redirect or localization variants contain different tags. | Choose one canonical share URL and make every redirect resolve to metadata containing the intended image. |
Operational practices that prevent stale cards
- Give each major image revision a new filename or explicit version, rather than silently replacing bytes at a long-lived URL.
- Keep Open Graph tags in server-rendered HTML so crawlers do not depend on JavaScript execution.
- After deployment, fetch the page as an unauthenticated client and verify the image response before opening a social inspector.
- Record which URL was inspected and when, especially for scheduled campaigns.
- Preview on the target network before publishing and allow the platform’s stated propagation window.
Or skip the browser setup
For an automated check or a screenshot of the refreshed page, ScreenshotNeo provides a website screenshot API and MCP server. Its clean-shot process accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be disabled. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the page verdict and billing status in headers. An MCP server supplies take_screenshot, get_page_info and capture_pdf tools to Claude, Cursor and other MCP clients.
Use the API documented at screenshotneo.com/docs/:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Rank #4
Python
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
The Free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Sign up free for ScreenshotNeo.
Best Value
FAQ
Will changing only the image file clear every social cache?
No. A platform can retain the response it previously fetched. Use its inspector or a new asset URL as appropriate, and regard URL changes as a workaround rather than a universal purge.
Can I repair the image on a post that is already published?
Usually not. LinkedIn explicitly says Post Inspector changes apply to new posts; existing previews remain as they were.
Is 48 hours the cache lifetime for all platforms?
No. Forty-eight hours is LinkedIn’s troubleshooting guidance for updates, not a cross-platform guarantee.
Free tools Windows power users keep installed
One-click scans. No signup required.
Should I add a query string to the image URL?
A version query can create a new asset URL and may prompt a refetch on some services. Use it only if your image host, CDN and application treat that URL as the intended public asset.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
