Visual regression testing for WordPress: catch broken layouts after auto-updates, plugin installs, or deploys before your visitors do. Find visual bugs before your visitors do Every time WordPress core, a plugin, or a theme updates, something on your site can quietly break. By the time a visitor rep
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 5.5 and PHP 7.4.
SourceWordPress plugins · Nov 1, 2026
01 / Source details
Aboutthistool.
Visual regression testing for WordPress: catch broken layouts after auto-updates, plugin installs, or deploys before your visitors do.
Find visual bugs before your visitors do
Every time WordPress core, a plugin, or a theme updates, something on your site can quietly break. By the time a visitor reports it, you have already lost trust and probably sales.
WebChange Detector takes a screenshot of your pages before the change, another after , and tells you exactly what is different on desktop and mobile. The AI check ignores moving parts like sliders, carousels, and animations, so you only get alerts that actually matter.
What is visual regression testing?
Visual regression testing is the practice of taking a screenshot of a web page in a known-good state, then comparing a new screenshot to it after any change like an update, a deploy, a CSS tweak, or a plugin install. Anything that looks different is flagged.
It is the fastest way to catch layout breakage that traditional testing like PHP errors or broken links cannot see, because the page can render “successfully” while still looking wrong to a human visitor. WebChange Detector brings this practice to WordPress with one-click setup, no headless-browser scripting, and no Selenium or BackstopJS know-how required.
What you can detect
Layout breaks after WordPress updates (core, plugins, themes)
Side effects of installing or activating a new plugin
Visual regressions after deployments, CSS edits, or pagespeed tweaks
Silent breakage from third-party scripts, fonts, or external APIs
Hacks, defacement, or injected ads during continuous monitoring
Theme regressions after switching themes or updating a child theme
Quiet times when monitoring gets skipped to save check credits
Three ways to detect changes
WebChange Detector gives you three independent check modes. Use one, two, or all three side by side, depending on how you manage your site.
1. Auto Update Checks: automatic safety net for WordPress auto-updates. This mode hooks directly into the WordPress auto-update system. Right before WordPress installs a core, plugin, or theme update automatically, WebChange Detector takes a “before” screenshot of the pages you selected. Right after the native WordPress auto-update finishes, it takes the “after” screenshot. If anything changed visually you get an email with the affected pages highlighted, plus an AI summary of what looks different. This is the mode that lets you actually leave WordPress auto-updates turned on without losing sleep.
2. On-Demand Checks: visual diffs on your own schedule. Run a check on demand right before and right after any change you make: a deploy, a plugin install, a CSS tweak, a theme switch, a hosting migration. On-demand checks are perfect for teams that already have an update workflow in tools like MainWP, ManageWP, WP Umbrella, InfiniteWP, or WP Remote . Use those tools to push your updates, and use WebChange Detector to verify visually that nothing broke. The plugin captures the pre-state, you push your changes, you trigger the post-state, and you get a side-by-side diff.
3. Monitoring: continuous visual surveillance with alerts. Schedule recurring checks at fixed intervals. Or let a save trigger it: a few minutes after someone edits a published page, WebChange Detector checks exactly that page. A “Run monitoring now” button starts a full check right away, for example after a deploy. The plugin captures and compares your selected pages on schedule, and emails you the moment a difference appears. Monitoring catches changes that nobody on your team pushed: hacks, defacement, expired SSL, third-party-script breakage, broken CDN assets, accidental edits, server-side issues, theme regressions, vendor outages. It is your “site is silently broken” alarm.
You can mix all three. A typical agency setup: auto-update checks on every client site so nothing breaks silently during automated WordPress updates, monitoring at 24h intervals on the same selection, and on-demand checks fired from the agency’s MainWP or ManageWP dashboard before scheduled maintenance windows.
Features
Automatic cookie banner opt-in to load all content which is blocked initially.
Hiding ads that might cause changes on every check.
AI classification of whether a change is an actual change or just a moving element.
Train the AI to recognize intentional changes like A/B tests so specific patterns get ignored.
Smart shift detection: if your hero section gets taller, we don’t flag the entire page below it as ‘changed’.
Check desktop and mobile screen sizes.
Pausing dynamic content like sliders, carousels, GIFs, videos, etc. before taking screenshots.
Trigger lazy load elements before starting the visual regression testing.
Check browser console logs for new errors to detect errors like a broken contact form.
WPML and Polylang support.
WP Multisite support.
Publicly accessible link to a check to share with your agency or developer.
Basic Auth support to check websites behind a password.
Static IP proxy to whitelist the IP in a firewall which blocks other users.
Why site owners and agencies pick WebChange Detector
Works on staging, password-protected, and firewalled sites. Basic-auth credentials and an optional static IP for firewall whitelisting come built in. Most visual-regression plugins refuse to run on anything that is not public.
Free plan with 10 monthly checks. On-demand checks, auto-update checks, and the API are all included; no paywall on the core workflow.
AI-powered noise filtering. Sliders, counters and other randomized content are filtered out automatically so you stop drowning in false positives.
Built for multisite. Network-activated or per-site, with sub-site allowances so agencies can hand each client a controlled slice of features, and agencies can hide the plugin from a client’s WP admin entirely while updates and checks keep running.
WPML and Polylang ready. Each language version is synced and checked separately.
Share results without giving WP access. Every comparison has a public link you can paste into Slack or send to a designer.
Desktop and/or mobile in every check. Choose which screen size(s) you want to check per site.
How it works
01Install the plugin and create a free account from inside WordPress.
02Pick the pages you want watched (posts, pages, custom post types, taxonomies, custom URLs).
03Pick your check mode: auto-update checks, on-demand checks, monitoring, or any combination.
04Get an email alert with the changed pages highlighted. Open the slider view to compare before/after, mark the result Ok / To Fix / False Positive, and share the link with your team.
Manual QA vs. automated visual regression testing
Most WordPress site owners check their site after an update by clicking through a few pages and trusting their memory. That works until it does not.
A manual click-through covers only the pages you happen to remember, takes 10 to 60 minutes per round, almost never includes the mobile viewport, and depends on your eyes catching pixel shifts that the human visual system is genuinely bad at. The output, when something does break, is usually a panicked Slack message after a customer noticed first.
WebChange Detector checks every URL you selected, every single time, on desktop and mobile, in seconds. It runs unattended while you sleep (in monitoring and auto-update modes), and produces a public side-by-side comparison link you can paste straight to a designer or developer.
Manual QA is fine for one-off changes. WebChange Detector pays for itself the first time an auto-update silently breaks a checkout button at 3 a.m.
Who is WebChange Detector for?
Site owners and freelancers who do not want to spend half a Sunday afternoon clicking through 30 pages after the WordPress auto-update ran.
Agencies and maintenance providers running MainWP, ManageWP, WP Umbrella, InfiniteWP, or WP Remote across dozens or hundreds of client sites. WebChange Detector slots into your existing update workflow as the visual-verification layer those tools do not provide on their own.
WooCommerce and shop owners who cannot afford a broken checkout, cart, or product page after a WooCommerce or payment-gateway update.
Publishers and news sites that release content many times a day on top of fragile templates and ad scripts.
SaaS and lead-gen teams running landing-page experiments where every CRO test carries layout risk.
Multilingual sites running WPML or Polylang where breakage often hides in non-English language versions.
Multisite networks where one update can ripple across dozens of sub-sites and a single dashboard view is the only way to stay sane.
Compatibility
WebChange Detector renders the front-end of your site through a real browser, so anything that renders for a human visitor renders for our screenshot engine. We are tested with:
Themes : Astra, GeneratePress, Kadence, Blocksy, Hello, Divi, Avada, Storefront, and any well-coded theme.
WooCommerce , EDD, MemberPress, LearnDash, BuddyBoss, bbPress, and most WordPress ecosystems.
Caching plugins : WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, FlyingPress.
Multilingual : WPML, Polylang.
Hosts : works on shared hosting, VPS, managed (Kinsta, WP Engine, SiteGround, Pressable, Cloudways), and on-premise.
Trial plan
1,000 checks during your 14-day trial
Use and test all features mentioned above
Free plan
After the trial, you are automatically switched to our free plan with some restrictions: * 10 checks per month * No browser console log errors
Premium plans
Need more checks and all features unlocked? S
See it in action
Screenshots & previews.
Check view: before-screenshot left and after-screenshot right with highlighted changes.Dashboard: account overview, recent checks, and quick actions.On-Demand Checks: settings for the auto update checks and on-demand checks. Also run an on-demand visual diff before and after updates or other changes.Monitoring settings: select pages, intervals and other settings for continuous monitoring.Checks list: every result, grouped by source (monitoring, on-demand, auto-update) and filterable by status.After On-Demand Checks: see the results immediatelly after the checks ran.AI rules: train AI to ignore regions of a check in future runs to eliminate false-positive alarms.
02 / Source details
Gettingstarted.
01From your WordPress admin, go to Plugins > Add New , search for “WebChange Detector”, and click Install.
02Activate the plugin through the Plugins menu.
03Open WebChange Detector in the sidebar and complete the short signup form to create a free account.
04Click Activate Account in the email we send you.
05Pick the pages you want to monitor and run your first check.
Manual install: upload the webchangedetector folder to /wp-content/plugins/ , then follow steps 2 through 5 above.
03 / Source details
Frequently asked questions.
What is the difference between auto-update checks, on-demand checks, and monitoring?
These are the three check modes the plugin offers. Auto-update checks are fired automatically by the WordPress auto-update system: a “before” screenshot right before the update runs, an “after” screenshot right after, and an email if anything looks different. On-demand checks are run by you on demand, typically right before and after a deploy or update you trigger yourself. Monitoring is a recurring schedule that catches changes nobody pushed. You can use one, two, or all three at the same time.
Can I use it with MainWP, ManageWP, WP Umbrella, or InfiniteWP?
Yes. WebChange Detector is the visual-verification layer those tools might not provide. Run your updates through whichever dashboard you already use, and let WebChange Detector handle the before/after visual diff. On-demand checks can be triggered from the WordPress admin, the webapp or the REST API, so you can also wire them into your own scripts or pipelines.
Will it work on a staging site or behind a password?
Yes. WebChange Detector supports HTTP basic auth credentials and an optional static IP proxy that you can whitelist in your firewall.
How does it differ from manually clicking through pages after an update?
Manual QA does not scale, you forget pages, and you cannot remember the exact pixel state from yesterday. WebChange Detector compares the rendered page at the pixel level on desktop and mobile, highlights the differences, and emails you only when something actually changed.
How does the AI know what to ignore?
The AI is trained to recognize dynamic elements that are designed to change every page load: image sliders, ad slots, randomized testimonials, live counters. You can also create your own per-URL or per-website rules to ignore specific classifications permanently.
Does it work with WordPress multisite?
Yes. The plugin supports both network-activated and per-site activation modes. From the network admin you can register sub-sites, set per-site allowances, and run pre/post screenshots across the whole network during auto-updates.
Does it work with WPML or Polylang?
Yes. URLs are synced per language and each language version is checked independently.
Are mobile and desktop both checked?
Yes. You can select per URL whether to check the desktop and/or mobile viewport.
Does it work with Elementor, Divi, Gutenberg, or other page builders?
Yes. We screenshot the rendered front-end, so any builder, theme, or block library is supported by default.
Can I share a result with a designer or developer who is not in WordPress?
Yes. Every check has a public share link that opens the comparison view in a browser, no login required.
What does the free plan include?
1,000 checks during the 14-day trial, then 10 free checks every month after. The free plan activates automatically after your trial with some restrictions (no browser console log monitoring).
Can I trigger checks from a deploy pipeline?
Yes. The REST API covers websites, groups, comparisons, AI rules, and webhooks. One API call starts a monitoring run of all monitored pages, ideal as the last step of a deploy script.
What is monitored besides visual changes?
In addition to layout, the browser console log is checked for errors.
Website LLMs.txt and LLMs-Full.txt Generator is an LLMs.txt generator and llms-full.txt generator for WordPress. It helps site owners generate, manage, preview, validate, and serve AI discovery files from published public content. Use it to create structured /llms.txt and optional /llms-full.txt end
EngageDock AI is a customizable floating contact widget for WordPress websites that want more leads and faster visitor communication. It helps small businesses turn website traffic into calls, texts, emails, and callback requests from one clean contact panel. Key Features: Click-to-Call – One tap ca
Altify AI is an auto ALT text and AI ALT text plugin for WordPress images. It helps generate descriptive image ALT text for accessibility and image SEO. Use bulk image ALT text tools for your Media Library, generate featured image ALT text automatically, and scale WooCommerce image ALT updates with
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati
