How to Run WCD Updates with Visual Checks in MainWP

Updating 40 client sites from MainWP takes one click. Knowing that none of them broke takes 40 browser tabs, and that is the part that never happens on a busy day. So the broken slider, the missing menu or the dead checkout gets found by the client.

A WCD Update wraps your MainWP updates in a visual check: WebChange Detector takes screenshots of the selected pages on every site, installs the updates, takes the same screenshots again and compares them. You get one answer per site, “All good” or “N pages to review”, before your clients notice anything.

Why agencies update this way

  • Proof instead of hope: for every site you see whether a page changed, with before and after side by side.
  • You find it first: a broken page shows up in your dashboard minutes after the update, not in a client email days later.
  • Fresh screenshots: the cache of each site is cleared before the first screenshots and after the updates, so a cached page can neither hide a change nor fake one.
  • No surprise costs: before anything runs, you see exactly how many checks the run needs. Sites without pending updates are skipped and cost nothing.
  • A record for your clients: every run stays on the Checks tab with date, results and an AI summary of what changed.

Before you start

  • MainWP Dashboard with your child sites connected.
  • The add-on WebChange Detector for MainWP installed and connected to your WebChange Detector account, with pages chosen for your sites. New to it? Follow Start with MainWP first; it takes about ten minutes.

Step 1: Choose the sites

In MainWP, open Add-ons, then WebChange Detector for MainWP and the Settings tab. Switch on visual checks for every site you want to protect 1. With Settings 2 you adjust the checks per site.

The site list of the add-on: switch visual checks on per site, then configure URLs and settings

The site settings define where the screenshots are taken and who gets the alert e-mail.

Visual check settings of one MainWP site: region, alert e-mails, delay and CSS

Use Configure URLs to pick the pages that get checked on each site, separately for desktop and mobile. A site with no pages selected is updated without checks.

Step 2: Start a WCD Update

Open the Run tab 1. It shows how many of your sites have updates, how many pages will be checked and how many checks that needs. Click Run visual checks & updates 2.

The Run tab of WebChange Detector for MainWP with the update summary and the button to run visual checks and updates

The Run tab updates all activated sites that have pending updates. You can also start a WCD Update right where you already work:

  • MainWP’s Updates page: on the WordPress, Plugins, Themes and Translations tabs, tick the updates you want and click Update Selected with Checks, or Update All with Checks for everything on that tab.
  • Your dashboard: the WebChange Detector: Updates widget, and the WCD Updates card with Update with Checks inside MainWP’s Updates Overview widget.
  • A single site: the WebChange Detector tab of that site, or its own Updates page.
Ticking plugin updates on MainWP’s Updates page and clicking Update Selected with Checks: the preflight opens.

Selected a site on the Updates page that has no visual checks activated? It is still updated, marked Checks not activated, and uses no checks.

Step 3: Check the preflight

Before anything happens, the preflight lists the sites and pages, the updates that will be installed and whether your checks cover the run 1. Sites without updates are skipped automatically.

The preflight of a WCD Update: which sites get updated, which pages are checked and whether the checks are covered
  • Checks: “This run uses N checks” next to what is left on your plan. Enough credits means you are good to go. If the run does not fit, the preflight tells you how many checks are missing, offers Upgrade plan and does not let you start.
  • Updates: click the line “updates will be installed” to see, per site, which WordPress, plugin and theme updates are coming and to which version.
  • Pages: open a site to see its selected pages with their Desktop and Mobile marks.
  • Skipped sites: sites without pending updates are greyed out with a No updates badge. They get no screenshots and cost nothing.
  • Warnings: if the checks of a site cannot be loaded, the preflight says so clearly: that site would be updated without visual checks.

All fine? Click Capture & update.

Step 4: Follow the run

The popup turns into the run view with a timeline: Pre, Updates, Post, Done. Your sites stay live the whole time; only screenshots are taken.

  1. Pre: the cache of each site is cleared, then the pre-update screenshots of all selected pages are taken. The panel counts Queue, Processing, Done and Failed.
  2. Updates: the updates are installed one site after another, so your dashboard is never overloaded. When a site got updates, its cache is cleared again.
  3. Post: the same pages are captured again and compared with their pre-update screenshots.
  4. Done: the run ends with All good or N pages to review.

Below the timeline, every site has its own line with its progress and status, so you see at a glance which site is still updating and which one has pages to review.

When the run is done, View results opens the Checks tab. Fixed something on a site after the run? Re-check takes new post-update screenshots and compares them with the same pre-update screenshots. That uses checks again.

If you close the tab or lose the connection

Your browser drives the run, so the add-on makes sure a long run over many sites survives the usual accidents:

  • While the run is going, the popup cannot be closed and asks you to keep it open. Your browser also warns you before you close the tab.
  • If you navigate away or the tab closes anyway, the run continues when you come back to the add-on or your dashboard. It picks up where it stopped: only missing pre-update screenshots are taken again, and only sites that are not updated yet get their updates. Nothing is charged twice.
  • A resumed run continues in the background. Click Updates running to open the popup again.
  • Open the dashboard in a second tab and you cannot start a second run by accident. The second tab only takes over when the first one has gone silent.

One thing the add-on cannot undo: leaving while an update is being installed can interrupt that very update. So during the Updates phase, keep the tab open.

Step 5: Review the results

After the run, the Checks tab lists every WCD Update with its status and an AI summary of what changed. Open a run to see each page before and after the update.

The Checks tab with WCD Update runs, their AI summaries and the status of each comparison
  • Filter by period, status and website, or show only runs with changes. Switch between Runs (grouped) and List (every page in one list).
  • Each page shows the time of the before and after screenshots, the visual change in percent, the AI summary and its review status: New, OK, To Fix or False positive.
  • View opens the comparison with the differences highlighted. It is a public link, so you can send it straight to a client or a developer.

The people in the Alert emails field of a site’s settings also get an email when a WCD Update finds a change on that site. How to read a comparison and when to trust the AI: How to Review Checks.

Good to know

  • Only updates you start as a WCD Update get checked. Updates started with MainWP’s normal buttons, by cron or WP-CLI run as before, without screenshots and without using checks.
  • The cache clearing runs through the MainWP Child plugin that is already on your sites and works with more than 20 caching plugins. If clearing fails on a site, the run still continues.
  • Websites are unlimited on every plan; only the checks you run count against it.
  • Your sites stay live during the run; only screenshots are taken.

WebChange Detector Newsletter

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