Skip to content
Metaspry

Docs

Drift monitoring

Pin URLs, auto re-scan them daily, and catch the moment a page's crawler-facing signals change. Pro feature.

Drift monitoring is a Pro feature. Pin the URLs that matter, and Metaspry re-scans them on a schedule and flags the ones that slipped - so you find out before your audience does.

The pain

You ship a redesign on Tuesday. The new template silently changes og:image. You find out from a Slack share that looks broken on Friday afternoon.

The industry calls this template drift - one CSS or partial change cascades across many pages and nobody notices until rankings move or shares stop converting. Drift monitoring brings that watch down to single-URL granularity.

What it watches

For each URL you pin, every scheduled scan is compared to the previous one and surfaces changes to:

  • Audit score - does the weighted 0-100 number change?
  • Title and description - text and length.
  • Canonical - points elsewhere now? Now a chain?
  • og:image - URL, dimensions, or content type changed.
  • Twitter card - type changed, or image downgraded below the recommended size.
  • JSON-LD - schema type changed, required property dropped.
  • AI crawler row - robots.txt rules changed for any monitored AI bot.
  • Sitemap presence - URL added to or removed from sitemap.xml.
  • Indexability verdict - flipped from indexable to conflict / excluded.

How it works

  1. Pin a URL from the web app.
  2. Metaspry re-scans it automatically - daily by default.
  3. Each scan is diffed against the previous one.
  4. Pages whose score dropped (or whose signals changed) are flagged in the app so you can drill into the diff.

Today this is an in-app workflow: open the app, see what drifted, click into the timeline and diff viewer.

What you’ll see in the app

Your pinned URLs list shows, per URL:

  • Score (current + delta vs the last scan)
  • Last-change date
  • A trend of the score over time

Click into a URL for the detail view:

  • Score timeline
  • Diff viewer: added / removed / value-changed tags, color-coded by severity
  • Per-scan history you can compare across runs

Tiers

TierMonitored URLsRe-scan frequency
Free--
ProPinned URLs, daily re-scanDaily
TeamLarger caps, shared across the workspaceDaily

Why per-URL

Whole-site change monitors crawl tens of thousands of URLs on a fixed cadence and are priced accordingly. Most teams don’t need that. You need to know if the handful of pages that drive your traffic broke overnight - and that’s exactly what pinning a URL gives you.