You are about to update plugins, switch a theme setting or deploy new code, and you want to know afterwards what it did to your pages without clicking through every one of them. That is what an On-Demand Check is for. This guide walks you through every step: choosing pages and devices, seeing the cost before you start, following the progress live, and reading the results.
What Are On-Demand Checks?
On-Demand Checks are visual comparisons you start yourself. You trigger them when you’re about to make a change. That’s the key difference from Monitoring, which runs on a schedule and watches for unexpected changes without you doing anything.
The concept is simple: capture the visual state of your pages before an update, make the update, then capture the state after. WebChange Detector compares both sets of screenshots and tells you exactly what changed.
Use On-Demand Checks whenever you:
- Update WordPress core, plugins, or themes
- Deploy custom code changes
- Migrate or restructure content
- Change CSS or layout settings
- Run any update where visual regressions are a real risk
Desktop and mobile screenshots are captured in the same run, so you don’t have to check them separately.
Good to know: On-Demand Checks can email you when they find changes: add alert addresses in the website settings. You can also review every result directly in the dashboard. If you want checks that run on their own schedule, that’s what Monitoring is for.
The Workflow at a Glance
In the Web App, every website gets its own check card that moves through four phases. You can run checks for several websites at the same time; each website has one active check at a time, so before and after screenshots never get mixed up.
- Pre: choose pages and devices, confirm, and the “before” screenshots are taken
- Updates: you do the actual work on your site
- Post: you create the checks, the “after” screenshots are taken and compared
- Done: you review the results
Working inside WordPress instead? The plugin has its own guided version, see On-Demand Checks in the plugin for WordPress below.
Step 1: Selecting Your Pages
Open On-Demand in the dashboard menu. Below the summary at the top you see all your websites. Each row shows how many URLs are Checking at next run and how many Checks for this run they add up to. Tick the websites you want to check 1. Run on-demand checks 2 then counts them, for example “Run on 8 websites”, and opens the confirmation of Step 2.
Choosing Pages and Devices
Click a website row to open its page list. Every URL row has two buttons, Desktop 1 and Mobile 2. Switch them on independently: if a change only affects the mobile layout, check mobile only and save checks.
To switch a whole website at once, use the Desktop and Mobile buttons next to Select all above the list. On large sites, the Search URLs… field finds a page quickly. Your selection is saved the moment you click, and the counts in the website row update right away.
While a check is running for a website, its page selection is locked. Changing pages halfway would leave “after” screenshots without a “before”.
Start the Check: One Website or Many
Pages chosen? Then start the run. Nothing is spent at this point: the click only opens the confirmation window of Step 2.
- On the On-Demand tab, find the website and look at Checking at next run in its row: these are the pages the run will cover.
- Click Run check in that row. If the button is greyed out, no URL is selected for this website yet.
- The window Confirm pre-update screenshots opens. Go on with Step 2.
Several websites at once: tick the checkbox at the start of each website row, then click the big button in the Start an on-demand run box at the top. Its label tells you how many websites it covers, for example Run on 3 websites. Next to it you see the Websites, URLs selected and Checks / run.
Website Settings
Each website carries its own settings: screenshot delay, CSS/JS injection, basic authentication, proxy, region and alert emails. Open them from the three dots in the website row, under Website Settings. Every check of that website uses them, so you configure once and it applies everywhere.
Step 2: Confirm and Take the Before Screenshots
Before a single check is spent, a confirmation window shows you exactly what will happen. Why? So a click on the wrong website, or a forgotten “Select all” on a big shop, never surprises you.
- The window Confirm pre-update screenshots opens. At the top you see the totals: Sites, URLs and Total checks (for a single website also how many are Desktop and Mobile).
- Below, every website is listed with its URLs and checks. Click Show URLs to see exactly which pages and devices are included.
- Happy with it? Click Start pre-update screenshots 1. The button shows the number of checks this run will use. Not happy? Cancel and adjust your selection.
The confirmation is a scope and cost review. If your remaining checks don’t cover a run, the run is refused instead of starting halfway.
Step 3: Follow the Progress Live
Each started website appears as a card in Running checks at the top of the page. The cards update on their own, no reload needed, so you can watch a run fill in instead of guessing whether it’s done.
- The phase line (Pre, Updates, Post, Done) shows where this website stands.
- Four counters show the screenshots in the Queue, Processing, Done and Failed, with a progress bar below.
- The header of Running checks sums up all cards: how many are in Pre, Awaiting, Post, Done or Failed.
If the Failed counter is above zero, a page could not be captured, for example because of a timeout, an error page or a password prompt. Open Logs in the menu to see which page and device failed. Fix the cause (for a password-protected site, add the basic authentication in the Website Settings) before you compare: a page without a “before” screenshot can’t be compared.
When the before screenshots are done, the card says: Pre-update screenshots saved. Install your updates, then create the checks. You can close your browser now. The card stays on the page and waits for you.
Step 4: Make Your Updates
Now do the actual work on your site. Update WordPress core, install plugin updates, switch theme versions, deploy code changes. Whatever you planned. The comparison is only meaningful if something actually changed between before and after.
Tip: Make a note of which plugins or themes you updated. When you review the results, this context helps you quickly decide whether a detected change is expected or a sign of a problem.
Step 5: Create the Checks
Back on the On-Demand page, click Create checks on the website’s card. A second confirmation, Confirm post-update checks, opens. Click Show screenshots to look through the captured before screenshots: it’s worth a quick look to make sure they show your page and not a cookie banner or a login screen. Then click Create checks. The number on the button is the number of checks this round uses.
Running checks for several websites? Create all checks in the Running checks header does this for every waiting card in one go.
The after screenshots are taken, each one is paired with its before screenshot, and the card moves through Post to Done.
Reviewing the Results
A finished card tells you at a glance: Changes detected or All good. Click View results to open the checks of this run. Each comparison shows the visual difference, our AI’s verdict on each changed area (real issue or expected dynamic content), and browser console changes.
If you added alert email addresses in the Website Settings, you also get an email when a change is found.
For the full walkthrough of the comparison popup, AI verdicts, feedback rules, and review best practices, see our dedicated guide: How to Review Checks.
Done with a card? Close it with the × in its corner. Clear all good and Clear all done tidy up many cards at once. The results stay in Checks.
Re-Checking Against the Same Baseline
Found a problem in the results? Fix it on your site, then click Re-check on the card. New after screenshots are taken and compared against the same before screenshots, after the same confirmation as in step 5.
You can repeat until everything shows OK. The before screenshots stay as they are for as many rounds as you need. Fix, re-check, fix, re-check until you’re confident.
On-Demand Checks in the plugin for WordPress
Looking after a single site from wp-admin? The plugin runs the same before/after check as a guided flow with the steps Settings, Pre-Update, Post-Update and Checks. You can watch a complete run as a short clip in Start with the plugin for WordPress.
- Open WebChange Detector → On-Demand Checks. Under Select URLs to Check, switch Desktop and Mobile on for the pages you want.
- Click Start On-Demand Checks. The next screen tells you how many checks this run will use, then click Take Pre-Update Screenshots.
- Watch the counters In queue, Processing, Completed and Failed, with the elapsed and remaining time. Finished screenshots appear under Completed Screenshots; click one to preview it.
- Make your updates. You can leave the page in the meantime.
- Come back and click Create Checks. The results appear under Checks as the comparisons finish.
- Then choose: All good? Start a new check (fresh before screenshots for your next update) or Fixed something? Check again (new after screenshots against the same before screenshots).
The plugin also remembers which plugins, themes or WordPress versions changed between the before and after screenshots, so the check shows what changed on the site, not only on screen.
Best Practices
- Take the before screenshots before touching anything. It’s easy to forget. Add it to your update checklist and make it a habit.
- Always check mobile. Many layout regressions only appear on small screens. Don’t assume desktop looks good means mobile does too.
- Be selective about which pages to check. Routine plugin update? Check only affected pages. Major WordPress core update? Check the whole site.
- Read the confirmation. Each URL on each device uses 1 check per round. The confirmation shows the total before anything is spent.
Stop Guessing, Start Checking
Most WordPress update problems are found too late: by a client, by a visitor, or by you three days after the fact. On-Demand Checks give you a simple, repeatable process to catch visual regressions the moment they happen.
Take the before screenshots. Make your updates. Create the checks. Let our AI tell you what changed and whether it matters. It takes a few minutes and saves a lot of “how long has this been broken?” conversations.
Related Guides
- How to Review Checks: The complete guide to the comparison popup, AI analysis, feedback rules, and review workflow
- How to Set Up Monitoring: Scheduled checks that catch unexpected changes
- Auto Update Checks: Automatically check your site after every WordPress auto-update
- Managing Multiple Client Sites: The Web App for many websites