Website change alerts: 3 ways to get them
You've got a page that matters: a product that might come back in stock, a price that might drop, a tender portal, a competitor's pricing table. Refreshing it yourself covers the moments you remember to do it, and the change is free to land in any of the others - overnight, say, or on the Saturday you finally stopped checking. What you actually want is website change alerts - something that watches the page and taps you on the shoulder when it moves.
There are three ways to get those alerts, and they differ a lot in what they cost and what they miss. Worth saying first: if the page changes quarterly and a day late costs nothing, a bookmark and a calendar reminder will do - no tool needed. The methods below are for the pages where that stops working. And if you already know you want a monitor and just need to set one up, the step-by-step setup guide is the faster read.
1. Install a browser extension
Extensions like Distill Web Monitor or Visualping's sit inside your browser, re-open the page on a schedule, and pop a page change alert as a desktop notification when something moved. Setup takes a couple of minutes: install it, open the page, click the part you want to watch. Both have free tiers, capped on how many pages you can watch and how often they check, and that's plenty to find out whether the approach suits you.
For quick, low-stakes watching at your desk, they're a solid tool. The catch is baked into where they run: the checks happen in your browser, on your machine. Close the laptop, quit the browser, or head out for the weekend and the checking stops with you. The notification also pops on the machine doing the checking, so an alert that fires while you're out just waits on a screen nobody is looking at.
Every extension shares that ceiling; it comes with running client-side. The vendors know it too, which is why most of them also sell a cloud version that checks from their servers instead - at which point you're comparing hosted services, which is method three.
Pick an extension when the page only matters during hours you're at the computer anyway, and missing a change is an annoyance rather than a loss.
2. Write a script
If you're a developer, the temptation is real: curl the page, diff it against the last copy, send yourself an email, wrap it in cron. For a static page, that genuinely is an afternoon of work. Self-hosting an open-source tool like changedetection.io is the more polished version of the same idea, with a UI on top and Docker doing the setup.
The control is the draw. You can watch pages on your intranet, which hosted tools can't see from the public internet, apply logic no product exposes, and pay nothing but hosting. For internal dashboards and custom workflows, DIY is often the only practical route.
What the afternoon estimate hides is the maintenance. Modern pages render through JavaScript, so curl sees an empty shell and you graduate to a headless browser. Sites change their markup and your selector silently starts watching nothing. Anti-bot measures appear. And the alert plumbing - the part that actually reaches you - is its own project: SMTP credentials, a webhook receiver, retry logic for the night your script died and said nothing.
The scheduler needs care too. If you'd rather not babysit a server, a scheduled GitHub Actions workflow can run your check for free, but GitHub's own documentation caps schedules at every 5 minutes and warns that runs can be delayed or even dropped during high-load periods. For a weekly check of a slow page, that's irrelevant. For a restock that sells out in twenty minutes, it's the whole game.
Build it yourself when the page is unreachable from outside, the logic is genuinely custom, or you'll enjoy the project enough that the maintenance is part of the fun.
3. Use a hosted monitoring service
The third method moves the watching to someone else's servers. A hosted monitor like Webtingle loads the page on a schedule around the clock, compares each version to the last, and sends the alert through a channel that reaches you wherever you are: email, Slack, Telegram, Discord, Microsoft Teams, or a webhook into your own system. Your laptop can stay closed the whole time, because none of the checking happens on it. That covers your phone too - a plain email or a Telegram push lands there without any extra app to install.
The setup is the same couple of minutes as an extension: paste the URL, click the element you care about, choose one of the channels you've connected. Checks can run as often as every couple of minutes for pages that move fast, or daily for ones that barely move. When something changes, the alert carries a before-and-after comparison with the difference highlighted, so you can tell a real restock from a reshuffled "related products" row without opening the page. You can even hold alerts behind a plain-language condition like "only when it's back in stock", which removes most of the false alarms the other methods leave you to filter out yourself.
There are honest trade-offs here too. Several hosted monitors have free tiers, but they come with tight limits - a few pages, infrequent checks, basic alerting. More pages, faster checks, and the smarter features are where the subscription starts. You're also trusting a third party to do the watching, and pages on a private network are out of reach - that one stays DIY territory.
Choose hosted when missing the change actually costs you something, when the alert has to reach your phone or your team rather than a desktop, or when the page does its moving at 2am.
What about Google Alerts or an RSS feed?
Two free tools come up in every conversation about this, so it's worth placing them. Google Alerts watches Google's index for new pages that mention a phrase. It's useful for tracking a topic or your own brand, but it won't tell you that one specific page changed, and it knows nothing about prices or stock. An RSS feed solves a different slice: when a site publishes one, any feed reader will hand you new posts for free. The catch is that the pages people most want to watch, like product pages and booking calendars, almost never offer a feed. If what you need is an alert when a webpage changes - that page, specifically - you're back to the three methods above.
Which one should you pick?
Match the method to the page, not the other way around:
| Method | Cost | Checks with your machine off | Reaches your phone | Upkeep |
|---|---|---|---|---|
| Browser extension | Free tier, paid above it | No | No | Low |
| DIY script | Your time, plus a little hosting | Yes | Only if you build it | High |
| Hosted service | Limited free tiers; subscription for full features | Yes | Yes | Minimal |
In short: for a low-stakes page that only matters while you're at your desk, an extension earns its keep. A page inside your network is script territory, since hosted tools generally can't reach it. And when missing the change costs real money, or the alert has to reach your phone or your team, hosted monitoring is the one that keeps working with your machine off and you elsewhere.
Mixed setups are normal, by the way. Plenty of people watch two hobby pages with an extension and put the one that costs real money on a hosted monitor. If that one page is a restock or a price, we've written up the exact setups: back-in-stock alerts and price drop alerts.
Whichever method you land on, the part that decides whether it was worth it is the alert itself - where it reaches you and whether it says enough to act on. That layer has its own guide: how to get notified when a website changes.
And if the hosted route sounds like the right fit, start free with Webtingle - 14-day trial, no credit card. Point it at the page you're tired of refreshing and let it do the checking.