Skip to content

article

Domain Monitoring and Change Alerts

Capture periodic snapshots of a domain's SEO posture and get plain-English alerts when health, backlinks, keywords, or issues change.

What the Domain Monitor does

The Domain Monitor combines tracking-over-time with change alerts. Each run captures a snapshot of a domain's SEO posture — all from StretchSEM's own engines — and diffs it against the previous snapshot to tell you exactly what changed. Capturing a snapshot costs 1 credit; reading the monitor history and deltas is free.

Monitoring is what makes ongoing SEO work visible: instead of wondering whether last month's fixes helped, you see the movement.

What a snapshot captures

Each snapshot records six metrics:

  • SEO health — the domain's health score (higher is better).
  • Pages — indexed page count.
  • SEO issues — total audit findings (lower is better).
  • Backlinks — total inbound links in the link graph.
  • Referring domains — distinct sites linking to you.
  • Keywords — distinct indexed keyword terms.

Running a monitor snapshot

  1. Open the Diagnostics or Tracking area and choose Domain monitor.
  2. Enter the domain.
  3. Run. StretchSEM captures a fresh snapshot, stores it, and compares it to the previous one.

The first run for a domain establishes a baseline (there's nothing to compare yet). Every run after that produces deltas and alerts.

Reading deltas and alerts

For each metric the monitor shows now, was, the delta, and a direction (up/down/flat). It also generates plain-English alerts — for example "SEO health improved: 74% → 82% (+8 pts)" or "Referring domains declined: 19 → 16 (−3)." Crucially, alerts are sorted with declines first, because a drop is the actionable signal you want to see immediately. The monitor knows which direction is good for each metric (more health, backlinks, keywords, and pages is good; more SEO issues is bad).

Building a monitoring routine

  1. Run a snapshot when you start work on a domain to set a baseline.
  2. Re-run on a regular cadence (weekly or monthly) — ideally after each batch of fixes.
  3. Each time, read the declines first to catch regressions (a broken deploy that adds errors, lost backlinks, dropped pages).
  4. Use the improvements to demonstrate progress in client or stakeholder reports.

A realistic example

An in-house SEO sets a baseline on acme.com: health 74, 240 backlinks, 41 SEO issues. After a month of fixing broken links and adding metadata, the next snapshot alerts: "SEO health improved 74% → 85%," "SEO issues declined 41 → 22" (a good decline for that metric), and "Backlinks improved 240 → 268." But it also flags "Pages declined 42 → 38" — surfacing that four pages fell out of the index, which they investigate and find was an accidental noindex on a template.

How it relates to other tools

  • The snapshot's health and issues come from the same engine as the Site Audit.
  • Backlinks and referring domains come from the link graph (run a backlink scan to keep it fresh).
  • Keyword counts come from your crawl index.
  • When Google Search Console is connected, real Google ranking data can enrich the picture.

Tips

  • Establish a baseline before you start optimizing so you can prove the impact.
  • Monitor on a consistent schedule — the deltas are only as meaningful as your cadence is regular.
  • Treat any decline alert as a to-do, especially drops in pages, backlinks, or referring domains.
  • Pair monitoring with rank tracking for the complete over-time picture: positions and posture.

FAQ

Why does my first snapshot have no alerts? There's no previous snapshot to compare against yet. The first run is your baseline; the next run produces deltas.

Is reading the monitor free? Yes. Only capturing a new snapshot costs a credit; reading history and deltas is free.

How often should I run it? Weekly for active engagements, monthly for maintenance. Always run one after a significant site change.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.