Web Page Monitor Changes: What Counts as a Real Change
Most page monitors fire on everything. The useful ones know the difference between a restyle and a price cut.
By AyeWatch Team3 min read
Short answer: A web page monitor should alert on a change to the fact you named, not on every byte or pixel. Price, availability, plan names, legal clauses, and job titles are real changes. Carousels, cookie banners, timestamps, and A/B tests are noise.
AyeWatch is a semantic page monitor: it reads the rendered page, compares it against a plain-English rule, and sends a summary that names the delta.
Three kinds of change
There is the change the page owner intended: a new price, a new role, a new clause. There is the change the page owner did not intend you to notice: a quiet edit to a fee table or a terms paragraph. And there is the change nobody intended: a rotating ad, a timestamp, a layout test.
A byte monitor treats all three the same. A semantic monitor can separate them because you told it what counts.
Name the fields
Write the rule as a list of fields. "Price, plan names, included seats." "Job title, location, team." "Section 4, cancellation terms." Fields give the monitor something to compare and give you something to read.
If the page has no stable fields, it may not be a monitoring target. It may be a page you should read weekly instead.
Ignore lists never finish
Raw HTML tools let you exclude selectors and strings. You add one for the timestamp. Then the cookie banner. Then the CSRF token. The list grows and the next redesign resets it.
A rule about meaning is shorter and survives a restyle. You are not enumerating everything that is not a price. You are naming the price.
Measure the noise
For one week, count alerts you would have forwarded. If the ratio is below one in three, the rule is too wide. If it is zero and the page moved, the rule is too narrow or the interval is too slow.
Noise is not a cosmetic problem. It trains you to ignore the channel, and the next real alert dies in that habit.
A rule you can forward
The test is simple: would you paste the alert into a team channel without editing it? If yes, the monitor is doing its job. If you need to open the page to understand the alert, it sent you a notification, not an answer.
AyeWatch writes the summary. The page change alerts guide covers routing and intervals. This page is the definition of a real change.
| Change | Example | Should it alert? |
|---|---|---|
| Price | Pro moves from $9 to $12 | Yes |
| Availability | A size or SKU returns to stock | Yes |
| Legal text | A cancellation clause is added | Yes |
| Job listing | A staff role appears | Yes |
| Layout | The hero image rotates | No |
| Consent banner | The cookie notice reappears | No |
| Timestamp | A build hash changes | No |
Start a monitor in under a minute
Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.
Try it free for 7 daysThe bottom line
Write down the last change on that page you actually cared about. That sentence is your rule. If you cannot remember one, the page may not need a monitor. If you can, you already know what to watch.
FAQ
Why does my page monitor alert on changes that do not matter?
It is comparing bytes or pixels. Those change when ads rotate, banners load, or a layout test runs. Use a rule that names the fields you care about, or switch to a semantic monitor.
What is a real page change?
A change to a fact you would repeat to a colleague: a price, a plan, a clause, a job, an availability state. A visual restyle is not a real change unless design is the job.
Can a page monitor ignore cookie banners?
A semantic monitor can, because the rule names the content that counts. A raw HTML or pixel monitor needs an ignore rule, and that rule breaks when the banner markup changes.
How many alerts should a good monitor send?
Few enough that you read every one. If most alerts are noise, the rule is too wide. A quiet week on a quiet page is a success.