A plugin update ships overnight. Your checkout page breaks. You find out three days later from a customer complaint.
This is exactly the scenario Auto Update Checks are built to prevent. WebChange Detector takes screenshots of your site before and after every WordPress auto-update, compares them, and emails you what was updated and what changed, all without you doing a thing.
This tutorial covers every setting, walks through the full update cycle, and shows you where to check afterwards what actually ran.
How it works
Auto Update Checks hook directly into WordPress’s built-in auto-update process. Here is the exact sequence:
- WordPress has an auto-update to install (plugin, theme, or core)
- WebChange Detector steps in and takes before screenshots of your selected pages
- WordPress runs the update
- WebChange Detector takes after screenshots of the same pages
- The two sets are compared
- You get an email with the updates and the results
You configure it once. After that, it just runs.
Which updates trigger it?
- WordPress core, when WordPress is allowed to update it automatically
- Plugins: only the ones you have enabled for auto-updates in WordPress
- Themes: same, only the ones set to auto-update
Heads up: This only works for auto-updates. If you click “Update” yourself in the WordPress dashboard, that update isn’t checked automatically. For manual updates, use an On-Demand Check instead.
Before you start
Make sure you have these in place:
- WebChange Detector plugin installed and connected: your API token is saved in the plugin settings. Not there yet? Start with the plugin for WordPress
- At least one auto-update enabled in WordPress: check under Dashboard > Updates or look for “Auto-updates enabled” in your Plugins list
- At least one URL selected for checks
- Checks available on your WebChange Detector account
Where to find the settings
In your WordPress admin, open WebChange Detector → On-Demand Checks. The box WP Auto Update & On-Demand Checks Settings holds everything below. The main switch is Auto Update Checks 1.
Every setting explained
Auto Update Checks (on / off)
The main switch. Turn it on and WebChange Detector checks every auto-update. Turn it off and WordPress updates run as normal, without checks.
This only does something if WordPress has auto-updates enabled. No auto-updates configured in WordPress means nothing to check.
Some hosting tools switch WordPress auto-updates off for the whole site. The plugin notices this and tells you on this page. If it’s safe on your site, you can switch them back on with Re-enable WP auto updates. Only do this if no other tool is supposed to manage your updates, otherwise two update mechanisms compete.
Auto Update Timeframe
Set a window during which auto-updates are allowed to run. Updates outside this window wait until the window opens again.
- From: Start of the window (e.g., 02:00)
- To: End of the window (e.g., 06:00)
A window across midnight works too: From 22:00 to 06:00 covers 10 PM to 6 AM.
The times are shown in your site’s timezone. Make sure it is set correctly under Settings → General.
Weekdays
Choose which days of the week updates are allowed to run. One checkbox per day, Monday through Sunday. You must pick at least one.
If you only want updates during your weekend maintenance window, enable Saturday and Sunday and leave the rest unchecked.
WordPress Security Updates
Security fixes shouldn’t wait for your weekend window. With Always allow WordPress core security updates (on by default), WordPress security releases (minor core updates) install right away, even outside your timeframe. They install without Auto Update Checks. Plugin, theme and major core updates still wait for the timeframe.
Notifications
Enter the email addresses (comma-separated) that should get the result of every update run. You can also connect Zapier to get the alerts in other apps.
The email is sent by WebChange Detector, not by your WordPress site, so it arrives even if your site’s own mail setup is unreliable. One update run means one email.
What’s in the email:
- The subject starts with [Alert] or [OK] and names the website, so your inbox already shows which runs need a look
- The list of what was updated: WordPress core, plugins and themes, each with the old and new version, plus any update errors
- An AI summary of what changed (on plans with AI verification)
- The changed pages, each with a link to the before/after comparison, and any pages that could not be captured
If WordPress installed nothing in a run, the email says so plainly.
The same box also has Alert emails for On-Demand Checks: the addresses that get an email when an On-Demand Check finds a change.
Difference Threshold
Leave this at 0, as the hint next to the field recommends: our AI already decides which changes matter.
Advanced settings
Basic Authentication (Username / Password)
Staging site behind a password? Enter your HTTP Basic Auth credentials here and the screenshots are taken logged in.
Static IP Proxy
Your site’s firewall only lets known IP addresses in? Switch on the static IP proxy and whitelist the IP shown next to it in your firewall.
Screenshot Region
Where the screenshots are taken from: Auto-Detect (the closest region for your site), United States, or Europe.
Screenshot Delay
The pause between two screenshot starts, so your server isn’t hit by many page loads at once. Leave it empty for the default of 10 seconds, and increase it if your server struggles during a run.
CSS Settings and JS Settings
Hide or fix elements before the screenshot is taken, for example a countdown timer that always looks different. Example:
.live-countdown { visibility: hidden !important; }
Currently enabled auto-updates
Under the main switch, an information panel shows exactly what WordPress is currently set to auto-update: core status, which plugins have auto-updates on, and which themes. Open it to verify your WordPress and WebChange Detector settings are in sync.
Switch on Auto Update Checks from the Web App
Looking after client sites? You do not have to log in to every wp-admin. Once the plugin is installed and connected on a site, you switch its Auto Update Checks on from the Web App and set the same timeframe, weekdays and email there. The checks themselves still run inside WordPress, so a site without the plugin cannot use them, and WordPress auto-updates have to be enabled on the site as described in Before you start.
- Open On-Demand in the dashboard menu and find the website. If its row shows No plugin, install and connect the plugin first: Start with the plugin for WordPress.
- Click the ⋯ button in the website row and choose WP Plugin Settings. The entry is greyed out as long as the plugin is not connected.
- Under Auto Update Settings 1, switch on Auto Updates Checks enabled.
- Tick the days under Do WP auto-updates only on these weekdays and set the hours in Auto update times from and to. Pick a time with few visitors and when somebody can react.
- Enter who gets the result email in Alert emails. Separate several addresses with commas.
- Click Save. The pill in the website row now reads Auto Update Checks · on.
The right side of the window, Plugin visibility 2 and Tabs in WP Plugin 3, decides what your client sees of the plugin: Control What Your Client Sees, or Hide the Plugin Completely.
The pages that get checked are the ones selected for On-Demand Checks of that website, see Which pages get checked?. To switch many sites on in one go, use Bulk changes. And to see every armed site and its next update window, open the Auto Update Checks panel.
Sites you update through MainWP do not use Auto Update Checks. There, WCD Updates do the same job: How to Run WCD Updates with Visual Checks in MainWP.
What actually happens during an update cycle
Step 1: WordPress has updates to install
WebChange Detector waits in the background. When WordPress is about to install an auto-update inside your timeframe, it steps in.
Step 2: Before screenshots
Before a single file gets updated:
- Your site’s caches are cleared, so the screenshots show the real current state (30+ caching plugins and hosting caches are supported, including WP Rocket, W3 Total Cache, LiteSpeed Cache and WP Engine)
- Screenshots are taken of all your selected URLs
- WordPress waits with the update while the screenshots are in progress
- Once all screenshots are done, WordPress proceeds
Step 3: WordPress runs the update
WordPress does its thing. Plugins update, themes update, core updates, whatever was queued.
Step 4: After screenshots and comparison
Once the update is done:
- Caches are cleared again
- After screenshots are taken of the same URLs
- Each after screenshot is compared with its before screenshot
- The results are saved together with the list of installed updates, and the email goes out
Reviewing the results
In WordPress, go to WebChange Detector → Checks and look for the run of your Auto Update Check. Each row shows the URL, device and difference. Click a row to open the full comparison with before/after slider, highlighted differences, and our AI’s verdict.
For a complete walkthrough of the comparison popup, AI verdicts, feedback rules, and review best practices, see: How to Review Checks.
All your sites in the Web App
Looking after many sites? In the Web App, open On-Demand and expand WordPress auto-update checks 1. You see how many sites are armed, under Upcoming 2 the next runs per day, and under Recent results the latest runs with their outcome and AI summary.
Check what ran: the Auto-Update History
“Did the updates actually run last night, and what did they change?” A client asks, your colleague asks, or you just want to be sure. The Auto-Update History is your record: every run the safety net saw, with what was installed and how it went.
- In WordPress, open WebChange Detector → Logs and click the tab Auto-Update History.
- Every run is one entry with its date and a status: Completed, Completed with Errors or Failed, plus how many updates were successful (for example “3 of 3 updates successful”).
- Open an entry to see the details under WordPress Core, Plugins and Themes, each with the version it moved from and to.
- Click View Visual Comparisons to jump straight to the checks of that run.
Some entries explain why nothing was checked:
- Security update: installed without checks: a WordPress security release went in right away (see WordPress Security Updates above).
- Auto-Update Cooldown Active: the last run was less than 12 hours ago, so this one waited.
- WP Auto Updates Disabled: WordPress auto-updates are switched off on the site, so there was nothing to check.
The history keeps the most recent runs. The list of installed updates is also stored with the check itself, so you find it in the results as well.
Which pages get checked?
Auto Update Checks use the same pages as your On-Demand Checks. Choose them on the same page, WebChange Detector → On-Demand Checks, under Select URLs to Check. Currently selected URLs 1 shows how many are on; switch Desktop 2 and Mobile 3 on or off per URL. Step by step: Choose the pages to check.
You don’t need to add every page on your site. Focus on the ones where a broken layout actually hurts: homepage, checkout, contact form, pricing page, key landing pages.
On a WordPress Multisite network
Running a multisite network with the plugin network-activated? Then one update run covers the whole network:
- The timeframe, weekdays and notification email are set once on the main site and apply to every sub-site.
- Each sub-site keeps its own Auto Update Checks switch, which decides whether its pages take part in the network-wide checks.
- The Auto-Update History lives on the main site.
- The email subject names the first site plus how many more were checked.
Network setup, sub-site permissions and everything else multisite: WordPress Multisite Visual Regression Testing.
Reliability features (the stuff running in the background)
A few things worth knowing about how the system keeps itself from getting stuck:
12-hour cooldown: After an update run completes (or fails), the system waits at least 12 hours before running again. No endless retry loops.
After screenshots, no matter what: If an update was triggered outside the normal flow, which happens on some hosting setups, a safety net still takes the after screenshots.
External webhook: WebChange Detector pings your site to make WordPress process its scheduled tasks. This matters on low-traffic sites where WordPress’s scheduled tasks barely run on their own.
AI change verification
On plans with AI verification, every comparison is analyzed by our AI. It marks each changed area as a real alert, as fine (expected dynamic content), or as something for you to look at. The AI verdict shows in the comparison popup and in the alert email, so you can triage at a glance. You can also create feedback rules to teach it about expected changes on your site. See the full details in our review guide.
Set it up once, stop worrying about updates
Auto Update Checks run completely on their own after the initial setup. One email per run tells you what was updated and whether anything changed. No post-update anxiety.
- Install the WebChange Detector plugin and connect your API token
- Select the pages you want to check under WebChange Detector → On-Demand Checks
- Set your update timeframe and add your notification email
- Switch Auto Update Checks on
The next time WordPress auto-updates, you’ll know exactly what changed, before any of your users do.
Troubleshooting
The switch won’t save or is greyed out
Your API token is probably missing or invalid. Go to the plugin settings and check that the token is entered correctly. If that doesn’t help, remove the API token in the settings and add it again.
Updates are running but no screenshots appear
Open the Auto-Update History first: it usually says why (cooldown, WordPress auto-updates disabled, or a security update installed without checks). Also check that your timeframe and weekdays cover the time the updates ran and that Auto Update Checks are switched on.
Too many alerts from things you don’t care about
When our AI marks a change as an alert that isn’t one, click Ignore in future on that area in the comparison. This creates a feedback rule, and in the next checks the same kind of change is marked as OK by your rule. For elements you never want in the screenshot at all (live counters, chat widgets), hide them with CSS under CSS Settings.
Notification emails aren’t arriving
Check your spam folder first, then check that the address under Notifications is correct. The emails come from WebChange Detector itself, so your site’s mail setup doesn’t matter here.
Before screenshots take a long time
Screenshots start one after another with a pause of at least 10 seconds, so your server isn’t overloaded. The way to speed up a run is to check fewer URLs.
Related Guides
- How to Review Checks: The complete guide to the comparison popup, AI analysis, feedback rules, and review workflow
- On-Demand Checks: Before/after comparisons for planned updates you start yourself
- Monitoring: Scheduled checks to catch unexpected changes
- Managing Multiple Client Sites: The Web App for many websites
- WordPress Multisite: Visual checks across a whole network