How to check social link previews before sharing your page
Review titles, descriptions, images, public access, and cached previews without confusing the preview with the landing experience.
The useful takeaway
Verify both the shared preview and the page it opens, using the exact public URL.
A social link preview is often the first thing someone sees of your page. An old title, blank image, or misleading description can create confusion before the visitor even clicks. But the preview is only a representation assembled by the sharing service; it is not the page itself and may update on a different schedule.
Check previews as part of publishing, especially when a campaign changes the page's purpose. Use the exact public URL, verify that the metadata describes the current destination, and inspect the page after opening it. A polished preview should introduce a useful experience rather than conceal an unfinished one.
Understand the metadata layer
The Open Graph protocol defines properties commonly used to describe a shared page, including its title, type, image, and URL. Individual services may use additional rules or fallbacks. Treat those properties as structured descriptions of the destination, not as a guarantee that every app will render the same card.
Keep the title specific and the description informative. The image should remain understandable when cropped or displayed small. Avoid putting essential offer details only inside an image, because the preview may not display it as expected. The page itself should carry the full current information in accessible text that visitors can read after opening the link.
Verify public access to the assets
Open the public page and preview image while signed out. A file that loads in the editor may require authentication or use an expiring address. Check that the image URL points to the intended asset and that the page does not redirect a preview request to a login screen or unrelated location.
Technical response behavior matters here. Google's HTTP-status reference is useful background for understanding response codes, though each social service has its own fetching behavior. A normal browser view is necessary evidence, but it does not prove every preview crawler can retrieve the same metadata and assets.
Use an illustrative preview checklist
Imagine a hypothetical workshop page moving from a summer event to an autumn event. The body now shows October dates, but the shared image still says Summer registration. The review should compare page title, description, image text, visible heading, event dates, and destination action. Any mismatch creates an avoidable expectation problem.
The team replaces the old asset, updates the metadata, and checks the exact public route in the sharing environments it uses. It records the artwork version and verification date. This illustrative process is more reliable than changing a filename and assuming every previously generated preview will immediately refresh across all services and conversations.
Distinguish caching from a failed update
A service may continue showing a previously fetched preview after the underlying page changes. First confirm that the current public metadata and assets are correct. Then use the platform's official inspection or refresh mechanism if one is available for that service. Do not invent a universal refresh procedure; the available tools and behavior differ.
Avoid repeatedly changing unrelated page settings while waiting for a cached card to update. Keep a record of the current correct state and the remaining stale surface. If the campaign is time-sensitive, a newly published destination may be an option, but consider the maintenance and historical-link implications before creating duplicate pages solely to force a visual change.
Check the promise after the click
Open the preview as a visitor and confirm that the landing page fulfills its message. Check mobile readability, the main action, destination availability, and any free-to-paid boundary. A preview advertising a free resource should not lead unexpectedly to a different paid offer without a clear explanation.
Save a simple publication record with the URL, metadata reviewed, image version, and platforms checked. Revisit it after major content changes or migrations. Preview quality is part of a larger chain of trust: the social post, preview card, landing page, and final action should all describe a coherent task the visitor can actually complete.
Sources & further reading
References for the principles and technical details in this guide.
Found something that needs correcting? Send us a correction.