Social Preview SEO Tool

Twitter Card Validator for X

Validate `twitter:card`, `twitter:title`, `twitter:description`, and `twitter:image` tags before publishing. X (formerly Twitter) has changed public tools over time, so ShareScan validates your page tags directly and highlights issues.

Issue-level diffsSlack reportsGitHub & CMS triggersScheduled monitoring

TRY IT NOW

Run a free 10-URL scan (no signup)

Start with a real scan, review metadata issues, then connect Slack to send a test report.

See a sample scan

Connect Slack to send a test report. Verify your domain to unlock scheduling and 250 URLs.

After scan completion, connect Slack and send a test report.

Up to 10 URLs. We will dedupe and validate automatically. Prepared 0 / 10 unique URLs.

Understand the issue, cause, and fix

Common problems we detect and how to resolve them

1

What breaks X and Twitter card previews

X/Twitter cards can look incomplete, clipped, 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.
How to fix it
  • 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.
2

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.
How to fix it
  • 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.
3

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.
How to fix it
  • Run post-deploy checks in GitHub Actions and monitor pass/fail output.
  • Connect Slack and send a test report to validate notification routing.
  • Verify your domain to schedule recurring scans for your priority URLs.
Unlock full monitoring

Verify your domain to unlock more

Verification unlocks scheduled scans, URL management, and monitoring up to 250 URLs on the Free plan.

Start free workspaceVerify your domain

Frequently Asked Questions

Public tooling has changed over time. ShareScan validates the card-related tags directly from your page output so you can catch structural problems quickly.

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

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

Add automated post-deploy scans and push result summaries into Slack channels that own the fix.

Related Tools

Open Graph Checker

Validate OG fields that power most social preview surfaces.

Link Preview Checker

Check cross-platform preview consistency in one workflow.

GitHub Actions OG Checks

Run metadata checks automatically after each deploy.