Definitive WordPress Uptime Monitoring Guide for 2026

In one paragraph: WordPress runs roughly 43% of the web, and the right way to monitor a WordPress site depends entirely on what kind of site you have. If you run a personal blog, Jetpack Monitor or Velprove Free covers the homepage at no cost. If you run a WordPress-powered SaaS or membership site, you need a browser login monitor on wp-admin and a multi-step API monitor for your Stripe webhook path, which puts you on Velprove Pro or Better Stack Responder. If you run a WooCommerce store, you need synthetic checkout-flow monitoring on top of all of that. If you run an agency managing 5 to 50 client sites, the math changes and we route you into a dedicated guide. Paid Velprove tiers start at $19 per month for Starter and $49 per month for Pro, with no credit card required for free. And if you run a high-traffic enterprise WordPress publication on Pagely or WPEngine Premium, Velprove is not the right pick. The pillar below shows what to monitor for each segment, then routes you into the right deep dive.

Why WordPress needs different monitoring than other sites

WordPress powers roughly 43% of the web according to W3Techs, which means a meaningful share of monitoring conversations are actually WordPress monitoring conversations. The problem is that most generic uptime tools were not designed with WordPress-specific failure modes in mind, and the WordPress-specific failure modes are where outages actually happen.

Start with the most common one. Plugin and theme updates break sites with HTTP 200 still returned. The white-screen-of-death after a force-pushed Jetpack 12.1.1 or Really Simple Security 9.1.2 update returns a working HTTP status code with broken markup. A homepage HTTP keyword check that asserts the response code is 200 will say everything is fine while your visitors stare at a blank page. A keyword assertion against actual rendered content catches the breakage; a browser login monitor catches the related class of failure where the public site renders but wp-admin throws a fatal.

Then there is wp-admin login breakage independent of the public site. A plugin conflict, a corrupted .htaccess directive, or a security-plugin lockout policy can leave the homepage rendering while wp-login.php is unreachable. Standard homepage monitoring misses this entirely. The fix is a browser login monitor that drives wp-login.php and asserts the dashboard loads.

WP-Cron is not a real cron. It is a PHP-based scheduler that runs inside HTTP requests, which means on low-traffic WordPress sites (B2B portals, internal tools, off-hours blogs) scheduled events stop running entirely if nobody visits. A skipped backup or a missed post publication is invisible to homepage HTTP monitoring. The fix is to replace WP-Cron with a real server cron, and that is awareness rather than a Velprove pitch.

Maintenance mode returns HTTP 503 with a Retry-After header. Per Kinsta's WordPress maintenance mode guide, this is the correct response and crawlers are designed to back off. Monitors should treat short 503-with-Retry-After windows as expected. And on multisite networks, one shared database fault can take the whole network down at once, which is a class of failure to monitor for, not a number to predict.

What you actually need to monitor depends on which kind of WordPress site you run. The next five sections decompose that.

Solo blogger: what to monitor and why Velprove Free fits

The solo-blogger profile is narrow. You run a personal or hobby WordPress site. Your traffic is low. Your revenue dependency on uptime is zero or close to it. You publish on a cadence that suits you, and the monitoring bar is "let me know when the homepage is actually down so I do not find out from a friend."

What to monitor at this tier is also narrow. Homepage HTTP at a 5-minute interval. Email alerts you will actually read. Optionally SSL certificate expiry, because an expired cert silently kills your site for any visitor who follows a https link. That is the whole list. You do not need multi-step API monitoring, you do not need PagerDuty, and you do not need a status page with a custom domain.

Recommended pick: Velprove Free. Ten HTTP monitors at a 5-minute interval, one browser login monitor at a 15-minute interval (handy if you log into wp-admin from public networks and want to know it works), five global regions, one public status page with a Velprove badge, email alerts, and commercial use allowed. No credit card required. For a personal blog you will use one or two of the ten monitor slots and have the rest as headroom.

