Guide
I changed the share image—why is the social preview still old?
When an Open Graph preview stays old after you swap the image, it is usually platform cache still serving a previous scrape. Confirm page meta points at the new stable HTTPS image URL, then use that platform’s debugger / re-scrape tool. This guide does not invent click-by-click admin paths.
Generate a fresh card with Ogmake. Overview: free OG share image. Defaults: default share images for sites. Sizes: social card sizes.
1. Confirm the site actually changed
- - The image file is publicly reachable over HTTPS.
- - CMS / meta fields point at the new URL, not the old file.
- - View page source in a private window and verify the OG image URL.
If the site still advertises the old URL, previews cannot update.
2. Platforms cache cards
Share cards are cached. Chat history may show an old card; scrapers may not have re-fetched yet. That is platform behavior—not proof Ogmake failed to export.
Qualitative fix: open the platform’s link debugger / sharing debugger / re-scrape tool, submit your page URL, and trigger a fresh fetch. Menu names change; follow each platform’s current docs—no invented paths here.
3. URL strategy: stable, version when needed
A stable path (e.g. /og-default.png) is easy to maintain. Overwriting the same filename can still leave caches on the old bytes for a while. For large visual changes, ship a versioned filename (e.g. og-default-2026-09.png), update meta, then re-scrape.
Support: [email protected].
4. Who does what
Ogmake: local title/brand card export. Cache refresh: your hosting + each platform’s scraper tools. Prefer this guide over the short legacy “platform-cache” stub.
FAQ
Still old? Likely cache; confirm meta, then debugger re-scrape.
Fewer surprises? Stable HTTPS; version filenames on big changes.
Ogmake clears cache? No—image generation only.
Image only? Keep title/description meta in sync.