You hit “Update All” across 40 sub-sites in your Multisite network on a Friday. Monday morning, three clients email screenshots of broken hero images before anyone on your team has noticed. That is not a QA process. That is optimism with a cron job.
This guide walks you through setting up WordPress Multisite visual regression testing with WebChange Detector: network activation for one shared account, or per-site activation when every sub-site needs its own account. Both modes work. Which one you pick depends on who owns the sub-sites, not on which one is technically nicer.
If you already know the plugin from single-site installs, most of it carries over. The Multisite-specific parts are the one account for the whole network, the registration of sub-sites, the per-site permissions, and the network-wide Auto Update Check schedule.
Before you start
Check these three things first:
- You are running WordPress Multisite (Network Admin > “Sites” exists in your menu).
- You are a Super Admin of the network.
- You have a WebChange Detector account, or you create one during setup.
If your install is not a Multisite, start with the regular plugin setup in Start with the plugin for WordPress.
Two ways to install: network activate or per-site
There are two activation modes on a Multisite, and the choice is about billing and ownership. Most agencies want network activate. Pick per-site only when your sub-sites belong to different customers who each need their own WebChange Detector account.
| You want this | Pick this mode | What it looks like |
|---|---|---|
| One account, one Auto Update Check schedule, manage everything from the Network Admin | Network activate | One API token for the whole network. A “WebChange Detector” menu in the Network Admin. Sub-sites inherit the Auto Update Check schedule. |
| Each sub-site has its own customer, its own account, or its own billing | Per-site activate | Each sub-site behaves like a standalone install with its own token. No Network Admin menu. |
Default for agencies: Network activate. Switch to per-site only if you have a real reason: reseller hosting, separate billing, strictly separated client setups.
Step 1: Install and network-activate
Network activation installs the plugin once for the entire network and makes it available on every current and future sub-site. Do not click “Activate” on a single site by mistake; that puts you into per-site mode and you lose the Network Admin menu.
- In the Network Admin, go to Plugins > Add New and search for “WebChange Detector” (or download the ZIP from WordPress.org).
- Click Install Now. The plugin installs once for the whole network.
- Click Network Activate (not just “Activate”, which would be per-site).
That is it. Activation prepares every sub-site in your network, and sub-sites you create later get the plugin activated automatically. To be checked, a sub-site still needs to be registered (Step 3).
Step 2: Connect your account once
The whole network uses one API token. You enter it once in the Network Admin, and the sub-sites never ask for it.
- Open Network Admin > WebChange Detector.
- Create a new account right there, or paste the API token of your existing account under Use Existing API Token (you find it after you log in to your account at webchangedetector.com).
- Click Save.
Switching from per-site to network activation? The plugin takes over the token your main site already had, and the sub-sites pick it up automatically. You do not have to touch anything.
Step 3: Register your sub-sites
Network Admin > WebChange Detector > Sites lists every site in the network as “Registered” or “Not Registered”. Registering a sub-site connects it to your account and syncs its pages. Only registered sites can be checked, so you decide which sub-sites use up checks.
- For each site you want to check, click Register.
- Or click Register All Unregistered Sites to register the whole network in one go.
A registered sub-site also shows up in the Web App at webchangedetector.com, labelled as a Multisite sub-site, next to every other website in your account.
From now on, the Network Admin pages of WebChange Detector show a Sub-Site Selection box at the top. Pick a sub-site and click Switch to work on it, or pick All Websites to push settings to every registered sub-site at once. Your choice is remembered while you move between the tabs.
Step 4: Set per-site permissions (optional)
Permissions decide what the admins of each sub-site see of the plugin and what they may do with it. Skip this if you own every sub-site yourself. Use it when the sub-sites are client-facing and you want to lock down which buttons a client can press, or hide the plugin from them completely.
Open Network Admin > WebChange Detector > Sub-Site Allowances, pick the sub-site in the Sub-Site Selection, and set the toggles:
- Plugin visibility: “Show plugin in WP admin (menu + admin bar)”. Switch it off and the sub-site’s admins no longer see the plugin, while its checks keep running.
- Tabs in WP Plugin: which pages the sub-site admins see (On-Demand Checks, Monitoring, Checks, AI Rules, Settings, Queue).
- On-Demand Checks and Monitoring Checks: whether they may start On-Demand Checks and see or change the settings and the page lists.
- Other Settings: account settings, the upgrade link, the setup wizard, and “Allow only checks for frontpage”.
Click Save Allowances. The change reaches the sub-site right away. In All Websites mode, saving overwrites the permissions of every registered sub-site, and an extra accordion, Defaults for new sites, sets what sub-sites get when you register them later.
As Super Admin you always keep full access to the plugin on every sub-site, whatever the permissions say. More about permissions and hiding the plugin: Control what your client sees, or hide the plugin.
Step 5: Configure Auto Update Checks network-wide
Auto Update Checks are where Multisite gets the most leverage: one schedule, one notification email, screenshots across every participating sub-site. In WordPress Multisite, updates run for the whole network from the main site, so the schedule lives there too.
In the main site’s WordPress admin, open WebChange Detector > On-Demand Checks. The section “WP Auto Update & On-Demand Checks Settings” holds the schedule for the entire network:
- Auto Update Checks: the toggle that lets the main site itself take part.
- Auto Update Timeframe: the time window in which WordPress may install updates (for example 02:00 to 05:00).
- Weekdays: the days on which updates may run.
- Notifications: the email address(es) that receive the result.
- WordPress Security Updates: “Always allow WordPress core security updates” installs security releases right away, even outside the timeframe, without checks.
Click Save Settings. A note on the page reminds you that the schedule and its notification email apply to the whole network.
Every sub-site decides on its own whether it takes part. A sub-site is only included when its toggle is on:
- Open the sub-site’s WordPress admin, or pick it in the Sub-Site Selection of the Network Admin.
- Go to WebChange Detector > On-Demand Checks.
- Switch Auto Update Checks on (or off) and save.
That toggle is the only Auto Update Check setting a sub-site has. The schedule fields are shown greyed out with the values inherited from the main site. Which pages of a sub-site are checked is the selection on its On-Demand Checks page. The full Auto Update Check guide is in How to Automatically Check Your WordPress Site After Every Update.
Step 6: Run your first On-Demand Check
An On-Demand Check is the fastest way to verify the whole setup works. It runs per sub-site:
- In the Network Admin, pick the sub-site in the Sub-Site Selection and open WebChange Detector > On-Demand Checks (or open the same page in the sub-site’s own admin).
- Select the pages you want to check and click Start On-Demand Checks.
- Click Take Pre-Update Screenshots. The page tells you how many checks the run uses.
- Make your change (deploy, plugin update, anything), then come back, click Next > and Create Checks.
The results show which pages changed and which stayed identical. In All Websites mode the On-Demand Checks page only shows the settings, which you can push to every registered sub-site at once; the checks themselves always run per sub-site. The step-by-step guide is in How to Run On-Demand Checks.
Per-site activation: when and why
Skip this section unless you have a reseller or strict-isolation use case. Per-site activation exists for one reason: your sub-sites belong to different customers who each need their own WebChange Detector account and their own billing. Everything network activation gives you (one token, one Auto Update Check schedule, the Network Admin pages) goes away.
If that is your case, do not network-activate. Instead:
- In the Network Admin, open Plugins and click Network Deactivate on the WebChange Detector plugin (if it was network-activated).
- Visit each sub-site and activate the plugin from that sub-site’s Plugins screen.
In per-site mode, each sub-site behaves exactly like a standalone WordPress install: own token, own settings, own billing, and no Network Admin menu.
Troubleshooting
These are the questions that come up most after a Multisite install.
A sub-site shows “Setup required”. The network has no account connected yet. Open Network Admin > WebChange Detector and connect your account (Step 2). Sub-site admins can not do this themselves; the button “Go to Network Admin” only appears for Super Admins.
A sub-site shows “Activation pending” or “Sub-site not registered”. The network is connected, but this sub-site was never registered. Open Network Admin > WebChange Detector > Sites and click Register next to it. Sub-sites are never registered just by visiting them, so nobody uses up an account slot by accident.
Auto Update Checks only cover the main site, not the sub-sites. Make sure each sub-site you want covered is registered and has its Auto Update Checks toggle switched on. Sub-sites with the toggle off are skipped. Also check that a notification email is set on the main site, otherwise the checks run but nobody gets the result.
A sub-site is archived. Is it still checked during auto-updates? No. Archived, deleted and spam sites are left out of the Auto Update Checks. Once you un-archive the site, it takes part again; its registration is kept.
Uninstalling cleanly
Removing the plugin is a full cleanup, not a soft delete. If you Network Deactivate and then delete WebChange Detector, it goes through every site in the network (including archived, deleted and spam sites) and removes the settings, data tables and scheduled tasks it created there, and then the network-wide settings including the API token. There is no manual cleanup step.
What’s next
Ready to run your first check? Open Network Admin > WebChange Detector > Sites, register your network, and start an On-Demand Check on one sub-site. If anything shifts, you will see it in a comparison, not a client email.