Social preview monitoring for content & web teams

Check your X / Twitter Card metadata.

Inspect card types, titles, descriptions and preview images, including Open Graph fallbacks. Find metadata issues before your team shares campaign and product links on X.

Start with a free scan. No account or credit card. Then choose weekly follow-ups by email or Slack for up to 10 report pages.

Paste a page, a domain, or up to 10 URLs, one per line.

See what the report shows

Quick diagnosis

Three checks when your Twitter/X card looks wrong.

  1. Check the card type and image tags

    For a wide image card, check for twitter:card set to summary_large_image in the initial page HTML. Compare twitter:image with og:image so an older Twitter-specific tag does not hide your new image.

  2. Open the image URL on its own

    Open the exact image URL from the metadata without logging in. It should return the intended image, not an error, a sign-in page, or an expired download link. Check redirects and the response content type too.

  3. Compare the current source with the card on X

    If the page and image are current but X shows an older card, check the exact shared URL and retest on X. ShareScan checks fetched metadata; it cannot clear X’s cache or guarantee the card X displays.

A clear place to start

See the issue. Find the page. Follow up.

  1. Check the sourceInspect titles, descriptions and images in the metadata your pages serve.
  2. Review the findingsOpen affected pages and use the issue details to decide what needs fixing.
  3. Check again after changesRun another scan after a fix, or set up recurring checks for the pages that matter.

Previews are based on fetched metadata. Slack, LinkedIn and X may show a different or cached card.

ShareScan / Preview reportActual product view
A ShareScan report showing a metadata score, checked pages and findings from a scan of sharescan.io.
A real scan of sharescan.io, captured 8 October 2026. A dated snapshot of three pages, not a live status.

From finding to fix

What to check and how to follow up.

Check 01

What breaks X and Twitter card previews

X/Twitter cards can look incomplete, clipped, stale, or inconsistent with Open Graph defaults.

Why it happens

  • Missing twitter:card declaration or unsupported image sizes.
  • Long copy that truncates the message before the value proposition appears.
  • Template fallbacks pulling stale metadata from previous page versions.
  • A page relies on client-side JavaScript to inject card tags after the crawler has already fetched HTML.

What to do next

  • Set twitter:card explicitly and confirm image dimensions are appropriate.
  • Keep twitter:title and twitter:description concise and front-loaded.
  • Align X/Twitter and Open Graph tags so cross-channel cards stay consistent.
  • Serve the card tags in the initial HTML response and keep the image publicly fetchable.
Check 02

Why cards differ between channels

Slack, LinkedIn, and X (formerly Twitter) may all render the same URL differently.

Why it happens

  • Each platform chooses different tag precedence and truncation behavior.
  • Recrawl timing differs, so one platform may keep an older snapshot.
  • Network errors during fetch can force fallback behavior.

What to do next

  • Scan the page metadata source first and validate both OG and Twitter tags.
  • Use one canonical URL with stable metadata and image assets.
  • Re-run scans after each deploy to catch regressions early.
Check 03

Release checklist for card quality

Cards often regress during routine releases when metadata QA is not automated.

Why it happens

  • No CI checks for metadata changes.
  • No alerting route to marketing or content owners.

What to do next

  • Run post-deploy checks in GitHub Actions and monitor pass/fail output.
  • Connect Slack from the scan report to continue setup and route preview alerts.
  • Verify your domain when you need recurring scans for priority campaign URLs.

When your team needs broader coverage

Bring recurring checks into your publishing workflow.

Create a workspace and verify your domain to schedule scans, manage URLs and connect CMS or GitHub Actions triggers. The Free workspace plan covers up to 100 pages.

Create free workspaceCompare monitoring plans

Before you start

A few useful details.

Does ShareScan show the exact card that X will display?

No. ShareScan checks the metadata and image your page serves. X may fetch a different response or show a cached card, so compare the report with X itself before sharing an important link. A scan does not refresh X’s cache.

What should I check in a Twitter/X card validator?

Check twitter:card, twitter:title, twitter:description, twitter:image, Open Graph fallback tags, canonical URL, redirect behavior, and whether the image can be fetched without cookies or authentication.

Why does my X/Twitter card text truncate?

Card layouts have limited space and vary by device. Keep titles short and keep the description focused on one message.

Why does X/Twitter show a different image than Open Graph?

If twitter:image differs from og:image, cards can diverge. Use intentionally different images only when required.

How can I avoid regressions after deployment?

Run post-deploy scans in a verified workspace and share the findings with the team that owns the fix.

Explore a related check

More ways to keep previews in view.

Social Preview Testing

Check the whole preview workflow before campaign and launch links go out.

Open Graph Checker

Validate OG fields that power most social preview surfaces.

Link Preview Checker

Check cross-platform preview consistency in one workflow.