An alert lands in your inbox at 7:02. You open it, compare the two screenshots, and find the difference: the chat widget’s menu now offers “Book a call” first. Nothing broke. You close the tab, and a little of your trust in the next alert goes with it.
That is the real cost of false alarms in WordPress visual monitoring. Not the minute you lose on each one, but the day you start skipping alerts and miss the one that mattered. This release is mostly about that problem: fewer alerts that turn out to be nothing, and checks that only run when there is something to check.
Most of it works on our side and needs no update at all. Plugin 4.6.1 and the MainWP addon 1.1.2 add the parts that live on your client sites.
Smarter AI checks, fewer alerts about nothing
The AI that decides whether a visual change is real now runs on an upgraded model with new instructions, and it raises fewer false alerts. It also knows about some kinds of change that kept slipping through as “something changed”: details on embedded maps, the options in chat widget menus, relative times like “3 days ago” and a few more..
That last one has a catch worth knowing. A relative time ticking forward is noise. A changed absolute date is not: if your event page suddenly says “October 24” instead of “October 17”, you still get the alert. The AI tells the two apart.
Auto Update Checks only run when an update actually installs
With plugin 4.6.1, an Auto Update Check starts only when WordPress will really install an update. Before, a check could start, take its screenshots and use up checks, and then WordPress quietly skipped the update. You paid for a before-and-after of a site where nothing happened.
WordPress skips updates more often than you would think. Common reasons:
- The license key of the plugin is missing
- WordPress needs FTP credentials to write the files.
- The plugin or theme is managed with Git or SVN.
- The update requires a newer PHP version than the server runs.
If your hosting provider or an update manager has switched off WordPress’s own automatic updates, the check is skipped entirely, and the Logs page tells you why. No more guessing why a site never ran its Auto Update Check.
Result mails you can sort without opening them
The Auto Update Check result mail used to say “something happened” without saying where. The subject now names the website and starts with the outcome, for example [Alert] Auto Update Check: example.com or [OK] Auto Update Check: example.com. Across 80 client sites, that is the difference between a mail filter and reading every single mail.
And when WordPress installed nothing, the mail no longer claims it checked the site “after the updates”.
Fill cache before screenshot
Before every screenshot, WebChange Detector now has a cache pre-build which lets the site rebuild what it needs, and only then takes the screenshot. It fixes one of the most annoying false alarms on websites which need to re-build their cache first.
Here is what used to happen. Some websites delete its generated CSS files on every plugin, theme or core update and only recreates them when a page is rendered fresh. A page cache (on the host, in Varnish, nginx or a CDN) kept serving the old HTML, which still pointed to the deleted files. The result was a screenshot of a page without its layout, right after an update, which looks exactly like the update broke the site.
Steadier screenshots, fewer moving parts
Three sources of random differences between two screenshots are gone:
- Sliders: More Sliders and carousels are now captured on their first slide even when they are in the middle of a slide change at the moment of the screenshot. Before, some of them showed whichever slide happened to be on screen, and every check looked like a change.
- Shrinking headers: Headers that get smaller as you scroll no longer leave a black band and a missing strip of content in the screenshot. The parts of the screenshot now join cleanly.
- Popups: Popups that a site builds in a less common way were sometimes missed and showed up again in every part of a long screenshot. They are now hidden like any other popup.
Security check pages are no longer your screenshot
Some hosts show a short “please wait while we complete a security check” page before the real site loads. That page used to be saved as the screenshot and compared as a change. WebChange Detector now waits for such a page to clear and then takes the screenshot of the real page.
Very long pages no longer break the comparison
Very long pages used to make the comparison fail. Now a screenshot covers up to 25,000 pixels of page height, which is roughly 23 full screens on desktop. A longer page is captured from the top down to that point, and the end of the screenshot carries a clear marker: “Screenshot ends here. This page is longer than the maximum capture height.”
The marker is identical on every check, so it never shows up as a change itself. Pages below the limit are captured exactly as before.
10 seconds between screenshots by default
The screenshot delay, the pause between two screenshots of the same site, now has a minimum and a default of 10 seconds, in the agency dashboard, the WordPress plugin and the MainWP extension. A lower value saved earlier now runs as 10 seconds, so you don’t need to change anything.
Smaller fixes
- When a page fails to load, the check shows the browser’s error message again instead of no reason at all.
- In the agency dashboard, the browser’s back button now closes an open check popup instead of leaving the page.
- Bulk Changes labelled the screenshot delay in milliseconds although it was applied in seconds. It now takes seconds.
What you will notice after the update
Pages with one of the sliders, headers or popups described above show a difference once, on their first check after this release. Their current reference screenshot still holds the old, random state, and the new one shows the steady version. Accept the change once, and from then on those pages stay quiet.
To get everything:
- Update the WebChange Detector plugin to 4.6.1 on your client sites, from the Plugins screen or your usual update tool.
- Using MainWP? Update the WebChange Detector extension to 1.1.2.
- Everything else, from the AI checks to the screenshots, is already live on our side.
New to scheduled checks? The guide to how website monitoring works explains intervals, quiet times and alerts. Running many installs? Here is how to manage multiple client sites from one dashboard.
Not using WebChange Detector yet? Install the plugin from WordPress.org and let the next alert you get be one that actually matters.
