Skip to main content
SkyyCast
Marketing & publishing tool

Social Preview Checker & OG Image Debugger

See exactly what your public metadata is telling social platforms: inspect Open Graph and Twitter Card tags, verify your preview image actually works, catch conflicting or missing tags, and get a simulated preview before you publish.

  • Real HTTP & HTML diagnostics
  • Image dimensions verified
  • No account required

Your analysis will appear here

Enter a URL and select Analyze URL to see the preview and diagnostics.

Enjoy this free tool? Help support SkyyCast and keep more free creator tools coming.

How to Use This Tool

  1. 01 Enter a public URL

    Use the page address you plan to share.

  2. 02 Fetch and inspect

    Review Open Graph, Twitter Card, canonical and preview-image findings.

  3. 03 Fix and recheck

    Update the source page or image, then run the checker again.

Social tools reference

Debug the metadata behind a shared link

A social preview depends on the page head, the image URL and the platform cache. This checker shows what the fetch returned and simulates several common card layouts.

When this helps

Use it after publishing a page update or before sharing a new landing page. Check the canonical and preview-image URLs as well as the title; a visually correct page can still expose stale head metadata.

Practical example

Enter a public article URL, compare the Open Graph title with the visible page title, and open the reported image URL separately. If the tags are correct but a social platform still shows an older card, its cache may need its own refresh path.

Reference at a glance

Reference at a glance for Social Preview Checker
MetadataThe report compares Open Graph and Twitter Card values and flags conflicts as facts about the page.
ImagesThe checker inspects the resolved preview image response and dimensions when it can fetch them.
CanonicalA canonical URL helps describe the preferred page, but it does not force every platform to refresh its cache.
LimitsA simulation cannot reproduce every platform crawler, cache or rendering decision.

Troubleshooting

  • If the checker cannot fetch a URL, confirm that the page is public and that its server allows the required request.
  • After fixing tags, a platform may still show an older cached preview; use that platform’s own refresh mechanism.
  • Check that preview images use absolute, publicly reachable URLs and return the intended image content.

Questions worth checking

Why does the preview differ from the page?

The preview reads metadata and image responses, not the full interactive page. Check the fetched values and the cache state separately.

Can it fix the tags?

No. Update the source page, rebuild or deploy it, then run the checker again.

Keep in mind: Only the URL is sent through the existing checker request path. The tool does not ask for account credentials or publish the page.

Why check your social preview before publishing?

A broken or missing preview image, a mismatched title, or a conflicting tag between Open Graph and Twitter Card metadata can make a shared link look unfinished or untrustworthy -- and by the time you notice, it may already be cached by the platform that shared it. Checking first means you can fix a problem before it reaches an audience, not after.

