Your WordPress site updated. Did anything break?

No. Sitewatch monitors your site from the outside, the way a visitor's browser does. There is nothing to install, nothing that can slow your site down, and nothing that goes offline when WordPress itself is struggling. Setup takes about a minute — paste your URL and go.

Yes. When an update renames or removes a file your page still points at, that file is no longer served — and the form, slider or checkout depending on it silently stops working. Sitewatch checks every script and stylesheet your pages load, so a missing one becomes an incident naming the exact file, even though WordPress still answers normally.

Yes. Because monitoring happens externally, it works with WP Engine, Kinsta, SiteGround, Cloudways, shared hosting and self-hosted WordPress alike. If your site loads in a browser, Sitewatch can monitor it.

Yes. Sitewatch verifies that your theme's stylesheets, fonts and scripts are actually being served. A theme update that drops or renames one of them shows up as a missing file on the affected pages, usually before anyone visits.

Yes. Page builders like Elementor, Divi and Beaver Builder load a lot of their own scripts and styling, which makes them especially prone to breakage after updates. Because Sitewatch verifies everything the page actually loads — not just the homepage content — it catches a builder file that has gone missing or is being served as an error page, whichever builder produced the page.

Yes. Add your cart and checkout as critical pages and they are checked on their own schedule with their own alerts, so if an update breaks the purchase flow you hear about it before customers cannot buy. See WooCommerce monitoring for the store-specific checks.

Yes. The white screen of death is usually a fatal error or plugin conflict that leaves a blank page — often while the server still reports success, which fools basic uptime checks. Sitewatch compares the rendered page against its baseline, so a sudden collapse to an empty page raises an incident regardless of what the server reported.

Sitewatch is not a malware scanner, but it surfaces the symptoms of a compromise from the outside: unfamiliar third-party scripts appearing on your pages, content drifting from its known-good baseline, new redirects to domains you do not control, and security headers that suddenly disappear. Catching those early — before Google flags you or visitors see spam — is often the difference between a quick cleanup and a blocklisted domain.

Checks run every 30 minutes on the free plan, every 15 on Starter and every 5 on Pro. Connect a deploy hook to your update workflow and the check runs the moment you click "Update", so you find out within minutes rather than at the next interval. Every issue is confirmed with a retry first, so what reaches you is real.

Yes, and that is the point. Sitewatch does the fundamental availability checks — outages, timeouts, server errors, certificate expiry — and then keeps going to verify the page actually works. You get classic uptime monitoring plus the checks that catch post-update breakage, in one tool.

Yes. Sitewatch runs multiple sites from a single dashboard — up to 25 on Starter and 100 on Pro — with independent checks, per-site alert routing and client-facing status pages. Agencies typically use a separate workspace per client to keep alerts and data isolated.

It depends on what you need to catch. Plugin-based tools like Jetpack or ManageWP run inside WordPress and are strong on updates and backups, but they can go offline with the site they live on. Ping-based tools like UptimeRobot or Pingdom confirm the server responded but miss page-level breakage. Sitewatch is built for the failure that follows an update — a missing file, a stale cache, a redirect loop, all of which return a perfectly normal response — and it runs externally, so it keeps working when WordPress does not.

No. Sitewatch focuses on whether the site works: what loads, the redirects, availability, certificates and content changes. It does not measure load time or Core Web Vitals. Pair it with PageSpeed Insights if speed is what you need.