Social Preview SEO Tool

Open Graph Checker

Validate `og:title`, `og:description`, `og:image`, and `og:url` on real pages. Scan pages, get issue-level guidance, and track changes over time.

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 to validate first in Open Graph

Open Graph previews break when a few core fields are missing, conflicting, or mapped to unstable URLs.

Why it happens
  • No `og:image` or images with unsupported dimensions.
  • `og:url` differs from canonical URL and fragments engagement signals.
  • Template logic outputs old titles after content updates.
How to fix it
  • Set one canonical destination and match `og:url` to it.
  • Use a stable 1200x630 image URL with long-lived accessibility.
  • Audit template variables to ensure `og:title` and `og:description` update on publish.
2

Why valid tags can still produce bad cards

Tags can exist but still produce weak previews if platform crawlers cannot fetch them reliably.

Why it happens
  • Bot access blocked by WAF, robots, or geo restrictions.
  • Redirect loops and transient 5xx responses during deploy windows.
  • Cache layers serving stale HTML to social bots.
How to fix it
  • Allow known social crawlers and validate HTTP status for bot user agents.
  • Reduce redirect hops and avoid temporary URLs in share metadata.
  • Rescan after deployment to confirm final responses and tags.
3

How to keep Open Graph healthy over time

One-off validation is not enough when pages change every release.

Why it happens
  • Metadata checks are not part of deployment or publish workflows.
  • No alerts when a previously healthy page regresses.
How to fix it
  • Schedule scans after domain verification to monitor key URLs continuously.
  • Send Slack reports to page owners and track issue-level diffs over time.
  • Use post-deploy triggers from GitHub or CMS publish events.
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

Yes. Mismatches can split previews and analytics across multiple URL variants.

Yes. Crawler access, cache state, redirects, and response errors can all break preview rendering even with tags present.

No. ShareScan scans your pages, detects metadata issues, and tracks diffs. Cache refresh actions stay in each platform's own troubleshooting tools.

Verify your domain, schedule scans, and push reports to Slack to catch changes quickly.

Related Tools

Link Preview Checker

Cross-channel metadata checks for title, description, and image.

Open Graph Monitoring & Alerts

Track trend lines and send issue diffs to Slack.

LinkedIn Link Preview Checker

Diagnose LinkedIn preview behavior and caching expectations.