Social sharing metadata can determine whether a page appears polished, useful, and trustworthy when someone posts its URL. This checklist explains how to use an Open Graph debugger, social media preview checker, crawler, validator, or CMS plugin to inspect titles, descriptions, images, canonical URLs, and locale settings before publishing.
Overview
A social preview is assembled from metadata in a page's <head>, together with the page response, image availability, and the rules used by the platform fetching the URL. A browser-based preview tool is helpful because it lets you inspect the likely result without repeatedly posting a link. However, a preview is not a guarantee: platforms may cache fetched data, use different fields, crop images differently, or change which metadata they support.
Use a social preview checker as one part of a wider publishing workflow. First inspect the rendered HTML and HTTP response. Then check the page in a crawler or validator, review the image itself, and finally test a public URL that is not blocked by authentication, robots directives, a firewall, or an incomplete deployment.
The most important fields are usually the page title, description, selected image, URL, content type, locale, and card type. Open Graph tags commonly use names such as og:title, og:description, og:image, og:url, og:type, and og:locale. Twitter/X card metadata may use fields such as twitter:card, twitter:title, twitter:description, and twitter:image. Support and validation behavior can change, so treat a tool's current documentation and output as the final reference.
| Element | Typical metadata | What to check |
|---|---|---|
| Title | og:title, twitter:title | It matches the page, is specific, and does not contain a template fallback. |
| Description | og:description, twitter:description | It explains the page clearly and is not copied from a site-wide default by mistake. |
| Image | og:image, twitter:image | The URL is public, absolute, stable, reachable, and visually suitable for cropping. |
| Card type | twitter:card | The selected value matches the intended image and layout behavior. |
| Canonical | link rel="canonical", og:url | The preferred URL is consistent, canonicalized, and not a staging or tracking URL. |
| Locale | og:locale | The language and regional setting reflect the page rather than the default site locale. |
| Content type | og:type | The value suits the page, such as an article or website, where applicable. |
Checklist by scenario
For a new page or campaign landing page
- Publish the page to a testable environment or confirm that the production URL is available.
- Open the source or rendered head and confirm that page-level values replace the CMS defaults.
- Run the URL through a browser-based social preview tool. Record the title, description, image, URL, and detected card type.
- Confirm that the image uses an absolute HTTPS URL and can be fetched without a login, temporary token, or session cookie.
- Check the final URL after redirects. A redirect from a tracking URL, HTTP address, or old slug can cause a crawler to read a different page than expected.
- Test the canonical link and
og:urltogether. They do not always need identical formatting, but they should identify the same intended page. - Save a screenshot or test record with the page URL, date, metadata values, image filename, and deployment version.
For a title or image update
Change the page metadata and the image asset together when possible. Check that the new image is not being served from an old cached path and that its file permissions, MIME type, and response are valid. Use a crawler or validator to confirm that the updated HTML is visible to an external fetcher. If the preview still shows the old result, treat caching as a separate diagnostic step rather than changing correct metadata repeatedly.
For a CMS migration or redesign
- Create a sample list covering home pages, articles, products, category pages, localized pages, and pages with no custom image.
- Compare the old and new source for duplicate tags, missing tags, incorrect variables, and unexpected site-wide fallbacks.
- Test URLs with query parameters, trailing-slash variations, redirects, and canonical tags.
- Confirm that image transformations do not produce blocked, oversized, or incomplete URLs.
- Review the default behavior for pages that editors leave partially completed.
For a missing or incorrect preview
- Fetch the exact public URL shown in the post, not only the URL in your CMS.
- Inspect the raw response and rendered head for the expected tags.
- Follow redirects and check which final document the crawler receives.
- Test the image URL independently and inspect its response status, content type, dimensions, and access controls.
- Use the relevant platform's current refresh, re-scrape, or validation mechanism if one is available.
- Wait for the platform to fetch the page again, then retest before making additional changes.
What to double-check
Different tool categories answer different questions. A browser-based preview tool provides a fast visual approximation and is useful for editorial review. A crawler shows what an external fetcher can access, including redirects, blocked resources, response codes, and the final HTML. A validator checks syntax or platform-specific expectations, although its availability and supported fields may change. A CMS plugin helps editors enter and manage values at page level, but it cannot correct a deployment problem, inaccessible image, or crawler restriction by itself.
Check for duplicate Open Graph tags. When multiple plugins, themes, or templates emit the same field, a crawler may select an unexpected value. Also check whether JavaScript adds the metadata after the initial response; some fetchers may not process it in the same way as server-rendered HTML. For important pages, place essential sharing metadata in the initial document response.
Review image details rather than judging only the preview thumbnail. The image should have enough resolution for the intended placement, readable text at a reduced size, a stable URL, and a composition that tolerates different crops. Avoid assuming that one image ratio will look identical everywhere. Keep important faces, logos, and words away from edges, and test both desktop and mobile-looking previews where a tool provides them.
Locale deserves a page-level check on multilingual sites. Confirm that the title, description, language, canonical URL, and locale all point to the same version. For technical metadata workflows, keep the values in a documented template, much like a JSON schema or content contract. A related JSON Schema validation guide can help teams formalize structured checks, while the website performance testing workflow is useful when slow pages or heavy images affect the publishing process.
Common mistakes
- Testing a private or staging URL: A preview may work for an authenticated team member but fail for an external crawler.
- Using relative image paths: Social metadata generally needs a complete, publicly resolvable image URL.
- Leaving template variables unresolved: Tokens such as a missing post title or category make the preview look broken.
- Assuming the browser preview is the source of truth: Always inspect the response, redirects, and image URL as well.
- Changing correct tags to defeat a cache: First use the platform's available refresh process and verify that the new URL is live.
- Ignoring canonical mismatches: A page may display one URL while its metadata identifies another version.
- Publishing duplicate or conflicting tags: Audit theme, plugin, server-rendered, and manually inserted metadata together.
- Forgetting fallback pages: Error pages, search results, author archives, and pages without featured images need deliberate defaults.
For broader release quality, pair this checklist with an accessibility testing workflow. Social previews are only one part of whether a page is ready to share.
When to revisit
Recheck this workflow before seasonal planning cycles, major campaign launches, and any page with a new title, description, image, slug, locale, or canonical URL. Run a representative sample after a CMS migration, theme change, SEO plugin update, image CDN change, hosting move, or redirect implementation. A DNS and domain configuration check is also appropriate when a new domain, subdomain, or delivery host is involved.
Keep a small metadata test register rather than relying on memory. Record the URL, expected values, test tool, date, result, and follow-up owner. Refresh the register whenever platform-supported fields, crawler behavior, validator availability, image requirements, or cache-clearing instructions change. Before the next publication, run the exact URL through the same checks, compare the output with the record, and approve only after the title, description, image, canonical, redirects, and locale agree.
That repeatable process turns an Open Graph debugger or social media preview checker from a last-minute troubleshooting tool into a dependable part of content publishing.