Open Graph and Social Sharing

Information checked: 21 July 2026.

Open Graph metadata gives social and messaging services structured information for building a link preview. It does not guarantee that every platform will display the same card, but it gives the website a controlled and testable source for the title, image, URL and page type.

In brief: Generate one consistent set of page-level metadata from the same source as the visible article title, summary, canonical URL and featured image. Avoid multiple plugins writing conflicting tags.

Core Open Graph fields

Minimum useful metadata

Property	Purpose	Editorial rule
og:title	Preview title	Match the page topic without clickbait
og:type	Object type	Use a type that reflects the visible page
og:url	Permanent identity	Use the final canonical HTTPS URL
og:image	Representative image	Use an absolute, publicly accessible URL
og:description	Optional summary	Explain the value of the page accurately

Keep metadata, canonical and visible content aligned

The share title should not promise something the article does not provide. The Open Graph URL should normally match the canonical URL, and the image should represent the page rather than a generic logo used across hundreds of unrelated articles. When an article is renamed or moved, update the metadata at the same time as the visible heading, canonical and redirect.

Prepare reliable images

Use an image that remains readable when cropped or reduced. Keep essential text away from the edges, avoid tiny screenshots and provide appropriate image dimensions where the implementation supports them. The file should load over HTTPS, return a successful response without authentication and remain available to crawlers that do not execute the full page application.

Do not generate a unique decorative image merely to fill a metadata field. A consistent category illustration or a genuine diagram can be better than low-value AI artwork. The image also needs a documented owner and replacement process if licensing or branding changes.

Prevent duplicate and conflicting tags

A theme, SEO plugin, social plugin and custom template can all attempt to write Open Graph metadata. The browser then receives several versions of the same property and platforms may choose an unexpected one. Assign one component as the metadata owner and remove the overlapping output from the others.

Test the published URL, not only the draft

Inspect the page source after publication and verify that each property appears once with the final URL. Then test the public URL using the relevant platform's current sharing or debugging tool where available. Some platforms cache previews, so an old card may persist until the URL is re-scraped or the cache expires.

Acceptance check

• One set of Open Graph tags is present in the document head.
• The title and description match the visible page.
• The Open Graph URL matches the intended canonical URL.
• The image loads publicly over HTTPS and remains legible when reduced.
• Moved pages update metadata and redirect from the old URL.
• A real shared-link test has been completed on representative page types.

Next practical step

Choose one metadata owner in the future engine, define the page fields it will use and test at least the homepage, one hub, one article and one comparison page after import.

Sources and date checked

Protocol information was checked against the primary Open Graph specification. Platform rendering rules can change and should be tested on the live URL. Date checked: 21 July 2026.

• The Open Graph protocol
• Google Search Central: canonical URL guidance