Content change

Watches a page and tells you when it changes. It is the mirror image of content freshness: freshness complains when nothing has happened, this announces when something has.

Use it when

You want to know about a change you do not control: a competitor's pricing page, a supplier's terms, a regulator's guidance, a vendor's status page, a documentation page your integration depends on.

What to enter

Watching the whole page is simple and noisy — an ad slot, a rotating quote or a build timestamp will trigger on every check. If you get noise, switch to a pattern that selects just the part you care about.

It never goes DOWN

Worth saying twice, because it is unlike every other monitor:

• It has no up or down status and opens no incidents.
• It is not counted as downtime anywhere, and not in your uptime figures.
• It has no failure threshold.
• Its page shows a count of changes rather than an uptime percentage.

It sends one alert per detected change. If it cannot fetch the page for about a day, it sends a single "cannot fetch" notice — so a watched page that quietly 404s does not just go silent.

What it doesn't do

• It tells you that it changed, not what changed.
• No JavaScript: it sees the HTML the server sent.
• A page that changes every visit will alert every check. Use a pattern.

Example

URL https://competitor.example.com/pricing, source "part of the body" with a pattern selecting the price table. You hear about a price change the day it happens, not the quarter after.

Alerts

Content changed, and "cannot fetch" after about a day of failures. Never down or recovered, because it has no such state.