This tool fetches the actual page server-side (a browser cannot read another site's HTML directly because of cross-origin restrictions), parses its real HTML, and inspects the resolved preview image itself rather than trusting the declared dimensions.

What this tool checks, and how

  • Open Graph. The protocol's four required base properties (og:title, og:type, og:image, og:url) plus the structured og:image sub-properties and og:description/og:site_name, which are recommended but not required.
  • Twitter/X Card. twitter:card, twitter:title, twitter:description, twitter:image, twitter:site and twitter:creator, cross-checked against the Open Graph equivalents. X documents that it falls back to Open Graph tags when a twitter:* tag is missing, so a missing tag is reported as informational, not an error.
  • Canonical & URL relationships. The requested URL, the final URL after redirects, the declared canonical, and og:url are compared -- a mismatch is reported as a fact, never as a claim about search ranking or indexing.
  • The actual preview image. Fetched and inspected directly: real HTTP status, content type, and pixel dimensions read from the image's own header bytes, compared against any declared og:image:width/height.

A minimal set of tags, and how to debug a bad preview

For most pages, five tags in the <head> are enough: og:title, og:description, og:image (an absolute, publicly reachable URL), og:url and og:type, plus twitter:card set to summary_large_image if you want the large card on X. A 1200 × 630 pixel image, close to a 1.91:1 ratio, is a sensible cross-platform default.

When a preview looks wrong, work through the report in this order. First, check the fetch: if the page could not be fetched, or the final URL after redirects is not the one you meant to share, nothing below matters. Second, read the metadata and cross-checks: a missing og:image, or og:title and twitter:title that disagree, are the usual causes. Third, look at the preview image candidates, because the tool inspects the real image file (its status, type and pixel size), which catches images that are missing, blocked or much smaller than declared. Finally, if the report is healthy but a platform still shows the old card, that is the platform’s cache, and its own debugger or time will refresh it.

Our guide How to control your link preview: Open Graph and social cards explained covers the tags and the caching in more depth. If the link carries campaign tags, build and check them with the UTM Campaign Builder.

What this tool cannot promise

  • It cannot guarantee exact platform rendering. Facebook, X, LinkedIn and other platforms may cache a previous version of a page's preview, apply their own crawler logic, or change layouts without notice. The previews shown here are simulations built from the metadata this tool could fetch, not a call to any platform's own API.
  • It cannot guarantee search ranking or indexing outcomes. A canonical mismatch is reported as a fact; this tool never claims to know how Google will index a URL.
  • It only reads the page once, as a logged-out, non-JavaScript visitor would. A page that renders its metadata with client-side JavaScript will not show those tags here, since the fetch never executes the page's scripts.

Privacy

SkyyCast fetches the public URL you submit, server-side, to inspect its HTML and social metadata. The submitted URL necessarily reaches the SkyyCast API to do this -- we do not claim this tool works entirely in your browser, because that would not be true for a tool that reads another site's page. We do not require your site's credentials, do not forward cookies or an Authorization header to the page being checked, do not execute its JavaScript, and do not store the analysis, the fetched HTML, or a copy of the image anywhere after the response is returned.

Frequently asked questions

What is Open Graph metadata?

Open Graph is a set of <meta> tags (prefixed og:) that a page adds to its <head> to tell any platform that reads it what title, description, image and type to show when the page is shared as a link. It's an open protocol, not something specific to one social network -- most major platforms and messaging apps read it.

Why does my shared link show the wrong image or no image at all?

The most common causes: no og:image tag at all, an og:image pointing to a URL that no longer exists or returns an error, an image blocked behind authentication, or a platform that already cached an older version of the page from before the image was added. This tool fetches and checks the image directly so you can see which of these is actually happening.

Why do og:title and twitter:title sometimes show different text?

They're two separate, independent tags. If a page sets both and they disagree, different platforms can show different text for the exact same link, since X/Twitter prefers its own twitter:* tags when present and other platforms generally read Open Graph. Keeping them identical (or only setting the Open Graph tags, which X falls back to) avoids the inconsistency.

Do I need twitter:card tags if I already have Open Graph tags?

Not strictly -- X documents that it falls back to Open Graph tags when twitter:* tags are missing, which is why this tool reports a missing twitter:card as informational rather than an error. Adding them explicitly gives you direct control over how the X card specifically renders, which can be worth doing if X is an important audience for a particular page.

Why does my preview still look wrong after I fixed the tags?

Several platforms cache a link's preview the first time it's shared and don't automatically re-check it. If a page changes after someone has already shared it, you may need that platform's own cache-refresh/debug tool to force it to re-fetch -- this checker reads the page fresh every time, so a healthy result here means the current HTML is correct even if an old cached preview is still showing elsewhere.

Does a canonical URL mismatch hurt my SEO?

This tool only reports that the canonical URL, the final URL, and og:url disagree -- it's a fact about the page's own tags, not a claim about search ranking or indexing, which only a search engine itself determines. A mismatch is still worth fixing for consistency, but treat it as a metadata hygiene issue here, not an SEO verdict.

More free tools

See all free SkyyCast tools. Want the text, images, video and link checked together? Try the Bluesky Post Checker. Sharing a tracked campaign link? Build it with the UTM Campaign Builder first, then check this page to see how it previews once the parameters are attached. Publishing to Bluesky? Check the post first with the Bluesky Post Validator, or the image with the Bluesky Image Size Checker.

About this tool

SkyyCast is an independent third-party service. It is not affiliated with, endorsed by or sponsored by Facebook/Meta, X, LinkedIn, or any other platform referenced on this page. Platform names are used only to describe the preview format being simulated.