Track website changes without checking pages by hand
WebsiteChange checks the public pages you care about on a schedule you choose, throws away the noise and tells you in one line what really changed. Below is every step a check goes through, in the order it happens, so you know what to expect before you add your first URL.
Seven steps from a URL to an alert
Each monitor follows the same path every time it runs. Nothing is hidden and nothing is guessed.
-
1.Add a URL
Paste the address of a public page, for example a competitor's pricing page, a vendor's terms of service or a regulator's guidance page. You can watch the whole page or just one part of it.
-
2.Pick an element if you want one
Click the part you care about on the first snapshot, or type a CSS selector. Watch only the pricing table, only the job list or only the stock badge, and everything else on the page is ignored.
-
3.Choose a schedule and a sensitivity level
Set how often the page is checked and how big a change has to be before it counts. A pricing page may need hourly checks, a privacy policy is fine weekly.
-
4.Fetch, render and store
Each check loads the public page, renders it the way a browser would and stores three things: the visible text, the HTML structure and a full-page screenshot.
-
5.Compare and filter
The diff engine compares the new version with the last one and removes what does not matter: dates, counters, rotating banners, cookie bars, tracking parameters and any ignore rules you set.
-
6.Summarize and score
When a real change is left after filtering, an AI model writes a short summary, for example "Pro plan price raised from 79 to 99 USD per month; annual discount removed", and scores its importance as low, medium or high.
-
7.Alert and keep the record
The alert goes to email, Slack, Microsoft Teams or a webhook, right away or in a daily or weekly digest. Every version stays in your history with its screenshot, text diff and visual diff.
Why most checks end quietly
Most pages change a little every time you load them. A clock in the footer moves, a "3 people viewing" counter ticks, a hero banner rotates, a cookie bar appears, a link gains a new tracking parameter. If every one of those raised an alert, you would mute the tool within a week.
WebsiteChange strips these out before anything else happens. What is left is compared again, and only a change that survives the filter moves on to a summary and an alert. Your own ignore rules sit on top: skip a section, a selector or a pattern of text you already know is irrelevant.
The result is simple. A competitor that rewrites its homepage headline gets your attention. A competitor whose footer says a different year does not.
- Dates, times and relative times like "2 hours ago"
- Visitor counters, stock tickers and rotating testimonials
- Cookie bars, consent overlays and chat widgets
- Tracking parameters added to links
- Ignore rules you add per monitor
Sensitivity levels you can tune per monitor
Sensitivity decides how much of the filtered content must differ before a change counts.
- Low catches only larger edits, such as a removed section, a new plan or a rewritten paragraph.
- Medium is the balanced default for most business pages.
- High catches single words and numbers, which is right for a price, a date in a contract clause or a stock status.
You can change sensitivity at any time without losing history. If a monitor feels too chatty, lower it, or narrow it to one element with website change detection rules.
How often each plan checks
The fastest interval depends on your plan. Every plan can also check daily or weekly, which keeps check usage low for slow pages.
| Plan | Fastest interval | Checks per month |
|---|---|---|
| Starter | hourly | 15,000 |
| Growth | every 15 minutes | 75,000 |
| Business | every 5 minutes | 300,000 |
| Enterprise | every 2 minutes | 1,500,000 |
Checks are counted as usage within your billing period. Deleting a monitor does not return the checks it already used. A page checked hourly uses about 720 checks a month, a page checked daily about 30, so mixing schedules lets you watch many more pages on the same plan.
Public pages only, and we say so plainly
WebsiteChange reads pages that anyone can open without an account. We never log in on your behalf, never store your passwords for other sites, never solve CAPTCHAs and never get around paywalls or access controls.
If you add a page that sits behind a login, the check shows a clear message: the page asks for sign in, so we cannot watch its content. You will not get a fake snapshot or a silent empty history. You can still watch the public parts of the same site, such as the pricing page, the changelog or the help center.
We respect robots.txt, and we fetch politely: requests to the same host are spaced out so your monitors never put load on the sites you watch.
What you see after a change
Each change opens as one record with the summary, the importance score, the text diff, a page change monitor view with highlighted areas on the screenshot and a link to the previous version. From there you can share it, export it or compare it with any older version in your website archive tools.
Alerts follow the importance score. Send high importance changes to Slack right away and collect the rest in a weekly digest, all set up on the website change alert settings of each workspace.
Questions about how checks work
No. Dates, counters, rotating banners, cookie bars and tracking parameters are filtered out first, and you can set sensitivity and ignore rules per monitor. Alerts can also be limited to medium or high importance.
No. We only read publicly reachable pages and never log in on your behalf. A page behind a login shows a clear message instead of a snapshot.
No. A summary runs only when a real change remains after noise filtering, so quiet checks never use your summary allowance.
As fast as your plan's interval allows: hourly on Starter, every 15 minutes on Growth, every 5 minutes on Business and every 2 minutes on Enterprise, plus the time to deliver the alert.
Watch your first page in under a minute
Paste a public URL, see the first snapshot and a summary of a real change. No card needed for the demo.