Honest competitor mention. Jetpack Monitor is the strongest "good enough" free alternative for this segment. Per Jetpack's downtime monitor docs, it runs from Automattic's servers, checks every 5 minutes, and sends email plus mobile push notifications. It is activated from the WordPress.com dashboard under Settings then Security. It does not cover wp-admin login monitoring or multi-step API checks, but for a hobby blog those are not the bar.

UptimeRobot Free at 50 monitors works only if your blog is genuinely non-commercial. The Terms of Service changed in late 2024 to restrict the free tier to personal use. If your blog has ad revenue, affiliate links, sponsorships, or anything resembling a monetized footer, the free tier is not for you and Velprove Free or Jetpack Monitor is the cleaner pick. When the blog adds a paid newsletter, course, or membership, the segment changes and the next H2 applies.

WP-powered solo SaaS or membership site: Velprove Pro

The solo-SaaS profile looks like an indie product running on WordPress. A membership site on MemberPress or Paid Memberships Pro. A course platform on LearnDash or LifterLMS. A B2B tool whose login flow is the conversion funnel. The monitoring surface is no longer "is the homepage up." It is "is my login flow working, is the customer-facing login flow working, are Stripe webhooks arriving, and is SSL not about to expire."

What to monitor at this tier is a four-monitor stack at minimum. Homepage HTTP. A browser login monitor on wp-admin to catch your own lockouts. A browser login monitor on the customer-facing login page (the pmpro-account page, the MemberPress dashboard, the MemberMouse account portal). A multi-step API monitor that walks the Stripe webhook receipt path and asserts the success response. SSL expiry monitoring is a fifth low-effort add.

The browser login monitor on wp-admin is the differentiator the rest of the market does not match on free. Of every WordPress monitoring option in the matrix below, only Velprove includes a browser-based login monitor on a free tier. Checkly does include 5 browser checks on free, but Checkly requires writing Playwright scripts in version control. For a solo founder running on WordPress, that is more engineering investment than the point-and-click setup Velprove offers.

Recommended pick: Velprove Pro at $49 per month. One hundred HTTP monitors at 30-second intervals, ten browser login monitors at 5-minute intervals (enough for both admin and customer login plus headroom), multi-step API up to ten steps for the Stripe webhook receipt path, all five global regions, custom-domain status pages, PagerDuty plus Slack plus Discord plus Teams plus webhooks, and SSL monitoring built in. Velprove Free covers about half of this need with one browser login monitor at 15-minute interval, which is fine for the admin side but does not stretch to cover the customer side.

Honest competitor mention. Better Stack Responder at $34 per month monthly ($29 annual) bundles incident management and log aggregation with a metered Playwright transactions surface. If your team has a developer who will own Playwright scripts in version control, Better Stack is a defensible alternative. For MemberPress, Paid Memberships Pro, MemberMouse, or WishList Member specifically, the membership-site login monitoring deep dive walks through MemberPress, Paid Memberships Pro, and the Stripe webhook receipt monitor.

WooCommerce shop: checkout flow plus Stripe webhook monitoring

The WooCommerce profile is revenue-on-uptime. Cart abandonment is a real cost. A 30-minute checkout outage on a busy Saturday is measurable money lost. Your homepage being green while the checkout API returns 500s is the worst version of a partial outage, because customers reach the moment of intent and bounce before you know anything is wrong.

What to monitor at this tier is the most aggressive of any segment. A synthetic checkout-flow monitor that adds a product to cart, proceeds through checkout, asserts the payment-method selection step renders, and confirms the success page. A multi-step API monitor for the cart and checkout REST routes which depend on session state and tokens passed between requests. A browser login monitor for the customer account portal so you catch the partial outage where the storefront works but logged-in customers cannot reach order history. SSL expiry monitoring, because an expired cert kills checkout instantly. Regional probes near customer concentrations so you see what European or Asian customers see. And a Stripe webhook receipt monitor so you know immediately if Stripe events are not arriving.

