Website Change Monitor
Private owner workspace · No paid API
Keep an eye on important page changes
Website Change Monitor compares scheduled captures of administrator-selected public pages. It records changes to page titles, descriptions, canonicals, robots directives, headings, response details and normalized page text.
This is an owner-managed tool. Monitoring targets and history are private. Visitors cannot start background checks or view another site owner’s results from this page.
Choose and enable a target
An administrator adds an authorized public page and explicitly enables its schedule. The first successful capture establishes a baseline, not a false change alert.
Review evidence, not guesses
Compatible captures are compared in a private dashboard. Failed requests remain failures. Retained text has a size cap, and coverage notes explain what was captured.
Control history and notifications
Administrators can pause targets, run bounded manual checks, set retention, delete data and optionally enable email. Email is off unless explicitly selected.
What this monitor does—and does not do
Checks use initial HTML and HTTP evidence. They do not render JavaScript, take visual screenshots, confirm Google indexing, edit page content, or archive complete websites. WordPress scheduled checks depend on page traffic or an existing cron runner, so they are not a guaranteed real-time uptime service.
Public-address, redirect, robots and request limits remain in place. No API key or paid monitoring subscription is required by this module.
Questions about Website Change Monitor
Can visitors monitor arbitrary websites here?
No. Monitoring targets and history are private and managed by authorized site administrators. This public page does not accept background monitoring requests or expose stored captures.
Does it check pages at exact scheduled times?
No. WordPress scheduled tasks depend on site traffic and server availability. The dashboard shows last attempts, next due times and overdue checks; intervals are not a delivery guarantee.
What changes can it detect?
It compares compatible successful server-HTML captures for title, description, headings, canonical and robots directives, final response URL/status, and normalized main text. It does not render JavaScript or prove indexing or ranking changes.
Are captured pages stored permanently?
No. Private bounded snapshots and history follow administrator-set retention and record limits. Deleting a target removes its stored history; a separate confirmed purge clears all monitor targets and data.
Does monitoring require a paid API?
No. This module uses protected public-page retrieval and a locally bundled open-source diff library. Email alerts are optional, off by default, and use the site’s existing mail delivery.