Website change alerts: get an email when a web page changes
How to set up a website change alert: get an email when a web page changes, choose how often it is checked, and stop false alerts from firing.
Alexandra SwanCustomer Operations Lead
The short answer
A website change alert is an email you get when a page you are monitoring changes. To set one up, paste the page's URL into a change monitoring tool, say in plain English what should trigger the alert (or leave it blank for any change), pick how often the page is checked, and choose where the alert goes. After the next check that finds a change, the alert says what changed in a few short lines, such as the old price and the new one.
How to set up a website change alert
The whole setup takes about a minute and needs no code, no browser extension, and nothing left running on your machine. The checks happen on a server, so it works while your laptop is closed.
- Copy the URL of the exact page you want to monitor. Use the page itself, not a category, search, or feed page, because those reorder themselves constantly and will fire alerts about nothing.
- Paste it into the monitoring tool and say what should trigger the alert, in plain English: 'alert me when the price drops' or 'tell me when the status changes'. Leave it blank and any change to the page's text counts.
- Pick how often the page is checked. The next section covers how to choose.
- Choose where the alert goes: your email address, or a Slack channel when a team acts on it. Each alert says what changed in plain words, such as the old price and the new one, and links to the exact lines.
That last detail is the one worth insisting on. An alert that only says the page changed sends you back to the page to work out what happened, which is most of the work you were trying to avoid.
For the wider picture, from choosing the page to choosing a tool, see how to monitor a website for changes.
How often to check the page
The right interval is set by how fast the thing you care about disappears, not by how important it feels. Checking a slow page every 5 minutes does not make you better informed, and checking a fast one daily means the answer arrives after it stopped mattering.
| Check every | Right for | Why |
|---|---|---|
| 5 minutes | Restocks, ticket releases, flash sales, sanctions, status pages and FAA ground stop alerts | Other people are racing you, or the exposure window is measured in minutes |
| Hourly | A competitor's pricing page during a launch, a job board, a tender portal | Fast enough to act the same day, quiet enough to ignore for a week |
| Daily | Terms of service, privacy policies, vendor documentation, long-running competitor watching | These pages change rarely, and the response is measured in days anyway |
On Website Change Tracker, daily checks come with every plan, hourly checks start on Starter, and 5-minute checks on Pro.
Why most page change alerts become noise
The usual reason people abandon change monitoring is not that it failed to detect a change. It is that it detected all of them.
A modern page is full of things that move for reasons unrelated to why you are watching: a rotating banner, a view counter, a "3 people are looking at this" widget, a cookie notice, a recommended products carousel, a timestamp in the footer, an A/B test serving you a different variant. Monitor the whole page and every one of those counts as a change.
After three or four alerts that turn out to be nothing, you stop opening them. The monitoring is still running and still reporting, and it has stopped working, because the failure is in whether you read it.
How to stop false alerts
All the fixes come down to narrowing what can trigger the alert.
- Describe the change rather than the page. A rule like 'alert me when the price drops' does not fire when the price rises or when a banner rotates above it.
- Ignore the lines that always move. Dates, view counts and live-visitor widgets can be listed once and skipped on every check.
- Monitor one element instead of the whole page by pointing a CSS selector, such as .price, at it. Everything outside the selection loses the ability to fire.
- Point at the specific page, not a listing. Product pages are stable; search results and category pages reorder on every load.
- Slow the interval down for pages that change slowly. A daily check on a policy page produces one true alert a quarter instead of fifty ambiguous ones.
A monitor you still trust after a month is worth more than one that catches marginally more and gets muted in week two.
There is a worked example, using real checks of the Hacker News front page, in how to stop false positives in website change monitoring.
Other ways to get notified when a website changes
Change monitoring is not always the answer. It is worth knowing when something simpler will do.
Monitoring earns its place when the page will not tell you, the change is an edit rather than a new item, and being late has a cost.
For new posts, events and listings in particular, see how to get notified when a website is updated.
The site's own notifications
If the page offers a back-in-stock alert, a price drop watch, or a mailing list, use it. It is free and it is authoritative. The catch is that the site chooses what counts as newsworthy, and it is rarely the thing a competitor or a regulator would rather you did not notice.
An RSS feed
Where a feed exists, it is a clean solution. Feeds are increasingly rare outside blogs and news, and they carry new items rather than edits, so a reworded clause on an existing page never appears in one.
A site without a visible feed often still has one; how to get an RSS feed from a website that doesn't have one shows where to look.
A script you write yourself
Fetching a page on a timer and diffing it is an afternoon's work. Keeping it alive is the part people underestimate: pages start rendering client-side, requests get blocked, the selector you keyed on gets renamed in a redesign, and your cron job reports success while watching nothing. The maintenance, not the build, is what makes this the expensive option.
Where to send website change notifications
Email is the right default because it is the one channel everyone already reads, and because an emailed diff is a record you can forward, file, and search months later.
For anything a team acts on rather than one person, send it to the channel where the work happens as well. A price change that reaches a shared Slack channel gets picked up by whoever is free. The same alert in one person's inbox waits for them to come back from leave.
For a change one person has to act on within minutes, such as a restock or a seat opening up, a text message or a WhatsApp notification reaches them faster than an inbox.
To feed changes into your own systems, a webhook delivers each one as JSON: the page, a summary of the change, the removed and added lines, and the rule's verdict.
On Website Change Tracker, every destination comes with every plan: email, text, WhatsApp, Slack and webhooks.
The Slack setup takes a few minutes: how to get a Slack notification when a website changes.