The Stripe side has a useful default. Per the WooCommerce Stripe extension docs, "since version 8.6.1 of the Stripe extension, webhooks are automatically set up when you connect to Stripe." That removes one source of misconfiguration but does not remove the need to actively verify the webhook delivery path; for a high-volume store, "stores processing more than 1,000 orders per day should consider offloading webhook processing to a message queue."

Recommended pick: Velprove Pro at $49 per month. Multi-step API up to ten steps covers a chained add-to-cart through payment-confirmation flow. Ten browser login monitors at 5-minute intervals cover the customer account portal and any admin-side flows. Five regions, custom-domain status pages, PagerDuty escalation, and SSL monitoring round it out. Velprove Free does not stretch this far: the 3-step multi-step API cap on Free will not cover a full checkout flow, and one browser login monitor is not enough for both admin and customer surfaces.

Honest competitor mention. Pingdom or Site24x7 win if RUM (real user monitoring) is a hard requirement for your conversion-rate optimization work. Velprove does not include RUM today. For a WooCommerce shop with a dedicated growth team that wants real-user performance data on top of synthetic checks, Pingdom is the typical pick with the budget to match. There is no published Velprove guide that walks through WooCommerce checkout monitoring end to end yet; that is a future spoke. This pillar names WooCommerce as a real segment without overpromising.

WordPress agency (5 to 50+ clients): see the agency playbook

The agency profile is reseller-shaped. You maintain a portfolio of client WordPress sites under retainer. Each client expects professional monitoring as part of the service. You need white-label status pages on a custom domain per client, multi-client monitor grouping in one dashboard, browser login monitors on each client's wp-admin, and flat pricing rather than per-monitor metered cost so the unit economics work as the client roster grows.

The math is unforgiving and worth saying once. Fifty client sites times three to five monitors per client lands at 150 to 250 monitors. Velprove Pro caps at 100 monitors. Above roughly ten client sites with browser login monitoring on each, the agency math starts to push past the Pro tier and a different tool gets serious consideration. Below ten clients, Velprove Pro at $49 per month is the lowest-cost flat-fee pick that includes browser login monitoring on every client.

This pillar deliberately does not re-litigate the Velprove Pro vs Hyperping Pro vs Hyperping Business comparison; that whole story, including the per-client status page setup, the white-label alert email configuration, and the math at 5, 25, and 50 clients, lives in the agency playbook. The dedicated WordPress agency monitoring guide covers per-client status pages, the Velprove Pro vs Hyperping math at 5, 25, and 50 clients, and the white-label client-facing alert setup.

Enterprise WordPress and SOC 2 procurement

Velprove is not the recommended pick for this segment. The enterprise WordPress profile is a high-traffic publisher (news, magazine, content-heavy site) running on Pagely, WPEngine Premium, Pressable Premium, or WordPress VIP. Real revenue comes from ad inventory and page views, not from login flows. The monitoring requirements come from procurement, not from engineering instinct.

What enterprise WordPress procurement asks for from a monitoring vendor is explicit. SOC 2 Type II attestation the customer's security team can review. SAML SSO so the monitoring tool fits inside a centralized identity perimeter. A Terraform provider so monitor lifecycle is managed in version control alongside the rest of the infrastructure. Real user monitoring (RUM) for the user-experience metrics that complement synthetic checks. Page-speed waterfall analytics. Seventy or more probe locations for global performance benchmarking. Escalation policies with L1-to-L2 routing rules. A dedicated customer success manager who picks up the phone.

To be direct: Velprove does not include SOC 2 Type II, SAML SSO, a Terraform provider, RUM, or page-speed waterfall analytics today. If any of those features are non-negotiable for your procurement cycle, you need a different tool. The honest framing is that Velprove is calibrated for solo bloggers, WP-powered solo SaaS, WooCommerce shops, and agencies under roughly ten clients. Enterprise WordPress publishing is a different market.

