Uptime Monitoring for WordPress: Tools and Setup Guide

Your WordPress site going down is one of the worst things that can happen - especially if you do not find out about it for hours. Uptime monitoring sends you an alert within minutes of downtime, gives you historical data to identify patterns, and helps you make the case for better hosting when your SLA is being violated.

This guide covers the five most practical uptime monitoring tools for WordPress sites in 2026 - UptimeRobot, Pingdom, Better Uptime, StatusCake, and WP Health Check - with setup instructions, alerting configuration, and guidance on what to monitor beyond just “is the homepage loading.”

What to Monitor on a WordPress Site

Most uptime monitors default to checking the homepage URL every 5 minutes. That is a reasonable starting point but not sufficient for a production WordPress site. A comprehensive monitoring setup covers:

• Homepage HTTP check: Basic availability and correct HTTP 200 response
• wp-login.php keyword check: Verify the login form loads (catches database connection errors that return 200 from a cached page)
• WooCommerce checkout URL: If you run an ecommerce site, the checkout page down = revenue lost immediately
• REST API endpoint: GET /wp-json/ returns a 200 with correct JSON content type
• SSL certificate expiry: Alert 30 days before certificate expires
• DNS resolution: Verify DNS is resolving correctly from multiple locations
• Response time: Alert if TTFB exceeds a threshold (e.g., 2 seconds)

UptimeRobot: Free Tier That Actually Works

UptimeRobot has a free plan that covers 50 monitors with 5-minute check intervals. For most WordPress sites, this is enough. The paid plans start at $7/month for 1-minute intervals and advanced alerting.

Setting Up UptimeRobot

1. Create an account at uptimerobot.com
2. Click Add New Monitor
3. Select HTTP(s) monitor type
4. Enter your WordPress site URL
5. Set check interval to 5 minutes (free) or 1 minute (paid)
6. Configure alert contacts (email is built in; Slack/SMS require paid or integration)

Keyword Monitoring for WordPress

UptimeRobot’s keyword monitor type is powerful for WordPress. Instead of just checking the HTTP status code, it checks whether a specific word appears (or does not appear) in the response body. This catches situations where a page loads with HTTP 200 but shows a database error or maintenance mode message.

Useful keyword monitors for WordPress:

UptimeRobot Alerting

On the free plan, UptimeRobot sends email alerts. For Slack notifications, add an Integrations block in your Slack workspace and copy the webhook URL into UptimeRobot’s alert contacts. For SMS, the paid plan includes SMS credits.

Pingdom: Enterprise-Grade with a Friendly Interface

Pingdom (now part of SolarWinds) is the industry standard for uptime and performance monitoring. Plans start at $10/month. It offers 1-minute check intervals, global probe locations, and transaction monitoring (multi-step checks that simulate user actions like login or checkout).

Pingdom Transaction Monitoring for WooCommerce

Pingdom’s transaction monitoring simulates real user flows. For a WooCommerce store you can set up a monitor that:

1. Loads the homepage
2. Navigates to a product page
3. Adds a product to the cart
4. Proceeds to checkout
5. Verifies the checkout form loads

If any step fails, Pingdom alerts you. This is significantly more valuable than a simple HTTP check because it catches application-level failures that still return HTTP 200.

Pingdom Real User Monitoring (RUM)

Pingdom also offers RUM - Real User Monitoring - which instruments actual visitor sessions to measure load times, not just synthetic checks from Pingdom’s servers. RUM data gives you page load times broken down by browser, country, and device type. Adding the Pingdom RUM snippet to WordPress is straightforward:

Add the snippet to your theme’s functions.php using wp_enqueue_script, or use a plugin like WP Code to inject it into the header. The snippet is a small JavaScript file from Pingdom’s CDN that tracks performance metrics for real visitors.

Better Uptime: Status Pages and Incident Management

Better Uptime stands out for its built-in status page feature and on-call scheduling. If you run a WordPress site or SaaS product built on WordPress and have customers who need to know about outages, a public status page is essential. Plans start at $24/month for teams.

Setting Up a WordPress Status Page

