Social preview monitoring for content & web teams

Know when your link previews need attention.

Monitor the metadata behind your product and campaign links. Find issues after CMS edits, deploys and image changes, and give your team a clear place to start.

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.

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 link previews need monitoring

Campaign and product links can look fine at launch, then lose the right image, title, or description after the next change.

Why it happens

  • Shared metadata templates changing across many pages at once.
  • CMS edits removing preview image fields or overriding descriptions.
  • Redirect, canonical, or asset changes that affect social crawlers.

What to do next

  • Scan a priority URL to establish the current preview baseline.
  • Choose a follow-up channel and complete setup for the pages you want to monitor.
  • Use alerts to catch preview regressions after deploys and CMS changes.
Check 02

What to watch beyond the first scan

The most expensive preview problems often appear after the initial QA pass.

Why it happens

  • Landing pages continue changing after campaigns go live.
  • Product, pricing, and content pages inherit metadata from shared components.
  • Preview images can become blocked, oversized, stale, or unreachable.

What to do next

  • Track Open Graph, Twitter Card, image, and canonical metadata changes.
  • Route alerts to Slack where marketing, content, and web teams can act.
  • Use report history to understand whether an issue is new or recurring.
Check 03

How monitoring fits the ShareScan flow

A free public scan is intentionally point-in-time; monitoring needs a setup path and clear ownership.

Why it happens

  • The first report can show value without activating ongoing coverage.
  • Teams need to decide which URLs and alert destinations matter.

What to do next

  • Start with the free scan to see current preview and metadata issues.
  • Choose email or Slack follow-ups from the report, or create a workspace for configurable schedules and history.
  • Verify your domain when you need scheduled scans and broader URL coverage.

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.

Before you start

A few useful details.

Is link preview monitoring different from a checker?

Yes. A checker is a point-in-time scan. Monitoring is for URLs that need continued coverage when deploys, CMS edits, or image changes can break previews later.

What happens after I connect Slack?

Connecting Slack sends setup instructions. Complete the setup and choose what to monitor before alerts begin.

What kinds of links should I monitor?

Start with campaign pages, launch pages, pricing pages, product pages, and high-traffic content where a broken preview can cost clicks or trust.

Can I scan before setting up monitoring?

Yes. Run a free scan and review the report before choosing optional follow-ups by email or Slack.

Explore a related check

More ways to keep previews in view.