Social Preview SEO Tool

Link Preview Checker

Check how your URL title, description, and image render in social previews. Find issues fast, then monitor regressions after publish or deploy.

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 goes wrong in link previews

Previews can show the wrong image, stale copy, or a different landing page than expected.

Why it happens
  • Missing or low-quality `og:image` and `twitter:image` tags.
  • Titles and descriptions that are too long and truncate in feeds.
  • Redirect chains or canonical conflicts that point crawlers to another URL.
  • Bot blocking rules that stop preview scrapers from loading metadata.
How to fix it
  • Set one canonical URL and align `og:url` with that destination.
  • Use a 1200x630 share image and confirm it is fetchable without auth.
  • Keep titles concise and put key context in the first 55-70 characters.
2

Why previews stay stale after updates

You publish a fix, but old cards can keep showing until each platform re-crawls the page.

Why it happens
  • Platform-level cache windows and recrawl timing differ by channel.
  • CDN caching can keep old HTML or image responses available to bots.
  • The shared URL might include variants with different metadata output.
How to fix it
  • Re-share the exact canonical URL and verify response headers are current.
  • Use platform troubleshooting tools such as LinkedIn Post Inspector or Facebook Sharing Debugger when needed.
  • Run a new scan after publish to confirm source metadata is fixed.
3

Practical checklist before launch

Most preview incidents are preventable with a short preflight pass before publish or deploy.

Why it happens
  • No consistent QA step for metadata across content and engineering teams.
  • No regression monitoring between releases.
How to fix it
  • Run a free 10-URL scan before launch and review issue-level guidance.
  • Connect Slack and send a test report to verify routing and ownership.
  • Verify your domain to unlock scheduled scans and ongoing monitoring up to 250 URLs on Free.
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

The image tag might be missing, blocked, too small, or cached. Check `og:image` and `twitter:image` values, then verify the image URL can be fetched directly.

Most platforms cache metadata and refresh on their own schedule. Make sure the canonical URL now serves updated tags and use each platform's inspector/debug tool if available.

Different feeds reserve different character space. Keep titles tight and move critical context to the first sentence of the description.

Run scans post-deploy and compare diffs between releases. Then push results to Slack so the owning team gets immediate visibility.

Related Tools

Open Graph Checker

Validate `og:*` tags and fix structural metadata issues.

Twitter Card Validator for X

Check `twitter:*` tags, truncation risk, and image quality.

Slack Link Preview Checker

Debug Slack unfurls and route regressions to the right channel.