Feature · Monitoring & Alerts

Website monitoring & visual change alerts.

Visual monitoring and change alerts for WordPress agencies. Check client sites on a schedule, from every 15 minutes (depending on your plan) to monthly, and every time someone on your team saves a page. You hear about it only when something really changed: a broken layout, a white screen, a broken checkout.

webchangedetector.com / monitoring
Monitoring overview with interval, next check and URLs per website
What you get

Monitoring that stays quiet until it matters.

On a schedule

Every 15 minutes for a WooCommerce checkout, hourly for a homepage, weekly or monthly for a portfolio. You choose the rhythm per website, down to the weekdays.

When a page is saved

Most visual breakage happens when someone edits a page, not at 3 a.m. With the plugin for WordPress, a saved page is checked a few minutes after editing stops. Pages nobody touched cost nothing.

One email per check run

Sent only when something really changed. Alert emails come from our platform, not from the client’s WordPress, so they arrive even when the site is down. Each one carries an AI summary and a link to the before and after view.

Desktop and mobile

Every page is checked full page on desktop and mobile. Catch an overlapping mobile menu or a hidden checkout button before your client’s customers do.

Quiet hours

Pause scheduled runs in a window you choose, for example during your nightly maintenance, so planned work never triggers an alert.

Never goes dark

Pages that fail to load are reported in the same alert, and you get a warning before your checks run low. Monitoring never stops silently.

Website monitoring settings with interval, quiet hours, page-save checks and alert recipients
Fine-grained control

Tune every website in one panel.

Every client site gets its own settings: schedule, checks on page save, quiet hours, alert recipients, AI Rules and screenshot region. Basic Auth reaches password-protected staging sites, and a line of custom CSS hides a chat widget before the screenshot.

  • AI Rules per website: tell the AI once what to ignore.
  • Screenshot region: check EU sites from the EU, so they look the way visitors see them.
  • Basic Auth support for staging environments.
  • Run monitoring now: one click, or one API call at the end of your deploy script, checks every monitored page right away.
See the monitoring use case →
How it works

How website change monitoring works, step by step.

From adding a site to the first useful alert. The checks run in our cloud, nothing runs on your server.

STEP 01

Add your pages

Sync client pages automatically with our plugin for WordPress, import a sitemap, or add landing pages and checkout URLs by hand.

STEP 02

Set the schedule

Check from every 15 minutes to monthly, or check pages when they are saved, or both. Quiet hours keep your update windows free of alerts.

STEP 03

See the cost first

Your dashboard estimates the monthly checks for your pages, devices and schedule before you save.

STEP 04

Captures run on time

Full-page screenshots on desktop and mobile. Cookie banners, popups, sliders and animations are handled automatically.

STEP 05

AI filters the noise

AI verification sets aside rotating sliders, date stamps and other harmless changes, so only real problems reach you.

STEP 06

One email per check run

You get an email only when something really changed, with an AI summary and a link to the before and after view, plus a signed webhook for your own tools. Slack and other tools work via Zapier.

Why not by hand?

Daily click-throughs vs. continuous monitoring.

Checking manually

Clicking through client sites once a day eats developer time and only shows one moment. When a third-party chat widget breaks the mobile layout or a plugin auto-updates at 2:00 AM, the broken checkout stays live until an angry client calls.

With monitoring

Monitoring checks every client page on your schedule and again whenever someone saves it. AI verification sets the harmless changes aside, so your team hears only about layouts that really broke, and fixes them before clients or their customers notice.

In practice

Three alerts that paid for themselves.

The well-meant edit

An editor updates the homepage, saves, and goes to lunch. A new block now pushes the contact form off screen on mobile. A few minutes after the save, the check runs and the alert with a before/after link is in your inbox, before the first visitor gives up. See Continuous Monitoring.

The quiet hack

Injected spam links appear in the footer of an older site. Daily monitoring flags the new content on the next run; without it, this class of change routinely survives for months.

The expired campaign

Marketing’s promotion ends, but the banner keeps promising 20% off. The content change is flagged, and the public comparison link goes straight to the person who can fix the copy.

Tuning

Alert channels, AI Rules, and why there is no digest.

Alert emails are sent by our platform, not by the client’s WordPress, so they arrive even when the site is down. Connect signed webhooks for your own tools, or use Zapier to get alerts in Slack, ClickUp, Asana and other tools.

Leave the difference threshold at 0: AI verification already sets harmless changes aside, and AI Rules handle anything that keeps coming back.

There is deliberately no digest mode: a real change is worth an email now, not tomorrow morning. Automatic handling of banners and sliders, AI verification, AI Rules and quiet hours keep alerts rare enough to be read every single time.

FAQ

Frequently asked questions

How frequently can WebChange Detector monitor client websites?

From every 15 minutes for checkouts and lead forms, through hourly and daily, up to weekly or monthly for portfolio sites. With the plugin for WordPress, pages can also be checked a few minutes after someone saves them, next to the schedule or instead of it.

How do you prevent client inboxes from being spammed by false alerts?

Cookie banners, popups, sliders, animations, videos and ads are handled automatically, and moved content is not reported as broken. AI verification then marks harmless changes like rotating banners and date updates as OK, so you hear only about real changes.

Why are alert emails not sent from the client’s WordPress?

When a site crashes, its own mail often goes down with it. Alert emails are sent by our platform, not by the client’s WordPress, so they arrive even when the site is down.

Can I monitor password-protected staging environments?

Yes. You can store HTTP Basic Auth credentials per website, so private staging sites are checked like any other site, before launch and after.

What happens if a monitored site suffers a White Screen of Death (WSOD)?

A page that turns blank always triggers an alert, and error pages and unreachable pages are flagged with the reason. On Team plans and above, new JavaScript errors are detected as well, so the alert shows what broke, not only that something did.

How do quiet hours work for agency update windows?

Quiet hours pause scheduled runs in a time window you choose, for example 00:00 to 04:00, even across midnight. No run means no alert, so your team can push updates or migrate databases in peace.

Which alert channels are supported?

Email alerts, signed webhooks, and Zapier to connect Slack, ClickUp, Asana and many other tools.

Can I monitor non-WordPress websites?

Yes. Any publicly accessible URL or Basic Auth staging site can be monitored. The plugin for WordPress adds checks when a page is saved, Auto Update Checks and reviews inside wp-admin, but it is optional.

Catch the next visual bug before anyone else.

Start with a free trial, connect a site, and see your first before and after comparison today.