Run Monitoring Now After a Deploy

You finish a redesign on staging, click “Push to live” at your host, and the new version replaces the old one in seconds. Did every page survive the move? Monitoring will tell you, at the next scheduled run. That might be tonight.

Normally WebChange Detector can check a page as soon as somebody saves it in WordPress (see How to check a page automatically as soon as it is saved). But a staging-to-live push, as WP Engine and many other hosts do it, copies the whole site at once. Nothing is “saved” on the live site, so that trigger never fires. The same goes for a deploy from Git or a database import.

Run Monitoring now closes that gap. It checks all monitored pages of a website right away and compares them with their last Monitoring screenshots, with the usual AI verification, alert emails and webhooks. You start it with one click in the Web App or in the plugin for WordPress, or with one API call at the end of your deploy script.

Before you start

  • Monitoring is switched on for the website, and at least one page is selected for Monitoring. Run Monitoring now checks exactly those pages.
  • If you deploy with a page cache or a CDN, clear it first. The run starts immediately, and you want the screenshots to show the new version.
  • Each page and device counts as one check, like any Monitoring run. The confirmation tells you the number before anything starts.

In the Web App

Every website on the Monitoring tab has its own Run monitoring now button.

Run monitoring now in the Web App: confirm the run and the button turns into “Monitoring running”.
  1. Open the Monitoring tab.
  2. In the row of the website you just deployed, click Run monitoring now.
  3. The confirmation shows how many checks the run uses at most. Click Run now.
  4. The button turns into “Monitoring running…”. When the run is done you see “Monitoring finished” with the number of changes and a link to the results.

Is the button greyed out? Hover over it: “Enable monitoring first” means Monitoring is paused for that website, “No URLs selected for this website” means no page is selected yet.

In the plugin for WordPress

Working inside the client’s WordPress? The plugin has the same button.

Run monitoring now in the plugin: the button changes to “Monitoring running” and a message confirms the start.
  1. In the WordPress admin, open WebChange Detector > Monitoring.
  2. On the Monitoring Status card, click Run monitoring now.
  3. Confirm the question “Run monitoring now for all selected URLs?”, which also names the number of checks.
  4. The button shows “Monitoring running…” until the run is finished.

The button only appears when Monitoring is on and pages are selected. On client sites it also needs the permission “Show monitoring checks settings”; without it the client does not get the button (see Control what your client sees).

From your deploy script

If you deploy often, let the deploy start the check. One API call as the last step of your script, after the cache purge, starts the same run as the button. You can also send just the pages you changed. The call, the answers and how to find the right group are in Connect Slack, Zapier and your deploy pipeline.

What happens during the run

  • It starts at once. No waiting time, no hourly limit. Your remaining checks are the only limit.
  • Not enough checks left? Then nothing starts, and you are told why. No half-finished run.
  • No double charge. Pages that are being checked right now are skipped, and a second click while the run starts or runs gets “already running” instead of a second run.
  • Waiting page-save checks are taken over. If a page was saved a minute ago and is waiting for its check, the manual run checks it and the waiting check is dropped.
  • Easy to find later. In the Checks tab the run is labelled “Manual Trigger”, so you can tell it apart from scheduled runs and page saves.

Then review the results as usual: How to Review Checks.

WebChange Detector Newsletter

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