Web Change Monitor --:--:-- UTC

Hosted change monitoring

Web Change Monitor

Get notified when a page, API response or feed changes. Each event stores a clear before-and-after view of what changed.

Built by Fabian Wimberger.

Access is by login only. No analytics, no third-party scripts.

Visual picker

Click exactly what you want to track, instead of watching a whole noisy page.

Diff history

Compare old and new values side by side for page text, an API response or a specific element.

Alerting workflow

Get an alert the moment something changes, while your monitor settings stay private behind login.

What it monitors

Page changes, content diffs, selected elements, APIs, and feeds.

Web Change Monitor checks the pages, feeds and APIs you care about on a schedule: a changelog, a status page, a single table cell or one field in an API response. Every change is saved with the before and after values, a timestamp and a preview, so your team can see what changed at a glance.

01

Website change monitoring

Watch a specific element, a full page, release notes or a status page without checking every link by hand.

02

API and feed monitoring

Works just as well outside the browser: point it at an API field, a feed entry, or any text value you need to track.

03

How it works

Add a page or API address, pick what to watch (the whole page, one element or a specific field) and set how often to check. Every change is logged with the old and new value, so you always have a dated history.

Questions

Common questions about the monitors.

01

Can it monitor only one part of a page?

Yes. Use a CSS selector for a specific headline, price block, table cell, availability label, release-note section, or any other stable element. This keeps navigation changes, footer updates, cookie banners, and unrelated layout changes out of the review queue. If the page structure changes, the stored snapshots make it easier to see whether the selector should be adjusted.

02

Does it work for APIs and feeds?

Yes. JSON paths, regular expressions, plain text, and raw HTML checks cover endpoints that are not normal rendered pages. That makes it useful for status APIs, vendor feeds, changelog RSS feeds, version endpoints, and small internal JSON documents where one value is more important than the whole response body.