Social preview monitoring for content & web teams

Check social previews when your CMS publishes.

Trigger ShareScan checks from CMS webhooks. Find missing images and metadata issues after publishing, then use the affected pages and findings to guide follow-up.

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

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

Why publish-triggered scans matter

Preview regressions often start at publish time, especially when templates and content models evolve quickly.

Why it happens

  • CMS entries missing image fields or overriding metadata defaults.
  • Template-level changes that impact multiple page types at once.
  • Publishing workflows that skip metadata QA under deadline pressure.

What to do next

  • Trigger scans from CMS webhooks on publish events.
  • Include newly published and high-priority evergreen URLs.
  • Connect Slack to continue setup and route alerts to the content or web team.
Check 02

How secure webhook-based monitoring works

Event-based scans need controlled access and predictable payload handling.

Why it happens

  • Unsigned webhooks or weak shared secret handling.
  • Inconsistent URL payloads between CMS environments.
  • No retry strategy for transient delivery failures.

What to do next

  • Use secure webhook integration settings and shared secrets.
  • Normalize incoming URLs before scan requests are queued.
  • Use Slack setup instructions to verify routing before relying on alerts.
Check 03

How to prevent recurring publish regressions

Teams need feedback loops that connect publish events to release-quality ownership.

Why it happens

  • No monitoring between major launches.
  • No central trend view for metadata quality over time.

What to do next

  • Combine webhook-triggered scans with scheduled monitoring.
  • Verify your domain to unlock URL management and 100-page Free monitoring.
  • Track diff history to identify recurring metadata failure patterns after CMS edits.

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.

Can ShareScan scan URLs immediately after CMS publish?

Yes. CMS webhook triggers can run scans right after publish to catch issues quickly.

Can webhook scans send results to Slack?

Yes. Connect Slack to continue setup and route alerts to the channel that owns the published content.

What if the preview is still stale after publish?

Platform caches may lag behind your source metadata update. Validate the live page output first, then use platform troubleshooting tools as needed.

Should webhook monitoring replace scheduled scans?

Use both. Webhooks catch publish events, while schedules catch drift and regressions that happen between publishes.

Explore a related check

More ways to keep previews in view.

Open Graph Monitoring & Alerts

Add recurring scans and trend-based regression tracking.

Slack Link Preview Checker

Route publish scan reports directly into team channels.

Link Preview Checker

Run fast checks on individual URLs before broad rollout.