1. Create monitors in Better Uptime for each critical URL
2. Group monitors into a status page (e.g., “Website”, “API”, “Checkout”)
3. Set a custom subdomain (status.yoursite.com) via CNAME
4. Configure incident policy - manually update status or auto-update when monitors fail

Better Uptime also integrates with PagerDuty, OpsGenie, and Slack for on-call rotation. If you are on a small team, the built-in on-call scheduling is sufficient.

Better Uptime Heartbeat Monitoring

Heartbeat monitoring is the reverse of HTTP monitoring - instead of Better Uptime pinging your site, your site pings Better Uptime. This is useful for monitoring WordPress cron jobs. If a cron job does not complete, the heartbeat ping is never sent and you get an alert.

Set up a heartbeat for WordPress scheduled backups, cache-warming scripts, or any background job that must run regularly. Add the heartbeat ping URL to the end of the job’s completion hook in WordPress.

StatusCake: Multi-Location Monitoring with a Generous Free Plan

StatusCake’s free plan includes unlimited HTTP monitors with 5-minute intervals and SSL monitoring. Paid plans start at $20/month for 1-minute intervals and more check locations. StatusCake’s global monitoring network covers over 40 locations.

WordPress SSL Certificate Monitoring

StatusCake’s SSL monitoring checks your certificate expiry date and sends an alert 30, 14, and 7 days before expiry. Enable it per site from the SSL Tests section of the dashboard. For WordPress sites on managed hosting with auto-renewing Let’s Encrypt certificates, SSL monitoring provides a safety net for renewal failures.

Domain Expiry Monitoring

StatusCake also monitors domain registration expiry. Add your domains to the Domain Monitoring section with alerts at 30 and 7 days before expiry. Domain expiry is an under-monitored risk - a lapsed domain takes your site completely offline and can be picked up by a squatter within hours.

WP Health Check: On-Site WordPress Diagnostics

WP Health Check is the built-in WordPress feature accessible at Tools - Site Health. It is not an external uptime monitor but it catches configuration issues that external monitors miss: outdated PHP versions, inactive plugins causing security risks, background task failures, database performance issues, and file permission problems.

Run Site Health checks monthly. The “Info” tab provides detailed server configuration data useful for debugging hosting issues. The “Status” tab shows immediate action items.

WP Health Check Scheduled Email Reports

The Health Check & Troubleshooting plugin (official WordPress plugin) extends Site Health with scheduled email reports. Install it to get a weekly email summary of your site’s health status, so configuration drift does not go unnoticed between manual checks.

Comparing Monitoring Tools by Use Case

Setting Up Alerting That Does Not Create Alert Fatigue

Getting the alerting configuration right matters as much as setting up the monitors. Too many alerts and you start ignoring them. Too few and you miss real incidents.

• Confirmation checks: Most monitors support confirming from multiple locations before alerting. Use 2+ confirmation locations to avoid false positives from a single probe server issue.
• Escalation policy: Alert by email first, then SMS after 10 minutes if not acknowledged. Only page on-call team after 20+ minutes of confirmed downtime.
• Maintenance windows: Silence alerts during scheduled maintenance. All major monitoring tools support maintenance window scheduling.
• Response time alerts: Set a separate alert for response time threshold (e.g., TTFB over 3 seconds) at a lower urgency than downtime alerts. Slow is bad, down is worse.
• Group by priority: Checkout page down = P1 immediate alert. Blog post page slow = P3 next-business-day review.

SLA Monitoring and Uptime Reports

If your hosting provider guarantees a 99.9% uptime SLA, you need your own uptime data to hold them to it. 99.9% uptime allows approximately 8.7 hours of downtime per year. 99.99% allows 52 minutes per year.

All the tools listed here provide historical uptime reports. Export monthly reports from your monitoring tool and compare against your hosting SLA. If your host’s SLA is being violated, you typically have a path to service credits or contract termination. The data from your monitoring tool is your evidence.

Recommended Setup for Different WordPress Site Types

Personal Blog or Portfolio

