The short answer
Check the exact intended public URL and destination first. If its link card is stale, LinkedIn’s Post Inspector can refresh information for future posts; it does not replace previews already attached to published posts. Reopen a new composer with the exact URL, then verify the actual result after any intended publication. A local mockup is a different check.
What you’ll take away
- A correct page and a correct preview are separate observations.
- Inspector refreshes future previews, not an existing post’s attachment.
- Use the exact intended public URL, including meaningful parameters.
Verify where the exact URL leads
Copy the intended sharing URL from the real report or public page. Open it in the access context your reader will use and read the final destination, title and content. A development preview, expiring signed link, wrong edition or login-only route can look fine in your own session and still be the wrong public destination. Decide whether it should be shared before trying to improve its card.
Tracking parameters are part of the URL you are testing. Check the tagged destination too, especially if the application uses query values to select a language or edition. Do not add arbitrary cache-busting values to a broken link and assume the result is equivalent. Use the separate link-tagging guide to preserve meaningful destination fields.
Inspect what the page offers to a preview
If you control the destination, inspect the public page metadata and image. Open Graph defines title, type, image and canonical object URL, with a description and image properties such as dimensions and alternative text. Match them to the actual content and intended language. These fields describe the offered object; their presence does not guarantee how every service displays it.
Open the referenced image as well as the page. An image that requires your login, points to an old export or carries a different year can explain a mismatch without any defect in the post text. If you do not control the site, give the owner the exact URL, observed card and expected factual correction; do not invent an editor permission or claim you repaired their metadata.
Use the Inspector for the future sharing case
LinkedIn’s help links its Post Inspector: enter the exact shareable URL and inspect the returned information. Review the displayed title and image against the intended destination. Submit only a URL that is appropriate for this external preview service; a confidential signed URL or token is not a harmless substitute for a public link. The tool is not a private-data redaction step.
After a refresh, open a fresh intended composer and paste the same URL. An Inspector result and a composer card are two observations, not interchangeable screenshots. If either remains wrong, keep the case unresolved and record what differs. This guide does not promise a universal cache duration, instant propagation or a successful authenticated Inspector test.
Treat an already published card as a separate decision
LinkedIn explicitly says Inspector changes apply to new posts containing the URL; existing previews remain the same. Its editing help also says changing a URL in a published post does not create a new preview image. Therefore a metadata correction and text edit can leave an old card attached. Check the published card itself before declaring the incident closed.
Choose whether a clear textual correction is sufficient or the misleading attachment requires removal and a reviewed replacement. Consider the error’s consequence rather than chasing a cosmetic refresh. A replacement is a different publication with a separate link and history. Do not promise transferred discussion, recalled emails or deleted screenshots.
| Observed mismatch | Next useful check |
|---|---|
| Destination itself is wrong | Correct destination or edition before sharing |
| Page is right, offered metadata is wrong | Review the site’s actual public metadata and image |
| New composer still shows an old card | Inspect exact URL; compare Inspector and fresh composer |
| Only the old published card is wrong | Make an existing-post correction/replacement decision |
Follow a complete version-and-edition case
Constructed case: a creator intends to share the 2026 recap. The public destination is correct, but its image still says 2025. The creator corrects the offered image, checks the exact URL in Inspector, then checks a new composer. The old published post still shows 2025. That last observation is consistent with the documented boundary; it is not evidence that the refreshed page reverted.
The private record separates intended edition, exact URL, final destination, offered metadata, Inspector observation, new-composer observation and any existing post. Additional cases cover an inaccessible image and a parameter selecting the wrong edition. The original local example metadata are teaching fixtures; they have not been submitted to LinkedIn or used to prove its live rendering.
Sources & product references
Product details reflect the publication date. External features and interfaces may change.
