Why Is the Wrong Image Showing When I Share My Website?
Trace an incorrect shared-link image through Open Graph metadata, asset access and platform caching without confusing it with Google's favicon.
Part of our guide: How Can I Make My Website Look More Professional?
When a shared website link shows the wrong image, check the preview metadata for that exact page. The visible hero image and the image selected for a social card are not necessarily the same thing.
Different sharing services may interpret and cache previews differently. Correcting the website is one step; confirming the refreshed preview on the intended service is another.
Identify the affected preview
Record the full shared URL, the app or service, the wrong image and the date. Note whether the problem affects one page or every page.
A homepage default appearing on a service page often suggests that page-specific metadata is missing or overridden. An old image on only one service may also involve its stored preview.
Do not confuse this with a missing Google favicon. A tiny search icon and a large shared-link card use different mechanisms.
Inspect the actual page metadata
The Open Graph protocol defines properties including title, type, URL and image, with additional image details such as dimensions and descriptive alt text.
Ask the developer to inspect the metadata delivered for the public URL. Check for duplicate or conflicting image declarations from a theme, SEO extension or custom component.
A correct setting in an editor is not enough if another component replaces it in the generated page.
Open the referenced asset directly
Confirm that the declared image URL returns the intended picture without authentication or an access challenge. Check its format and dimensions against the target service’s current documented requirements.
Avoid assuming that a local file or private preview can be fetched by an external crawler. A developer’s browser may have permissions that the sharing service does not.
If the asset moved, inspect redirects and the final image response rather than stopping at the old filename.
Compare source and cached presentation
| Observation | Next check |
|---|---|
| Page declares the wrong image | Correct the responsible metadata source |
| Page declares the right image but asset fails | Repair public asset delivery |
| Source and asset are correct, one service is old | Inspect that service’s preview refresh process |
| Every page uses one generic card | Review page-specific metadata generation |
This is a diagnostic framework, not a promise that every platform offers a cache-clearing button.
Use the intended service’s official inspection or refresh mechanism where available. Do not repeatedly change page addresses just to escape a stale card.
Choose a preview that remains meaningful when cropped
Keep the important subject inside a safe central area and test the actual card presentation. Small text baked into artwork can become unreadable.
For a fictional roof-repair business, a clear completed project image may communicate more than a crowded collage of logos, tiny captions and telephone numbers.
The professional-looking website guide provides broader visual context. Metadata should represent the page honestly, not advertise an unrelated service because its photograph is more attractive.
Check the wording at the same time
Review the preview title and description against the page’s current content. An accurate picture beside an outdated offer is still misleading.
Our page-title and description guide helps with concise wording, although social properties and search metadata remain separate fields.
Keep one clear owner for each output so later content edits update the appropriate preview.
Record two completion states
First record that the public metadata and asset are correct. Then record the service and date on which the refreshed preview was observed.
If an old card persists elsewhere, leave that limitation explicit. A successful test on one messaging app is not evidence that every social platform has refreshed its stored version.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
