Check a page the moment it changes.
Most visual breakage happens when someone edits a page or ships a deploy, not at 3 a.m. WebChange Detector checks a saved page minutes after editing stops, and checks every monitored page with one click or one API call after a deploy. No waiting for the next scheduled run.
Pages break when people change them.
Edits land between runs
A schedule checks at fixed times. When an editor breaks a layout in the morning and the next run is in the evening, the broken page stays live until then, and nobody connects it to the edit.
Deploys save nothing
Hosts like WP Engine push staging to production as a full copy. Nothing is saved on the live site, so no save trigger fires. After a deploy you need a way to say: check now.
Quiet pages waste checks
Checking a legal page every few hours spends checks on a page nobody touches. Checked only when it is saved, that page costs nothing until someone edits it.
Start a check without waiting for the schedule.
Both triggers run a normal Monitoring check: the page is compared with its last Monitoring screenshot, with the usual AI verification, alerts and webhooks.
Check when a page is saved
When someone saves a published page or post in WordPress, WebChange Detector checks exactly that page shortly afterwards. Turn it on per website in the plugin for WordPress or the agency dashboard.
- Runs five minutes after the last save. While the editor keeps autosaving, it waits for five quiet minutes, so a long editing session is one check.
- Only real changes count: title, content, excerpt, page-builder layout or featured image. Drafts, imports, WP-CLI and cron saves never start a check.
- Works next to your schedule, or on its own with the schedule set to “Never”.
- Needs the WebChange Detector plugin for WordPress 4.6.0 or newer on the site.
Run Monitoring now
Start a Monitoring check right away for every active page of a website: with the “Run monitoring now” button in the agency dashboard or the plugin for WordPress, or with one API call as the last step of your deploy script.
- Starts immediately, no waiting time. If your deploy purges a cache, purge first, then trigger.
- One run per click, labelled “Manual Trigger” in your Checks list.
- A second click while the run starts or runs gets “already running”, never a double charge.
- Credits are checked up front: if they do not cover the run, nothing starts and you see why.
From a save or a deploy to a verified result.
Set it up once per website. After that, every edit and every deploy gets its own check.
Connect the WordPress site
Install the plugin for WordPress and sync your pages into Monitoring. A trigger only checks pages that are already in Monitoring.
Choose your triggers
Turn on “Check when a page is saved” in the plugin settings or the agency dashboard. Keep an interval next to it, or set the schedule to “Never”.
Someone saves a page
The site reports the save right after it happens, independent of site traffic. The check waits until editing has stopped.
Or you ship a deploy
Click “Run monitoring now” after the push, or add one API call as the last step of your deploy script.
Compared and verified
Each page is compared with its last Monitoring screenshot. AI verification sets harmless changes aside, so only real problems reach your inbox.
See who changed what
In the agency dashboard, each triggered run is labeled with the saved page and the editor who saved it.
Switch it on per website. Keep your schedule.
“Check when a page is saved” sits in the Monitoring settings of each website, next to the interval and quiet hours. Set it for one website, or for many at once with Bulk Changes in the agency dashboard.
- Websites checked only on save show “On page save” instead of an interval. Websites with both show “+ on page save”.
- A scheduled run that starts within 15 minutes takes over, so a page is not checked twice.
- Guard rails for bulk edits: at most 60 triggered pages per website and hour.
- A page without an earlier Monitoring screenshot gets its first screenshot as the baseline.
One API call as the last step of your deploy.
Run Monitoring now for a whole website from any deploy script or CI pipeline. Send the ID of the website’s Monitoring group, the type “manual_trigger” and the scope “all”:
curl -X POST https://api.webchangedetector.com/api/v2/monitoring/trigger \
-H "Authorization: Bearer $WCD_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"group_id": "023c282c-6513-420a-a36b-a654312ab229",
"type": "manual_trigger",
"scope": "all"
}'
To check only some pages, send the scope “url” with a list of up to 50 URLs instead. The answer lists the accepted pages and the ID of the new check run, so your pipeline can follow up or wait for the webhook. The check starts the moment the call returns, so purge or warm your caches first.
There is no hourly cap on Run Monitoring now: your credits are the limit. The endpoint accepts up to 120 requests per minute per account. All endpoints and code samples are on the API & Automation page.
When to use which, and why most teams combine both.
Scheduled Monitoring
Checks your pages at fixed times, whether anyone touched them or not.
- Catches changes nobody on your team made: a hack, a third-party script, an expired element.
- Runs as often as every 15 minutes on Team plans and above, or hourly up to every 24 hours, on chosen weekdays or days of the month.
- Quiet hours pause scheduled runs during your maintenance window.
Triggered Monitoring
Checks a page because something just happened to it.
- Catches what your own team breaks, minutes after the save or right after the deploy.
- Pages checked only when saved cost nothing until someone edits them.
- A good fit for pages that rarely change but must stay right: landing pages, forms, legal pages.
Best of both: a schedule catches what happens on its own, the save trigger catches edits within minutes, and Run Monitoring now closes the gap after a deploy. All three run as one Monitoring, with the same screenshots to compare against, the same AI verification and the same alerts.
What it costs: one check is one URL on one device, desktop or mobile. A long editing session is still one check. Before a manual run starts, the confirmation tells you how many checks it can use, and it starts only when your credits cover it. Compare plan sizes on the pricing page.
Frequently asked questions
Do I need the plugin for WordPress for triggered monitoring?
For checks on page save, yes: the WebChange Detector plugin 4.6.0 or newer reports each save. Run Monitoring now works without it, from the agency dashboard or the API, for any website in Monitoring.
Will a long editing session start dozens of checks?
No. The check runs five minutes after the last save, and while the editor keeps autosaving unsaved changes (block editor, classic editor, Elementor, Divi 4, Beaver Builder) it waits for five quiet minutes. A whole editing session becomes one check, and an autosave never starts a check on its own.
Which saves start a check?
Saving a published page or post with a real change: title, content, excerpt, page-builder layout or featured image. Drafts, imports, WP-CLI and cron saves do not. Only pages that are already in Monitoring are checked.
We deploy by copying staging to production. Does the save trigger catch that?
No, because nothing is saved on the live site. Click “Run monitoring now” after the push, or add one API call as the last step of your deploy script. It starts immediately, so purge your cache first.
Can I combine triggers with a schedule?
Yes. “Check when a page is saved” runs next to any interval, or on its own with the schedule set to “Never”. If a scheduled run starts within 15 minutes, it takes over, so the page is not checked twice.
What does triggered monitoring cost?
One check is one URL on one device. Pages checked only when saved cost nothing until someone edits them. Run Monitoring now checks your credits before it starts, and a second click while a run is going gets “already running” instead of a double charge.
Know within minutes when an edit breaks a page.
Start with a free trial, connect a WordPress site, and turn on “Check when a page is saved” for your first website today.