Open Graph
Validate Open Graph metadata before sharing a page
Social crawlers read page metadata before a person sees the page. A correct title is useful only when the URL, description, and visible page content all describe the same resource.
Content updated: · Maintainer and corrections
Follow a missing preview from markup to response
Use a test title such as Tea & "Cake", a public canonical URL, and an absolute HTTPS image URL. Generate the tags, then inspect the deployed page source. The title should remain one attribute value after escaping; the image must be available to a crawler without your login cookies.
If the tags are present but the image is absent, open the image URL in a signed-out session and inspect the response status and content type. A redirect to a sign-in page or an HTML error page is not an image response. After correcting the response, ask the platform debugger to fetch again.
| Case | Interpretation and next step |
|---|---|
| Preview shows an old title | Check deployed source first, then the platform cache and its last fetch. |
| Only one language appears | Make the shared URL resolve directly to the intended language and metadata. |
| Duplicate og:title tags | Check both the page and layout; remove competing values at their source. |
Choose the canonical resource first
Start with the public URL you want people to share. Do not point og:url at a preview deployment, a filtered result, or a URL containing private state.
Escape values, not the document
Metadata values may contain quotation marks, ampersands, or non-Latin text. Escape each value before inserting it into markup; do not hand-edit a copied tag string until its structure is unclear.
A local preview is not a crawler fetch
The tool can help produce tags, but it cannot publish them, check image availability, or clear a platform's cache. Deploy the page, then use the relevant platform debugger when a social preview is stale.
<meta property="og:url" content="https://example.test/guides/url-encoding/">Data provenance