Change MonitorMonitorReady
The change monitor compares each crawl with the last one and tells you when something important changed: a noindex tag, a robots.txt rule, a canonical, a title or a redirect. Many small changes from one deploy become one clear incident.
The Changes Monitor watches your own sites over time, so it works in your workspace. Sign in, add a site, and its first check runs within a minute.
How to use it
Four steps from an address to results you can act on.
We record a first snapshot of the pages and rules that matter for SEO.
Each new crawl is compared with the last one, field by field.
Changes from the same deploy or template become one incident with sample URLs.
Mark it as expected, or send it to the Fix Tracker with the before and after.
What it brings you
Every result comes with the proof behind it, so you can check it yourself.
New disallow rules that could block important pages.
Pages that suddenly ask search engines to leave.
Canonical targets that changed or now point elsewhere.
Edits to the text shown in search results.
Pages that start redirecting or stop working.
Large text changes on pages you choose to watch.
What the result looks like
Results are sorted so the most important rows come first. This example uses sample data to show the layout.
| Change | Status | Pages |
|---|---|---|
| Noindex added to /blog/* | Changed | 38 |
| Robots.txt: new Disallow /shop | Changed | All |
| Title rewritten on /pricing | Changed | 1 |
| Canonicals unchanged | OK | 212 |
What you get
For your team and your clients' sites.
Questions
No. Changes are grouped by cause, and you can mark areas of a page to ignore.
Changes that land together across a template are grouped as one incident. A simple API can also tell it when you deploy.
The before and after values, the time it was seen and sample URLs.
The uptime monitor tells you the site is down. The change monitor tells you the site is up but something important changed.