Social preview monitoring for content & web teams

Check your Open Graph tags before you share.

Find missing or conflicting Open Graph titles, descriptions, images and URLs. Give content and web teams a clear report to work from before the next launch.

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

Is the tag missing, or is the image failing?

  1. Read the published HTML

    Find og:image in the page source. Use property="og:image" and content="https://…". A tag visible only after JavaScript runs may not be available to the sharing platform.

  2. Fetch the image itself

    Open the exact image URL without signing in. Check the final response status and Content-Type: a successful HTML login page is not an image. Check redirects and expiring image URLs too.

  3. Check a representative set of pages

    Paste up to 10 URLs, one per line, into the free scan above. Include a product, article and campaign page when relevant. A domain or sitemap input selects a limited sample; it does not check your whole site.

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 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.

What to do next

  • 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.
Check 02

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.

What to do next

  • 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.
Check 03

How one scan becomes monitoring

One-off validation is useful, but Open Graph tags can regress after launches, CMS edits, or shared template changes.

Why it happens

  • Metadata checks are not part of deployment or publish workflows.
  • No alert path when a previously healthy campaign page loses its image or description.

What to do next

  • Scan a priority URL first and review the report for current Open Graph issues.
  • Choose weekly follow-ups by email or Slack from the report for up to 10 report pages.
  • Use scheduled, GitHub, or CMS-triggered scans for broader coverage after verification.

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.

Should `og:url` match the canonical URL?

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

Can Open Graph tags exist but still fail in social apps?

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

Do you refresh LinkedIn or Facebook caches for me?

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

How do I keep monitoring Open Graph regressions?

Start with a free scan and choose email or Slack follow-ups from the report. Create a workspace and verify your domain when you need scheduled scans and broader URL coverage.

Explore a related check

More ways to keep previews in view.

Social Preview Testing

A broader testing flow for Slack, LinkedIn, X, and Open Graph cards.

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.