Osmanth WatchAn Osmanth product

Osmanth Watch / Guides

How to get notified when an official page is updated

Published 13 October 2026

Short answer: if the agency offers an email alert for the page or the topic, use that. It is the source telling you directly. If it doesn't, a page watcher can read the page every day and email you when its content changes, but it needs a page whose text is in the page itself, and it can't tell you why the page changed.

Visa rules, exam timetables, travel advice and applications that open on a date are the kind of thing an official page changes without a headline. You don't want to open the page every morning, and a missed change can cost you a deadline. This guide is about getting told, and about checking that what you set up can really see the change.

Start with the official alert

Many official sites send their own updates, and those are better than anything a third party can do, because the agency knows when it publishes.

GOV.UK is one example. Its help page says that you can get email updates about topics, some individual pages, departments, agencies and public bodies, foreign travel advice, and news and communications (GOV.UK). Its publishing manual says the "get emails about this page" button was rolled out to most Whitehall publications, consultations and detailed guides on 1 March 2022, with a small list of pages excluded (GOV.UK Publishing Manual). That page is written for GOV.UK's own staff and was last updated in July 2025, so treat the date as history, and look for the link on the page you care about.

Other countries' sites vary. Look for words like "subscribe", "email alerts" or "get updates" on the page or on the agency's home page before you reach for anything else.

When a page watcher helps

A watcher helps when there is no alert, when the alert covers a whole topic and you care about one page, or when the page isn't on a site that offers alerts at all. It reads one public page on a schedule and emails you when its content changes. How to get notified when a website changes goes through that choice in general.

On an official page, three things are worth knowing.

It watches the text, not the date. Pages often say "Last updated" with a date. Osmanth Watch treats dates and times as the same from one reading to the next, so a page that changes only a date or a time is normally not counted as a change. You are told when the content changes.

It tells you what changed, in lines. The email says how many lines were added and removed and lists them, up to ten of each. It can't tell you whether a new line is important.

It reads a change twice. A change to a page is read again about ten minutes later, and only emailed if both readings agree.

What we tested

Readings from the live product on 10 October and 13 October 2026, run from the same network as the production server. In every case the request was "tell me when this page changes" unless it says otherwise.

Two results taught us more than the successes did.

Watching for the word "Updated" does not work on that GOV.UK page. We asked for the words “Updated” appear on the Standard Visitor page. The product set it up, with the reading "“Updated” not on the page". When we looked at the page's source, the word "updated" appears there only in two hidden metadata tags that visitors never see. The page does not print the word in its visible text. So a watch for that word would wait for something that is not coming. Watch the content of the page instead.

A central bank's press-release page read as almost nothing. For "tell me when a new announcement is posted" on the Federal Reserve's press releases page, the product answered "Alert when the page publishes/announces something new", with the starting reading "43 lines (372 characters) of content", and on 13 October it said it could check the page reliably. That is a small reading for a page whose job is to list releases. We looked at the page's source: it contains no links to individual releases, and it loads a script that appears to fill the list in. We also loaded the page in the product's full-page mode, and the list was still not there. A watch on that page would see the page around the list, but not the releases. We did not look for another page on that site that lists the releases in plain text.

That "reliably" was wrong, and we fixed it the same day. The same page now answers "We could read only a small amount of text from this page (372 characters), so the part you care about may be missing from what we can see.", marks the watch as unsure, and suggests trying another page of the site that shows the list as plain text. You can still start it, but you are told first. A very small page that is genuinely small gets the same notice.

On 13 October 2026 we also ran the product's own decision code on made-up readings. A plain "this page changes" watch that gained one line reported "The page content changed: 1 line(s) added, 0 removed" and held it for a second look. We have not yet watched a real official page change through the product, so we can't show you a real alert for one.

Check the reading before you start

The most useful habit is to look at the starting reading. It says how many lines and characters the watcher sees. If that is a lot smaller than the page you are looking at, the content you care about probably isn't in what we can read, and no setting will fix that. That was the case for the press-release page, and the product now warns you about readings that small, but the warning only catches the extreme cases, so compare the reading with the page yourself. If you can see a similar page on the same site that shows the list in plain text, such as an archive or a topic page, try that one.

Limits to plan for

Starting one

Paste the official page on the home page, say what you are waiting for, for example tell me when this page changes, and read the starting reading before you give an email address. To watch one section of a long page rather than the whole thing, see how to monitor a webpage for changes. The limits are written out in the terms.

Sources

More guides