Published: Last updated:
TL;DR
A website can look correct in your browser but show an old logo, an unrelated photograph or a vague title when someone shares it. The sharing service usually creates its preview from information it retrieves from the page. Open Graph metadata helps describe which content should represent that link.
For a small business, the immediate benefit is clarity. Someone sharing your service page should give the recipient a sensible introduction to the service, rather than a confusing snapshot of the website. That matters even when the link travels through a private conversation rather than a public social post.
Give every important page its own preview
Imagine a Wakefield joiner sends a fitted wardrobe page to a potential customer. A preview showing a kitchen photograph and “Welcome to our website” makes the link less useful. A wardrobe image, a descriptive title and a short explanation help the recipient understand what they are opening.
Check the homepage, main service pages, important articles and project examples individually. Repeating the same generic image everywhere can be an acceptable starting point, but a page-specific image often gives better context. Use photographs you own or have permission to use, and avoid presenting stock photography as a completed client project.
Know what the metadata can describe
The Open Graph specification defines four required properties: a title, an object type, an image and a canonical URL. A description and site name can provide additional context. The metadata belongs in the page’s HTML head and should agree with what the visitor actually sees.
You do not need to learn those tags to manage a website. In many content systems, your developer or existing SEO settings provide fields for social titles and images. Ask where those settings live and which value takes precedence when both the template and a plugin supply metadata.
A social title can be shorter than the article heading without changing its meaning. Choose wording that remains understandable if a platform truncates it. Keep essential details out of the edges of an image because previews can crop differently across services.
Test the public URL, not the editor
Save the page, then inspect the address a customer will actually receive. The image must be publicly reachable. A preview crawler cannot necessarily access a file behind a login, a staging password or a protection rule, even if the photograph loads for you.
Check that the URL resolves to the intended page and that its preview does not refer to a staging domain. Ask your developer to inspect the page’s generated metadata if the settings look right but sharing still fails. Duplicate tags or an unexpected template fallback are possible causes worth investigating.
Sharing services can retain previously collected information. After a correction, use the relevant platform’s inspection or debugging tool where available, then test a new share. A cached preview in an older message may remain unchanged. Avoid repeatedly rewriting the page title simply because one old message still displays the previous version.
What the symptom suggests
| What you see | First investigation | | --- | --- | | The same wrong preview on several platforms | Check the page's generated metadata, duplicate tags and the public image URL | | A correct preview on one platform but an old one on another | Check the affected platform's cache and whether its crawler can access the page and image | | The correct image with important text cropped | Adjust the composition and keep essential information in the page text | | Only an older message shows the wrong preview | Test a fresh share before changing the page again |
These are starting points, not proof of a cause. When asking for help, send the page URL, the sharing platform, what you expected, what appeared and when you tested it. A screenshot can help identify a crop or cached image without access to private conversations.
Keep the result in perspective
A correct preview helps people recognise and understand your link. It does not guarantee more enquiries or higher Google rankings. Open Graph describes shared content; it is not a substitute for useful page copy, accessible design or accurate business information.
Include preview checks in the handover for a new website or redesign. You should know who maintains the images, where they are stored and how to check a page after updating it. If your previews remain wrong, send the affected links when you get in touch so the problem can be scoped from the actual pages.
