How to Check a Page Automatically as Soon as It Is Saved

Most broken layouts don’t happen at 3 a.m. They happen when someone edits a page: a block pasted into the wrong column, an image that’s far too big, a page-builder section that falls apart on mobile. A Monitoring schedule finds that eventually, maybe hours later. By then a client or a visitor may have seen it first.

With Check when a page is saved, WebChange Detector checks exactly the page that was edited, a few minutes after it was saved, and compares it with its last Monitoring screenshot. You know within minutes whether the edit changed more than intended. And because only edited pages are checked, pages nobody touched cost no checks at all.

How page-save checks work

  • It waits until you’re done editing. The check runs about five minutes after the last save. If the editor keeps autosaving while you work, it waits until there have been five quiet minutes. A long editing session gives you one check, not one per save.
  • Only real changes count: title, content, excerpt, page-builder layout or featured image of a published page or post. Autosaves, drafts, imports and saves by scripts or scheduled tasks don’t start a check.
  • Only pages you monitor are checked. The saved page must be selected in the website’s Monitoring.
  • Everything else works as usual: our AI verification, alert emails and webhooks. Each check counts like any other Monitoring check.
  • It works next to your schedule or on its own. Keep your interval and get page-save checks on top, or set the schedule to Never and only check pages when they are saved.

Before you start

  • The WebChange Detector plugin, version 4.6.0 or newer, is installed and connected on your WordPress website. The site tells us about a save right when it happens, which is why this needs the plugin.
  • The website has Monitoring switched on, and the pages you care about are selected for Monitoring.

Step 1: Open the website settings

In your dashboard, open Monitoring 1. Find your website in the list and open its actions menu with the three dots 2, then choose Website Settings.

Monitoring tab of the WebChange Detector dashboard with the website list and the actions menu of a website

Step 2: Switch on “Check when a page is saved”

Switch on Check when a page is saved 1 and click Save 2. Your schedule stays as it is: the website is still checked at the chosen interval, and additionally after every save.

Website Settings with the schedule options and the switch "Check when a page is saved"

If the switch is greyed out with the note Needs the WebChange Detector plugin on this website, the site isn’t connected through the plugin. If you see Takes effect once the site runs plugin v4.6.0 or newer, update the plugin on that site first.

Want checks only after a save and none on a schedule? Choose Never under Run in intervals and keep the switch on. In the list, the website then shows On page save instead of an interval and When a page is saved as the next check. Websites that have both show + on page save under their interval.

A website in the monitoring list that is checked only when a page is saved

Many client sites? Bulk Changes on the Monitoring page switches Check when a page is saved on for many WordPress websites at once.

Or switch it on in WordPress

You can do the same in WordPress: open WebChange Detector → Monitoring 1. The button Run monitoring now 2 on the same page is the manual counterpart: it checks all selected pages right away, for example after you pushed a whole staging site live.

WebChange Detector Monitoring tab in WordPress with the monitoring status and the "Run monitoring now" button

Further down in Monitoring Settings, tick Check when a page is saved 1 and click Save Settings. The option appears once Monitoring is switched on.

The setting "Check when a page is saved" in the WebChange Detector plugin

Step 3: Save a page as usual

Nothing changes in how you work. Edit a page in the block editor (or your page builder) and click Save 1. About five minutes after your last save, WebChange Detector checks exactly this page.

The Save button of the WordPress block editor after a page was changed

Step 4: Review the result

In your dashboard, open Monitoring, click Next Monitoring Checks and then Recent results. The check run that the save started is listed with its AI summary 1. Click Checks to open it.

Recent monitoring results with the check run that was started by saving a page

The run is labelled with the saved page and who saved it 1, for example Page saved: About us (by Anna), so you always know which edit caused a change.

Checks of a run started by a page save, with the detected change

Good to know

  • Saving a page without changes does nothing. Drafts are not checked: the page must be published.
  • A page that has no Monitoring screenshot yet gets its first screenshot as the starting point. The comparison starts with the next save or scheduled run.
  • If a scheduled Monitoring run starts within 15 minutes anyway, it takes over, so the page isn’t checked twice.
  • Built-in brakes keep a busy day affordable: at most 60 saved pages per website and hour are checked, and a bulk edit of many pages is capped as well.
  • Alerts work as usual: if the check finds a change, you get the Monitoring alert email.

WebChange Detector Newsletter

News, feature Updates, and insights.
No spam. Unsubscribe anytime.