Distinguish the page from its preview
A shared link can open the correct article while displaying an old title, a generic logo or no image in a messaging app. Start by recording the exact URL used, including redirects, and the destination where the problem appeared. Preserve a screenshot of that result privately if it helps comparison.
The Open Graph protocol defines title, type, image and URL properties for describing an object. It also offers description and other optional metadata. Those fields describe what the page supplies; they do not establish how every service will display it or when a service refreshes its own copy. [1]
Inspect what the published response contains
Open the public page response or source and find the relevant metadata in the document head. Compare its values with the article actually visible on the page. MDN explains the meta element's role in document metadata and its use of attributes to express different kinds of information. Inspect the generated result, not only the editor's form fields. [2]
Look for duplicate or conflicting values created by a template, plugin or old custom-code block. Record the final page URL after redirects and the intended permanent public URL. A preview domain or local address is not a suitable production identity. Keep unpublished previews under their existing access and indexing controls.
Worked example: the article is correct but the image is not
In an invented launch, /guide/ shows the new article title, but its image metadata still points to /media/old-logo.png. The old logo loads successfully. This is a content-mapping failure, not evidence that the destination app cannot load images. Update the article's intended image mapping and inspect the generated page again.
A second invented case points to /media/guide-card.png, which returns an HTML error page. Here the metadata text looks correct but the image resource is wrong. Fetch the image URL independently, check the response and open the actual file. Repeatedly changing the article title would not address this failure.
Choose an image that survives a small preview
Use an image you own or are authorized to publish. Avoid tiny body text, account screenshots containing private data and claims that appear only in the image. Review a small crop of the image so its main subject remains understandable. This is an editorial readability check, not a platform dimension specification.
Open Graph supports structured image details such as dimensions and alternative text. Supply accurate values where your publishing system supports them. For a platform with additional card requirements, consult that platform's current official instructions before relying on a particular crop, size or fallback behavior. [1]
Retest the destination and keep the scope honest
After correcting the public page and image, use the destination's supported preview or inspection mechanism if one is available. Otherwise, perform a limited authorized sharing test. Record the exact destination and timestamp. Do not publish repeated promotional posts simply to see whether a cached image changes.
The worksheet separates source metadata, image response and observed destination behavior. Close a source defect when the generated page and image are correct; close the platform observation only when that destination shows the intended result. This documentation-based guide does not claim live tests of every social network. If a platform retains an older preview and its refresh behavior is undocumented, keep that uncertainty explicit rather than promising an expiry time.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Open Graph protocol: The Open Graph protocol Accessed 2026-09-14
- MDN Web Docs: The meta HTML metadata element Accessed 2026-09-14
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.