Most website problems do not happen while you are watching. A plugin updates itself on another server, the host changes something, a third-party script stops loading, or someone gets into the site. Nobody tells you, and the first person who notices is a customer.
Monitoring is for exactly that. WebChange Detector checks the pages you choose on a schedule, compares every screenshot with the last one, and only writes to you when something changed. This how-to gets Monitoring running for one website in a few minutes. Every option in detail is in the Monitoring settings reference.
When Monitoring Is the Right Check
- Monitoring: something might break at any time, and you want to hear about it without doing anything.
- On-Demand Check: you are about to change something yourself and want a before and after. See How to Run On-Demand Checks.
- Auto Update Check: WordPress updates itself and you want every update checked. See How to Automatically Check Your WordPress Site After Every Update.
Step 1: Switch On Monitoring and Choose Your Pages
Monitoring is set per website. Pick the pages that would hurt if they broke: homepage, contact form, checkout, your best landing pages.
- Open the Monitoring tab in your dashboard. If the website is not listed yet, click Add website first (see Getting Started).
- Turn on the switch in front of the website.
- Click the website row to open its pages.
- Switch on Desktop and/or Mobile for each page you want to monitor. Every page and device is one check per run.
Step 2: Choose a Schedule
Open the ⋯ menu of the website row and choose Website Settings. Under Run in intervals, pick when Monitoring runs:
- Every day: runs at a fixed Monitoring Interval, from every hour to every 24 hours (every 15 or 30 minutes on higher plans).
- Specific weekdays: only on the days you tick, for example Monday to Friday.
- Specific days in month: on chosen dates, including Last day. Good for pages that rarely change.
- Never: no schedule; pages are only checked when they are saved (WordPress websites with the plugin, see below).
Next to the interval, choose the hour the runs start. The times are shown in your own time zone. Not sure which interval? Start with every 24 hours and make important pages more frequent once you know how often they change.
Step 3: Set Quiet Hours (Optional)
Under Quiet Hours (no checks during this time), choose a window in which no checks run, for example 22:00 to 06:00. Use it for a nightly deployment or backup window, so you do not get alerts about half-finished states, or to save checks at night. Windows across midnight work fine.
Step 4: Decide Who Gets the Alert
In Email addresses for alerts, enter one or more addresses, separated by commas: yours, a colleague’s, the client’s. Leave it empty if you only want to look at the results in the dashboard. Then click Save.
You do not get an email for every pixel. Our AI checks every change first and lets content that changes on every page load (sliders, review widgets, “4 days ago” timestamps) pass as OK. The email only lists what the AI flagged, plus pages that could not be captured. If the AI flags something that is normal on your site, click Ignore in future on it once, and the same kind of change is ignored from then on. See How to Review Checks.
Step 5: Check the Next Run and the Monthly Checks
Back on the Monitoring tab, the website row now shows Next check in with a countdown and your interval. At the top, Next Monitoring Checks shows the estimated Checks / month 1 for all your schedules; open it to see the upcoming runs per website under Upcoming 2. Change the schedule or the pages and you see what it does to your monthly checks before the first run. The figure is an estimate, not a bill.
Do not want to wait for the first scheduled run? Click Run monitoring now on the website row. See Run Monitoring Now After a Deploy.
Option: Check a Page as Soon as It Is Saved
Most layout breakage happens when someone edits a page, not at 3 a.m. For WordPress websites with the WebChange Detector plugin, switch on Check when a page is saved in Website Settings. A few minutes after a published page is saved with changed content, exactly that page is checked against its last Monitoring screenshot. You can use it next to your schedule, or alone with the schedule set to Never. All details: How to Check a Page Automatically as Soon as It Is Saved.
Set up Monitoring in the plugin for WordPress
Using only the plugin, without the Web App? Everything above works from wp-admin too. One thing to know before you start: Monitoring has its own page list. The pages you picked for On-Demand Checks are not monitored until you switch them on here.
- In WordPress, open WebChange Detector → Monitoring 1.
- Switch on Enable Monitoring. The other settings appear.
- Under Run in intervals, choose Every day, Specific weekdays, Specific days in month or Never. For a daily schedule, set Interval in Hours and the Hour of the Day. Not sure? Start with every 24 hours.
- Optional: set Quiet Hours for a nightly backup or deployment window, and switch on Check when a page is saved if editors work on the site.
- Enter the email addresses that should hear about changes under Alerts.
- Click Save Settings.
- Scroll to Select URLs to Check and switch on Desktop, Mobile or both for every page that would hurt if it broke. Each click is saved right away, and Currently selected URLs counts along.
The plugin Dashboard shows the estimated checks per month for Monitoring. Do not want to wait for the first scheduled run? Click Run monitoring now 2, see Run Monitoring Now. Every field of the page is explained in the plugin reference.
In MainWP
The MainWP add-on runs checks around updates (WCD Updates) and has no Monitoring settings. Sites you activated in the add-on also appear in the Web App, marked MainWP: log in there with the same account and follow Step 1 to Step 5 above.
Next Steps
- Monitoring settings reference: every Monitoring option in detail, from what decides an alert to proxies and Basic Authentication
- How to Review Checks: what to do when the first alert arrives
- My Check Shows Changes I Do Not Care About: hide chat bubbles, timers and popups before the screenshot
- A Screenshot Failed or Looks Wrong: when a site blocks the screenshots or a page looks broken