What a Check Costs, and How to Keep an Eye on It

Metered plans make some people nervous: what if one wrong click, or one Monitoring schedule set too eagerly, eats the whole month? With WebChange Detector that doesn’t happen by accident. There is one simple counting rule, every check that costs something shows its price before it starts, and the dashboard tells you what the rest of the month will most likely use.

This guide shows the counting rule, where exactly you see the numbers, and what to change when they’re too high.

The rule: one page on one device is one check

Every time we compare a page with its earlier screenshot on one device, that’s one check. The same page on desktop and mobile is two checks. What that means for each check type:

Check typeWhen it uses checksExample
On-Demand CheckEach time you run one10 pages on both devices = 20 checks per run
MonitoringOn every scheduled run10 pages on both devices, once a day = about 600 checks in a 30-day month
Check when a page is savedOnly when someone edits a pagePages nobody touched cost nothing
Auto Update ChecksEach time WordPress installs updates in your chosen time windowDays without updates cost nothing

Comparisons that fail don’t use up checks.

See the cost before you click

Anything you start by hand shows its price first. Nothing is captured until you confirm.

The preflight of an On-Demand Check with the websites, pages and checks of this run
  • Web App: when you start an On-Demand Check, the Confirm pre-update screenshots window shows the sites, URLs, desktop and mobile screenshots and the Total checks. The start button 1 carries the same number, for example “Start pre-update screenshots · 20”. For several websites at once you see the total plus the URLs and checks of every single site. Run monitoring now asks too, with the maximum number of checks the run uses.
  • plugin for WordPress: before the first screenshots of an On-Demand Check, the plugin says “This run will use 20 checks” (with your number). If you don’t have enough checks left, you see Insufficient Screenshots Available instead of the start button, so you can select fewer pages or upgrade.
  • MainWP: before WCD Updates start, the preflight shows “This run uses … checks” next to how many you have left, marked Enough credits or “… short”. The run can only start when your checks cover it.

Whatever you use: a run your remaining checks can’t cover doesn’t start halfway. Step by step: How to Run On-Demand Checks and How to Run WCD Updates with Visual Checks in MainWP.

Know what the month will cost

Monitoring and Auto Update Checks run without you clicking anything. That’s why the Dashboard doesn’t stop at what you’ve used: it adds up what your current setup will most likely use until your checks renew. You find the same overview on the Dashboard of the Web App and on the Dashboard of the plugin for WordPress.

The WebChange Detector dashboard: plan and usage, then Monitoring, Auto Update Checks and On-Demand across all client websites
  1. The usage bar reads like “120 used + ≈ 480 more expected of 1,000 checks this period” (with your numbers), plus the days until renewal.
  2. Below it, the forecast is split into “Monitoring ~…/mo” and “Auto Update Checks max ~…/mo”, so you see which one drives your usage.
  3. The three cards go into detail. Monitoring shows how many URLs are monitored and the expected checks per month. Auto Update Checks shows the most it can use per month and warns about websites without an alert email. On-Demand shows how many checks one On-Demand Check costs with your current page selection.
  4. If the forecast is higher than your plan allows, a banner says so before renewal (“Consider upgrading or reducing scheduled checks before renewal”), and the plan button turns into Upgrade Plan →.

Why “max” for Auto Update Checks? We can’t know in advance on which days WordPress will have updates, so the forecast assumes an update run on every day you allowed. Most months use less.

In the Web App, the Monitoring page adds two more numbers: the summary at the top shows Checks / month for all monitored websites together with the next run, and every website shows its Checks for this run. The forecast takes your schedule, quiet hours, pages and devices into account.

Your plan page (Manage plan on the Dashboard) shows the same forecast. If your current plan will run short, it points you to the smallest plan that covers what you’re expected to use.

All of these numbers are estimates based on your current settings. They help you plan; they are not a bill.

The same numbers in WordPress

If you only use the plugin, open WebChange Detector → Dashboard in wp-admin. The usage bar, the forecast and the three cards are right there.

Forecast too high? Turn these knobs

  • Check the pages that matter. Home, key landing pages, checkout and contact form usually tell you more than 300 blog posts. Switch the rest off; see Keep Your Page List Up to Date.
  • Use mobile where it adds something. Both devices double the checks. Keep both for important pages, desktop alone may do for the others.
  • Run Monitoring less often, or pause it at night. A slower schedule or quiet hours cut the monthly number right away, and the forecast updates with your settings. See How to Set Up Monitoring.
  • Check edits instead of the clock. With Check when a page is saved, a page is checked when someone changes it, and untouched pages cost nothing.
  • Switch off pages that are gone. A deleted page stays in your list until you switch it off, and it keeps being checked.

When your checks run low

You don’t have to watch the bar every day. We send an email when it matters:

  • “Your checks are getting low”: you’ve used most of this period’s checks.
  • “You ran out of checks.”: everything is used up. Scheduled Monitoring stops until your checks renew or you upgrade.
  • “Monitoring check skipped: not enough checks left”: a scheduled Monitoring run was skipped because the remaining checks didn’t cover the whole website. The email lists the affected websites with the checks each one needs per run, how many checks you have left and when they renew. Smaller websites may keep running as long as your checks allow. You get this one at most once per billing period.

A website is always checked completely or not at all, never halfway. Every one of these emails has a button that takes you straight to your plan page, already signed in.

For agencies: subaccounts share your checks

Checks used in your subaccounts count toward your main account. If one client shouldn’t be able to use up everything, give that subaccount its own check limit. See How to Use Subaccounts and Switch Into a Client Account.

WebChange Detector Newsletter

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