How to detect website changes and stay on top of them.
Updated October 26, 2026 · 6 min read
A plugin update changes the page title, the phone number disappears from the legal notice, foreign code shows up on the homepage. Changes like these often go unnoticed for weeks, usually until someone complains. This guide shows how to detect website changes automatically, which method fits which job and how to avoid false alerts.
Contents
When change monitoring pays off
A website changes all the time, mostly on purpose. The tricky changes are the ones nobody notices because the page stays online. Typical cases:
- CMS, theme and plugin updates: texts, menu items or forms disappear without the page going down.
- SEO settings: a deployment accidentally sets "noindex" or changes the page title, description or canonical. Search engines react, visitors notice nothing.
- Legal pages: the legal notice, privacy policy and terms should only change on purpose. A dated history shows which version was online when.
- Prices and product pages in your own shop: you see when a price, a delivery note or an offer changed.
- Security: injected code, foreign links or a swapped script are often the first signs of a compromised system.
Three methods compared
Change detection tools work on one of three principles. They differ mainly in how well you can trace what actually changed.
| Method | Detects | Strengths | Weaknesses |
|---|---|---|---|
| Screenshot comparison | Changed rendering | Sees layout and images | False alerts from animations, cookie banners and ads; hard to tell what exactly changed |
| Text and source comparison | Text, HTML and CSS | Traceable line by line, little noise, easy to archive | Content that only appears through JavaScript in the browser is missing |
| Keyword check | Whether a specific text is present | Simple, ideal for error pages | Only catches what you defined in advance |
Avoiding false alerts
Change monitoring is only as good as its signal. If you get ten meaningless messages a day, you will miss the one that matters. These settings help:
- Narrow it down: with a CSS selector such as #pricing or main, only the part of the page you care about counts.
- Ignore changing lines: dates, times, visitor counters or "last updated" belong on an ignore list.
- Compare the right thing: the visible text is enough for content. Design and source are worth it if layout changes or new scripts matter to you.
- Bundle messages: at most one message per hour that sums up all changes since the last one.
- Filter technical noise: security tokens, tracing IDs and invisible hyphens change on every fetch and say nothing about the content.
How often should you check?
It depends on how quickly you need to react. For legal pages and subpages that rarely change, daily or every six hours is enough. Check the homepage, prices and campaign pages hourly. Every 15 minutes pays off for pages where every hour counts, for example after a big update or during a sale.
More important than a short interval is a history: only stored versions let you prove later what was online when, and compare any two states with each other.
Only your own pages, or with consent
Monitor pages you own or for which you have the operator’s consent, such as client projects. In Clesk Uptime you confirm this when you create a monitor.
Setting it up in Clesk Uptime
Under "Changes" you pick a monitor or create a new one, decide what counts as a change (visible text, design as well, or the full source) and how often to check. Clesk Uptime stores the first version right away and notifies you as soon as something changes afterwards. In the history you compare every version as text, HTML or CSS.
One page is free on the Free plan. Pro covers 10 pages and Business 50, each with checks as often as every 15 minutes.
Frequently asked questions
Does it detect changed images?
Through the source: if the address of an image changes, the comparison shows it in the HTML. If an image is replaced under the same address, that stays invisible; it would take an image comparison.
What about pages that only load through JavaScript?
Content that only appears in the browser is not captured by a source comparison. Often there is a subpage or an API with the same data, though. Clesk Uptime compares JSON responses indented, so field by field.
Does change monitoring replace a backup?
No. It stores the text, HTML and CSS of individual pages to make changes visible. It does not back up databases, images or files.
Your first page is free to monitor.
Text, HTML and CSS as versions, notifications by email. No credit card needed.