WordPress monitoring in 2026: manual, Google, tools, and continuous verification

The four approaches

'Monitoring' a WordPress site can mean very different things: is the server responding, are the Core Web Vitals healthy, is the site still indexable, did the last plugin update break checkout, is the SSL certificate about to expire? No single method covers all of it, which is why most sites end up using more than one.

The four approaches below — manual checks, Google's free tools, dedicated monitoring tools, and continuous verification — sit on a spectrum from 'free but all on you' to 'automated and broad'. Knowing what each is actually good at is the fastest way to stop paying for overlap or missing something important.

Checking it manually

The default for most site owners: load the homepage now and then, click through checkout before a big campaign, glance at the site on your phone. It costs nothing, needs no setup, and for a small, rarely-changing site it can be enough.

Its limits are structural, not a matter of discipline. Manual checks only happen when you remember, only cover what you think to look at, and only run while you're awake — so the first to notice a broken form, an expired certificate or a checkout that fails on mobile is usually a customer, not you. There's no history to diff against, and things you'd never check by eye — an accidental noindex tag, a broken hreflang cluster, a slow creep in Core Web Vitals — slip through entirely.

Google's free tools

Google Search Console, PageSpeed Insights (and the Lighthouse engine behind it) and Google Analytics are free, authoritative, and where every serious site should start. Search Console is the source of truth for how Google indexes and ranks you: index coverage, crawl errors, manual actions, and your field Core Web Vitals. PageSpeed Insights runs an on-demand lab audit plus that field data; Analytics shows real traffic and behaviour.

Where they stop is monitoring, in the continuous sense. They're dashboards you visit, not watchers that page you the moment something breaks — Search Console emails some issues, but with a lag. The field Core Web Vitals come from the Chrome User Experience Report as a 28-day rolling 75th-percentile, refreshed roughly daily in PageSpeed Insights but only where there's enough real traffic to report at all: a low-traffic page shows no data, and because the window is smoothed, a regression takes time to move the number rather than tripping an instant alert.

Most importantly, Google's tools don't test whether your site works. They won't tell you that a plugin update removed your 'Add to cart' button, that a contact form stopped submitting, that a redesign broke the layout on mobile, or that your certificate expires next week. That's simply not what they're for — and it's the gap the next two approaches fill.

Dedicated monitoring tools

A large ecosystem of purpose-built tools covers the ground Google doesn't, each excellent within its lane. Uptime monitors (UptimeRobot, Pingdom, Better Stack and others) ping your site every few minutes, track response time and SSL expiry, and alert in real time; some, on paid tiers, add synthetic 'transaction' checks that click through a flow like login or checkout. Security plugins and services (Wordfence, Sucuri, Jetpack Protect) handle firewalls, malware scanning and vulnerability detection. Performance monitors (SpeedCurve, Calibre, DebugBear and similar) track Core Web Vitals over time with alerting. Visual-regression tools (Percy, Chromatic, Applitools) diff screenshots, though they're aimed mostly at developers in a build pipeline. And all-in-one WordPress managers (ManageWP, MainWP, WP Umbrella, Jetpack) bundle updates, backups and an uptime add-on.

The honest catch is coverage and cost. Each tool is strong at its slice, but 'is my whole site working?' spans several slices — so you end up running three or four services, each with its own dashboard, configuration and bill. And a subtle point matters here: an uptime monitor's green check means the server returned a 200, not that the page is correct. Prices can be missing, a form can be dead, the layout can be broken, and a plain uptime check stays green through all of it. Verifying that a real customer can actually complete a purchase after an update is a different, harder job than pinging a URL.

Continuous verification

The newest category — where Relvato sits — tries to consolidate that harder job into one continuous system: instead of pinging a URL, it exercises the site the way a user and a search engine would, across many dimensions, and re-checks automatically when something changes. In practice that means uptime and SSL, Core Web Vitals in the lab plus real-user (RUM), visual-regression and structure-drift checks, broken links, and SEO and hreflang integrity — and, on WordPress specifically via a plugin, deeper WooCommerce checks like guest and logged-in checkout, payment methods, prices and stock, email delivery, background jobs, a vulnerability scan and file integrity.

Its defining trait is the trigger: because the WordPress plugin reports when a plugin, theme or core update lands, verification runs at the exact moment risk is introduced — not just on a fixed timer — and alerts you if a check that was passing starts failing. The honest trade-offs: it's a newer category than Google's tools or long-established uptime monitors; the deepest store checks need the plugin (the external checks don't); and it's a paid product. It also doesn't replace Google's search tools — Search Console stays where you see actual indexing and ranking; continuous verification complements it by making sure the site keeps working and your SEO tags don't silently break.

So which should you use?

For almost every site the answer is a combination, and two parts are close to non-negotiable. Set up Google's free tools — they're the authoritative, no-cost view of search and real-world performance, and nothing here replaces them. Then decide how you'll cover the part Google doesn't: whether the site actually works, looks right, and stays fast and available between the moments you happen to look.

For a simple, static, rarely-changing site, manual checks plus a free uptime monitor may genuinely be enough. For a site that changes often — a store, a site on a stack of plugins, anything where a broken checkout or a botched update costs real money — you want continuous, automated verification. You can assemble that from point tools if you prefer best-of-breed in each lane and don't mind several dashboards and bills, or use an all-in-one like Relvato to get functional, visual, performance and availability checks in one place, triggered by the updates that tend to break things. Neither is 'correct' — it's a trade between consolidation and specialisation.