UptimeRobot free plan is sufficient. Monitoring catches downtime but you should also track other factors affecting your page load time. Set up 3 monitors: homepage HTTP check, keyword check for your site name, keyword check for database errors. Email alerts only.

Business Site

UptimeRobot paid (1-minute intervals) plus StatusCake for SSL and domain monitoring. Add Slack integration so the team sees alerts. Set up keyword monitoring for the contact form page.

WooCommerce Store

Pingdom or Better Uptime for transaction monitoring covering the full checkout flow. UptimeRobot as a backup monitor. Better Uptime status page so customers can check status during incidents. Heartbeat monitoring for backup and inventory sync cron jobs.

Quick Setup Checklist

• Homepage HTTP monitor with 1-5 minute interval
• Keyword monitor checking for correct site content
• Keyword monitor checking for database error message (keyword NOT present)
• SSL certificate expiry monitor (alert at 30 days)
• Domain expiry monitor (alert at 30 days)
• WooCommerce checkout monitor (if applicable)
• Response time alert threshold set
• Slack or SMS alert configured (not just email)
• Maintenance window scheduled for planned deployments
• Monthly uptime report exported and saved for SLA reference

Understanding Uptime Monitoring Check Intervals

The check interval determines how quickly you learn about downtime. A 5-minute interval means your site could be down for up to 5 minutes before you receive an alert. On a business site doing $500/hour in revenue, that is $41 of potential lost revenue before you even know there is a problem.

One-minute intervals are available on paid plans for all the tools covered in this guide. For ecommerce sites or sites with high traffic during business hours, 1-minute intervals are worth the subscription cost. For personal sites or low-traffic blogs, 5-minute free monitoring is perfectly adequate.

How Monitor Checks Work

HTTP monitors work by sending a GET request to your URL from a monitoring server and checking the response code. A 200 response means up. A 4xx or 5xx response, a timeout, or a connection refused error triggers a down event. The monitoring service then waits for the configured confirmation period (often 1-2 additional checks from different servers) before sending an alert to avoid false positives from brief network issues.

Some monitoring tools let you configure what constitutes a down state. By default, most treat any response under 2xx or above 300 as down. But you might want to alert on a 301 redirect (which could indicate a misconfigured site) or on specific response time thresholds even for successful responses.

Integrating Uptime Monitoring with Your Incident Response Process

Getting the alert is only the first step. Having a clear response process means downtime gets resolved faster. A simple incident response runbook for WordPress sites:

1. Receive alert: SMS or Slack notification from your monitoring tool
2. Verify independently: Load the site from your phone on cellular data (not WiFi - rules out local network issues). Try a different browser.
3. Check hosting status page: Most hosts have a status page (e.g., status.kinsta.com). If there is an active incident on the host’s side, no debugging needed - wait for resolution and track SLA time.
4. Check server resources: If hosting is up, SSH into the server and check CPU/memory usage. A runaway process or memory exhaustion is a common cause of WordPress downtime.
5. Check WordPress error logs: Review wp-content/debug.log and the server PHP error log. Fatal errors in plugins often cause 500 errors with no visible page output.
6. Deactivate plugins via WP-CLI or FTP: If a plugin update coincided with the downtime, deactivate it. Use wp plugin deactivate - all via WP-CLI to isolate the issue if you cannot access wp-admin.
7. Restore from backup: If the cause is unclear and the site is fully down, restore from the most recent clean backup and investigate the cause in a staging copy.

Keep this runbook in a shared doc your team can access even when the site is down. A Google Doc or Notion page accessible from any device is better than documentation hosted on the very site that is down.

Multi-Location Monitoring: Why One Check Location Is Not Enough

Single-location monitoring has a failure mode: the monitoring server itself may have network issues, causing false down alerts. Most production uptime tools check from multiple locations simultaneously and require confirmation from at least two locations before alerting. This significantly reduces false positives.

Multi-location monitoring also reveals geographic issues. A site might appear up from a US monitoring server but down from Europe due to a DNS issue, CDN misconfiguration, or regional network problem. UptimeRobot paid, Pingdom, Better Uptime, and StatusCake all support multi-location checking. Enable it.