Social preview monitoring for content & web teams

Keep Open Graph changes in view after publishing.

Follow titles, descriptions and preview images across your product and campaign pages. Scheduled and release-triggered checks help your content and web teams find issues after CMS edits or deploys.

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

What monitoring catches after launch

Metadata regressions often appear after deploys, template edits, CMS updates, and image pipeline changes that seem unrelated to social previews.

Why it happens

  • Shared layout changes touching title, description, or canonical fields.
  • Image pipeline updates that silently break og:image output.
  • Environment-specific behavior that only appears in production.

What to do next

  • Scan priority campaign and product URLs first to establish the current state.
  • Compare issue-level diffs between healthy and regressed runs.
  • Connect Slack to set up monitoring and route alerts to channels with clear ownership.
Check 02

How timelines and diffs speed up fixes

Without a timeline, teams spend too long asking when a preview broke and why.

Why it happens

  • No baseline report to compare against.
  • No release-aware context when tags shift.

What to do next

  • Use trend history to spot first-seen regressions.
  • Inspect field-level changes (og:title, og:image, canonical, and more).
  • Use Slack reports to coordinate content and engineering fixes quickly.
Check 03

How to move from a scan to scheduled coverage

Free report monitoring follows up on up to 10 report pages. Workspace schedules and broader URL management require domain verification.

Why it happens

  • Free report follow-ups cover a small snapshot of pages, rather than a full site.
  • No URL management workflow until ownership is confirmed.

What to do next

  • Choose email or Slack follow-ups from the report for a small set of pages.
  • Verify your domain in ShareScan to unlock scheduler and URL management.
  • Set recurring scans and watch up to 100 pages on the Free plan.

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.

What is the difference between one-off scans and monitoring?

A one-off scan checks the current metadata. Free report monitoring adds weekly follow-ups for up to 10 report pages. A verified workspace adds configurable scan schedules, history and comparisons.

Can I alert a Slack channel when Open Graph breaks?

Yes. Connect Slack from the report to receive setup instructions, then choose what to monitor and where alerts should go.

How many pages can I monitor on the Free plan?

After domain verification, Free plan monitoring supports up to 100 pages.

Can scans run from deploy or publish events too?

Yes. You can trigger checks from GitHub Actions and CMS webhooks in addition to schedules.

Explore a related check

More ways to keep previews in view.

Link Preview Monitoring

Monitor preview regressions after deploys, CMS edits, and page changes.

Metadata Regression Monitoring

Catch title, description, image, and canonical metadata drift.

Slack Preview Alerts

Connect Slack to set up alerts where your team already works.