Recommended picks: Pingdom for RUM and waterfall analytics with the budget to match. Site24x7 for the all-in-one observability bundle (APM, RUM, log management, network device monitoring). Uptime.com is the typical pick for SOC 2 plus Terraform procurement requirements, with 80+ probe locations and a no-code transaction recorder starting at $7 per month annual. The deeper trade-offs across those three live in our Site24x7 alternative breakdown.

One related anchor worth keeping in mind. Even on a host that advertises a 100% uptime SLA, like Pressable Premium, or six-nines historical uptime, like Pagely's enterprise tier, you still need external monitoring as the evidence layer. Even hosts that advertise 100% uptime SLA require you to file a credit claim with your own evidence; the host's own status page is not the evidence.

WordPress monitoring plugin landscape

The WordPress reader has a tempting alternative path: install a plugin that does monitoring from inside WordPress, or run a self-hosted dashboard plugin that monitors your other WordPress sites. Both are legitimate options for some readers and both have a structural-honesty problem worth naming.

The structural-honesty axis is "where does the monitoring run from?" Self-hosted dashboard monitoring (MainWP) runs from your own server. If your dashboard server goes down, your monitoring goes down with it. Plugin-internal monitoring runs from inside the WordPress install you are trying to monitor; if that install goes down, the plugin cannot tell you. External vendor monitoring (Jetpack Monitor, ManageWP, WP Umbrella, MalCare, Solid Central, Velprove, UptimeRobot, Better Stack) runs from outside your network and is the only structurally-correct shape. The matrix below makes the "runs from where" axis explicit.

Two takeaways the matrix makes obvious. First, of all the WordPress monitoring options listed (and including Checkly, which is omitted from the table because it is not WordPress-specific), only Velprove and Checkly include a browser-based monitor on a free tier, and Checkly requires writing Playwright scripts. Velprove is point-and-click. If you need to verify a logged-in WordPress flow without writing code, that narrows the field to one vendor on free. Second, MainWP is the only self-hosted option in the matrix, and the structural problem is real: monitoring that runs from your own server inherits your server's availability. The plugin-free WordPress monitoring guide covers external monitoring approaches that don't require touching wp-content/plugins.

Where to go next

The whole point of this pillar is to route you into the right deep dive for your specific situation. Six WordPress monitoring spokes live alongside this guide, each one written for a single reader symptom or use case. Pick the one that matches.

• If your WordPress site is going down right now and you don't know why, our diagnostic guide on 7 common causes of WordPress downtime walks through the most common patterns and what each one looks like from the outside.
• If you specifically need to monitor your wp-admin login page, our step-by-step wp-admin login monitor tutorial covers the setup including the dedicated Subscriber-role test account, region selection, and assertion configuration.
• If you don't want to install another plugin on your site, our plugin-free WordPress monitoring guide covers external monitoring approaches that work without touching wp-content/plugins.
• If you run a paid WordPress membership site (MemberPress, Paid Memberships Pro, MemberMouse, WishList Member), our WordPress membership site login monitoring guide covers the customer-facing login flow and the Stripe webhook receipt monitor.
• If you just had a plugin update break a client site, our plugin-update-breakage detection guide covers what to monitor so the next force-pushed update is caught in seconds rather than days.
• If you're a WordPress agency monitoring 5 to 50+ client sites, our WordPress agency monitoring playbook covers white-label status pages, per-client setup, and the Velprove Pro vs Hyperping math at scale.

And if you're doing broader vendor evaluation across the full uptime monitoring market (not just WordPress), our 2026 buyer's guide to choosing the right uptime monitor compares 15 vendors across solo founder, ecommerce, SaaS, agency, enterprise, and hosting-reseller use cases.

Frequently Asked Questions

Do I need a WordPress uptime monitor?

If your WordPress site earns money, processes transactions, or holds member or customer data, yes. WordPress runs roughly 43% of the web, and the most common failure modes (plugin auto-updates breaking the site with HTTP 200 returned, wp-admin login locking out independently of the public site, WP-Cron silently stopping on low-traffic sites) are invisible to a standard browser refresh. A monitoring tool catches these in seconds rather than after a customer reports them. Personal hobby blogs without revenue are the one exception, and even there a free monitor like Velprove Free or Jetpack Monitor is worth the five minutes of setup.

