Use case
SEO on-page change monitoring
Track the visible heading and body region. A rewritten H1 or swapped intro shows up as a text diff you can archive.
Rankings move when the visible copy moves
Crawl tools tell you a title tag changed after the fact. A region on the H1 and first paragraph tells you the hour the live page rewrote the query. Pair it with Search Console; do not replace it.
Wachete and Distill.io can watch HTML. WebURLTracker is a better solution when SEO and content share a workspace and need a screenshot of the rendered heading, not only the source.
What to watch on a page you rank for
Most ranking drops that come from your own site trace back to a short list of fields. Someone shortens the title tag, a CMS template drops the meta description, a redesign changes the canonical, or a staging setting leaks a noindex into production. Each of these is one small value on the page, so each one deserves its own target instead of a full-page screenshot.
In WebURLTracker, add a Meta / title target for the title tag and the meta description. Add an Attribute target for the canonical link (the href on link[rel=canonical]) and for the robots meta tag (the content on meta[name=robots]). These targets compare the exact value, so a change from "index, follow" to "noindex" is one clear line in the alert, not a pixel diff you have to squint at.
Then draw one region around the H1 and the opening paragraph. That is the copy a searcher reads first and the part writers rewrite most often. Text and screenshot are kept together, so you can see both the old wording and how the page looked when it changed.
Site files that can change rankings overnight
Some of the costliest mistakes never touch a single page. A deploy ships a robots.txt with a blanket Disallow, or the sitemap loses half its URLs after a plugin update. Nobody notices until traffic falls a week later.
Watch your robots.txt as a plain text monitor and your sitemap.xml as a sitemap monitor. The sitemap check compares the list of URLs, so the alert names the pages that were added or removed instead of showing a wall of XML. A daily interval is enough for both, and they cost very little to check.
Add an HTTP status target on your most important landing pages too. A page that quietly starts returning 404 or a redirect loses its ranking fast, and the status check catches it on the next run.
Learn from the pages that outrank you
When a competitor moves above you for a query you care about, the useful question is what they changed. Put a Meta / title target and a region on the H1 and intro of their ranking page. When they rewrite the title or add a new section, you get the before and after with a date attached.
Keep these in a separate folder per competitor so the team can scroll one timeline instead of hunting through alerts. Over a few months the history shows which edits they make before a ranking gain, which is more useful than any single snapshot.
How to set it up in a few minutes
Paste the page URL into the preview, then add the targets: title and description, canonical, robots meta, and a region on the H1. Name the monitor after the query the page ranks for, such as "pricing page, main keyword", so the alert makes sense to whoever reads it.
Set the interval to daily for most pages and hourly only for pages where a broken release would be expensive. Send alerts to the channel your team already reads: email, Slack, Teams, Discord, or Telegram are on every plan, and paid plans add signed webhooks if you want changes in your own tooling.
Turn on the option to ignore timestamps and counters so a "last updated" line or a view count does not trigger an alert. The goal is a monitor that only speaks when a field that affects search actually changed.
Pair it with Search Console
Search Console tells you that clicks or positions moved. The change history tells you what was different on the page at the time. When a query drops, open the monitor timeline for that URL and check whether the title, canonical, or heading changed in the days before. If nothing changed on your side, the cause is more likely on the results page or a competitor, and the competitor folder is the next place to look.
For related setups, see content quality monitoring for catching broken modules after a deploy, and competitor page monitoring for tracking rival positioning beyond search.
Typical pages
- Category landers
- Program pages
- Help-center articles
Related watches
Paste the URL on the homepage to try the region picker, or create a free account.