Open Graph tags tell social platforms which title, image and description to show when somebody shares a page. Correct configuration gives you more control over the preview and reduces the risk of unrelated text or imagery being selected.
What is Open Graph?
Open Graph is a standardised protocol for describing a web page to services that display shared links. The implementation of it is quite technical, but it’s important to understand what it is and how it works even if you’re not a programmer.
When you share an external site on Facebook, it will pre-populate some fields, like the title, a blurb and an image to go with it, if applicable. If that site hasn’t implemented Open Graph, Facebook will make a best-guess as to what content to pull from the site for those fields, but it could be wildly off. This can produce a misleading preview; for example, if a visitor wants to share one of your products on your e-commerce site, you probably want the primary product image to be pulled across and displayed on social media. Without Open Graph, it could end up pulling through a completely unrelated image from your site instead.
How do I implement Open Graph?
Open Graph is a set of meta tags that sit in the code of your website and specify certain information, such as what the title, blurb and image should be if the page is shared on compatible social media, such as Facebook, X and LinkedIn. You can’t see the tags when you browse the page, but it allows you more control over what information is displayed when a page is shared.
If you use WordPress, check whether your theme or an existing SEO plugin already generates Open Graph tags. WordPress alone is not proof that the desired metadata is present. If not, you’ll have to get in touch with a software developer to help you implement it.
Is it worth supporting Open Graph?
Accurate previews help people recognise what a link offers before opening it. They do not guarantee clicks, referrals or better rankings. The benefit is a more consistent presentation, provided someone maintains the metadata when the page changes. Each platform still decides how to display the information.
Check the preview before publication
Set at least the title, description, canonical URL, content type and a suitable image. Test the preview with Meta’s Sharing Debugger. A cache may retain an older version, so request a fresh scrape after changes and check how other platforms display the link as well.
Understand the main fields
The Open Graph protocol defines core properties for the title, type, image and URL. A description is also useful for explaining the page. Keep the values specific to the individual article or product rather than reusing a generic homepage message everywhere.
The title should match the page’s promise. The image should depict the subject rather than an unrelated logo or banner. The URL should identify the intended page consistently. If the site has several languages, check that the preview text and destination belong to the same version.
Choose one place to manage the output
On a WordPress site, a theme and an SEO plugin can both produce metadata. Yoast’s guidance warns that duplicate Open Graph output can lead to incorrect titles or images. Inspect the generated page before adding another plugin; an additional tool may duplicate an existing function rather than solve the problem.
Assign responsibility for the fields. An editor can choose a relevant title and image, while a developer checks that the template outputs them correctly. Agree which value should be used when an editor leaves a field empty. A sensible fallback makes omissions less disruptive, but it still needs review.
Diagnose a wrong preview in order
First confirm that you are testing the final public address, not a draft or a different language version. Then check that the page’s current metadata contains the intended values. If the source itself is wrong, refreshing a platform cache cannot fix the underlying problem.
Next check access to the image. It should load without a private login and should not point to a temporary file. Ask the person maintaining the site to investigate crawler access or redirects if the page looks correct to you but cannot be read by the sharing service.
After correcting the source, use the platform’s inspection tool to request a fresh analysis where available. An old preview may be cached separately from your website. Keep a note of the tested address and result so the team does not keep changing correct fields in response to an old copy.
Make preview checking part of publication
Before promoting a page, review the title, image crop and destination together. For a product, ensure the visual matches the variant described. For an event, avoid putting an old date into a reusable image. Do not make the preview promise information that the page does not contain.
Check again after a redesign, language change or replacement of the featured image. Keep a short record of important pages and who owns their updates. The aim is not constant tweaking: it is to catch mismatches that would confuse a person deciding whether to follow the link.