Is Jetpack Monitor enough?

For a personal blog with no revenue dependency on uptime, Jetpack Monitor is fine. It runs from Automattic's servers, checks your homepage every 5 minutes, and sends email plus mobile push notifications. It does not cover wp-admin login monitoring, multi-step API checks for Stripe webhook flows, response-time thresholds, custom status pages, or multi-region probes. If your WordPress site monetizes anything (membership, ad revenue, ecommerce, courses), a richer tool such as Velprove Free covers more ground at the same cost.

Should I use a WordPress monitoring plugin or an external service?

External monitoring is structurally correct. Plugin-based or self-hosted-dashboard monitoring (MainWP, plugin-internal trackers) inherits the availability of the thing it's trying to monitor. If your WordPress install or your MainWP dashboard goes down, plugin-based monitoring goes down with it. The whole point of independent monitoring is that it runs from outside your infrastructure, so it can detect outages your servers cannot self-report. Use external services like Velprove, Jetpack Monitor, ManageWP, WP Umbrella, UptimeRobot, or Better Stack instead.

How do I monitor wp-admin login?

A browser login monitor drives wp-login.php with a real browser, enters credentials for a dedicated low-privilege test account (Subscriber role, never your primary admin), and asserts that the wp-admin dashboard renders. If any step fails, you get an alert with an optional screenshot. Velprove Free includes one browser login monitor at 15-minute interval and is point-and-click to set up. The full step-by-step setup walks through credential storage, region selection, and assertion configuration in our dedicated wp-admin login monitoring tutorial.

What's the cheapest WordPress uptime monitor?

Free is the cheapest, and several vendors offer commercial-use-allowed free WordPress monitoring tiers. Velprove Free includes 10 HTTP monitors plus 1 browser login monitor across 5 regions with email alerts. Jetpack Monitor is free for any WordPress site with the Jetpack plugin connected. UptimeRobot Free at 50 monitors is the highest raw count, but personal-use-only since late 2024, so it's not usable for monetized sites. Among paid floors, ManageWP Uptime Monitor is $1/site/month, WP Umbrella is around $2.20/site/month, UptimeRobot Solo is $9 annual, and Velprove Starter is $19/month for 25 monitors with 1-minute intervals.

Does WP-Cron run if nobody visits the site?

No. WP-Cron is not a real cron job. It's a PHP-based scheduler that runs inside HTTP requests, so on low-traffic WordPress sites (B2B portals, internal tools, off-hours blogs), scheduled events like backup runs, post publication, and email sending stop running entirely. The fix is to disable WP-Cron in wp-config.php with DISABLE_WP_CRON set to true and call wp-cron.php from a real server cron every 5 minutes. Standard homepage HTTP monitoring will not catch a skipped scheduled task; that's a separate monitoring concern handled by heartbeat-style monitors.

How should monitors handle WordPress maintenance mode?

WordPress maintenance mode returns HTTP 503 with an optional Retry-After header. This is the correct response code; search engine crawlers are designed to back off and retry after the indicated delay. Monitors should treat short 503-with-Retry-After windows as expected rather than as outages. The cleanest pattern is to either configure the monitor to treat 503 as a non-failure for a short window, or pause the monitor manually before scheduled plugin and core updates. Velprove's monitor pause is a manual toggle today; auto-suppression of maintenance windows is not a Velprove feature.

If your WordPress site fits one of the four Velprove-recommended segments above (solo blogger, WP-powered solo SaaS, WooCommerce shop, or agency under 10 clients), start a free Velprove account. The free plan includes 10 HTTP monitors across 5 global regions, a browser login monitor for your wp-admin or customer-facing flow, multi-step API monitors up to 3 steps, and a public status page. No credit card required.