How to monitor a webpage for changes without false alarms
Published 3 October 2026
Setting up a watch on a page takes a minute. Setting it up so it only speaks when something you care about happens is the part people get wrong. A watch that reacts to everything is as useless as one that reacts to nothing: you stop reading the emails.
This guide is about that choice. It uses one real page throughout, the Python downloads page, and shows what Osmanth Watch actually answered when we pointed it at that page on 3 October 2026.
Start from the question, not the page
Before you paste anything, finish this sentence: "Tell me when…". The ending decides how narrow the watch should be.
- …a number changes. Watch a price. You can ask for "below" a number you choose, "above" one, or simply for any drop or rise.
- …something is available. Watch stock: back in stock, or sold out. Getting notified when an item is back in stock goes through that on its own.
- …a word shows up. Watch for words appearing or disappearing.
- …a section is edited. Watch one part of the page.
- …anything real changes. Watch the whole page, for example to get notified when a website changes without knowing in advance what will change.
The narrower the question, the fewer false alarms. The whole-page watch is the broadest and the easiest to start, and it is the one most likely to tell you about things you don't care about.
Whole page or one part
When we asked for "this page changes" on the Python downloads page, the answer was a reading of "1180 lines (18,066 characters) of content" from the page's main content. That is a lot of page to be watching if you only care about one corner of it.
The same page, read for the same request, also returned the blocks it could see and offered them as things to watch instead. These are some of the labels it listed, with the start of each block's text:
| Block it found | Text it starts with |
|---|---|
| Active Python releases | "Active Python releases For more information visit the Python Developer…" |
| Release schedules | "Release schedules Python 3.16 release schedule Python 3.15 release schedule…" |
| 3.15 | "3.15 pre-release Download 2026-10-01 (planned) 2031-10 PEP 790 3.14…" |
If what you care about is the release schedule, you pick that block and the watch ignores the rest of the page. In the app this is under "Not quite right? Change what we watch", then "One part of the page". If you would rather keep the whole page but only hear about changes that mention something specific, "Any real change to the page" has an optional box for words the new content has to mention.
Words: two mistakes that cost people a week
The "some words appearing" watch is the most precise one, and it has two traps. We hit both of them on that same page.
Mistake one: not marking the phrase. We typed the words Python 3.15 appear, with no quotation marks. Osmanth Watch's built-in rules couldn't read it as a phrase, and instead of guessing it said so: "Could not interpret this request with built-in rules", and asked us to choose what kind of event to watch for. The fix is small. Put the exact words in quotation marks: the words “Python 3.16” appear. That version was understood straight away as "Alert when “Python 3.16” appears".
Mistake two: choosing words that are already there. Look at what came back for that quoted request. The reading at setup was "“Python 3.16” is on the page", and the evidence it showed was the line "Python 3.16 release schedule". The words were already on the page when we asked. A watch for words appearing is about the moment they go from absent to present, so when they are already present the watch has nothing to wait for. The app tells you this plainly at setup: "This is already true right now. You'll get an email the next time it becomes true after changing back."
So choose words that are not on the page yet, and that you would only expect to see once the thing you're waiting for has happened.
What keeps the noise down
Two things are built in, and it helps to know they are there.
First, when you ask for a change to the whole page, the product says it is looking for "meaningful content changes (ignoring timestamps, ads and page chrome)". A clock that ticks or an ad that rotates is not a change worth an email.
Second, the first reading is only a starting point and never an email, and a change to the page is read twice, about ten minutes apart, before you are told. If the second reading doesn't agree with the first, nothing is sent.
What to expect once it's running
You confirm your email, and from then on the page is read on a schedule. On the free plan that is once a day. You get one email the first time the thing happens, with what changed, and not one every time we look. If we can't read the page at some point, the watch says "we don't know" rather than "not yet", so silence never quietly means something is wrong. The limits are written out in the terms in plain language.
When you're ready, paste your page on the home page and read what it says back before you give it an email address. The reading you see at that point is the one the watch will start from.