How to get notified when a website changes

There's a page you keep checking. A product that's out of stock, a price you're hoping will drop, a job board, a form that says applications open "soon." The whole reason you're watching is to catch the one moment it changes, and that moment doesn't wait for you to hit refresh. Find out a few hours late and you might as well not have been watching at all.

You can hand that watching to a tool that loads the page for you and tells you the moment something changes on it. What decides whether that's genuinely useful, though, is the alert itself: where it reaches you, how soon, and whether it says enough for you to act without dropping everything to go and look. That is what this guide is about. (New to this? Our guide to monitoring a website for changes covers setting the monitor up; here we focus on the alert.)

What you can actually be alerted about

"The page changed" is rarely what you want to hear. Pages change constantly. A timestamp ticks over, a "customers also viewed" row reshuffles, a promo banner rotates, a view counter climbs. If every one of those fires an alert, you stop reading the alerts inside a day. So the first thing worth getting right is scope: what counts as a change worth telling you about.

Two choices shape this. The first is what part of the page you watch. You can watch the whole page, or click a single element and watch only that, which is the difference between hearing about everything and hearing about the one number or status line you care about. The second is sensitivity. "Any change" alerts you the moment the watched area moves at all, which is what you want for a stock flip or a price you don't want to miss by a hair. A custom percentage threshold tells the monitor to stay quiet until the page has changed by more than a set amount, which helps on a busy page where small cosmetic edits aren't worth an alert. Use that one with care, though: set the threshold too high and a change you actually care about, like a single price moving on an otherwise large page, can fall under the bar and never reach you. When in doubt, keep it low and raise it only if the noise turns out to be real. Getting these two right at setup is most of the work of getting clean alerts later.

Where the alert reaches you

An alert only helps if you see it in time, and the right channel depends on who you're watching for.

• Watching for yourself - if it can wait, email keeps a searchable record; if you want it the moment it happens, a Telegram push hits your phone.
• Watching for your team - send it to Slack or Microsoft Teams so everyone sees it at once. Here's the wiring.
• Watching with a community - drop it in Discord, where the group already is.
• Feeding it to another system - point a webhook at your own endpoint to log it, open a ticket, or trigger a script.

Each monitor sends to one channel, so route each page to wherever you'll actually catch it: a low-stakes page to email, the one you can't miss to your phone or a shared channel.

Cutting the noise so the alerts stay worth reading

The fastest way to ruin a monitoring setup is to drown the signal. An alert that fires on every trivial edit gets the same treatment as a noisy smoke detector: you tune it out, and then you miss the one that mattered. Beyond watching a single element and setting a sensible sensitivity, there's one more layer worth knowing about.

Webtingle can also take a condition written in plain words and hold the alert until that condition is actually met. Instead of "tell me when this element changes," you write something like "only when it's back in stock" or "only when the price drops," and its AI reads each change and stays quiet until that's what happened, ignoring the unrelated edits to the same spot. The ones it holds back aren't lost, though: every change still lands in the monitor's history, so you can scroll back any time and see exactly what changed and when, you just weren't pinged for it. When your problem is too many alerts rather than too few, that's the cleanest fix there is.

Choosing how often to check

How soon you hear about a change is up to you, and it comes down to how often the monitor checks the page. A monitor loads the page on a schedule and compares each version against the last one it saw, so you'll hear about a change on the next check after it happens. You set that pace per monitor, from a few times a day down to as little as every couple of minutes on the top plan.

It's worth matching the interval to how fast the page actually moves. A flash sale or a hyped product drop earns the tightest interval you can give it. A competitor's about page or a regulatory notice barely changes, so a daily check keeps you just as informed. Every account gets a monthly pool of checks to spread across its monitors, and matching each one to its page's pace is how you get the most out of that pool.

The weekly schedule helps here too. If the change you're waiting on only happens during business hours, or only on weekdays, you can tell the monitor to watch just then. It won't spend checks at 3am, and you won't get pinged outside the hours you care about.

What a good alert actually tells you

When the alert does fire, it should let you decide whether to act without making you go open the page yourself. A bare "something changed" message fails this; you still have to drop what you're doing and investigate, which for a false alarm is exactly the cost you were trying to avoid.

Webtingle's alert carries a side-by-side comparison of the page before and after, with the change highlighted, so you can see the actual difference in context: the old price next to the new one, the "out of stock" line replaced by a live buy button, the new clause added to the terms. That context is what tells you whether to move now or let it go, because pages lie in small ways. A button can go live while the variant you wanted is still gone, or a "new" post can be a quietly edited old one. Seeing the diff settles it at a glance. On the higher plans, a short AI summary of what changed rides along with the alert too, which is a fast way to triage a stack of them and only open the full comparison on the ones that earn it.

Putting it together

Say you're flat-hunting in a tight market, the kind where a good listing is gone within hours of going up. You'd point a monitor at the search-results page filtered to what you actually want, the right area, price, and number of rooms, and set sensitivity to "any change" so a new listing trips it. Check every few minutes through the day, when agencies tend to post, and narrow the schedule to those hours so you're not spending checks overnight. Route it to a Telegram push, and the moment a place appears your phone buzzes and you can be first to email the agent, while everyone relying on the portal's daily round-up is a day behind. When the alert fires, the before-and-after shows you the new listing straight away, so you can tell it's a real result and not just the page reshuffling what was already there.

The pieces are the same whichever page you're watching: pick what to watch, decide how sensitive it should be, match the interval and schedule to how fast the page moves, and send the alert wherever you'll actually see it. For a step-by-step walkthrough on a product page, our post on setting up restock alerts runs through the same choices.

Get your first alert set up

The alerting layer is what turns a page you're vaguely keeping an eye on into something you can stop thinking about, because you trust it to reach you when it counts. Set it up once and the page tells you when to look, instead of you checking on the off chance something moved.

Start free with Webtingle. 14-day trial, no credit card. If you're new to website monitoring, start with the quick setup guide and then come back to dial in your alerts.