WordPress uptime monitoring in 10 minutes

Set up uptime monitoring for a WordPress or WooCommerce site in 10 minutes: keyword checks for white screens, a page your cache can't hide, WP-Cron, SSL and domain expiry.

· 5 min read · By the Spot Downtime team

WordPress sites rarely go down cleanly. More often the server answers but the page is wrong: a blank white screen after a plugin update, “Error establishing a database connection”, or a cached home page that hides a broken checkout. A basic “is it up?” check passes through all of these. Here's a setup that catches them.

What can go wrong, and what catches it

ProblemWhat a visitor seesWhat catches it
Host or server downPage won't loadAny website check
Plugin or theme fatal errorBlank page or "There has been a critical error"A Page must contain keyword
Database down or out of connections"Error establishing a database connection"Status code check (it's a 500) or keyword
PHP broken behind a page cacheHome page fine, cart and login brokenA second check on an uncached page
WP-Cron not runningScheduled posts and emails never go outA heartbeat
Certificate or domain expiresBrowser warning, or nothing at allSSL and domain expiry checks

1. Check the home page for a keyword

  1. In Spot Downtime, click Add monitor and choose Website.
  2. Enter your home page in URL, like https://example.com/.
  3. In Page must contain, put text that's only on a working page: your site name in the footer, or a menu item. Avoid text that also appears on error pages.
  4. Pick Check every (5 minutes on Free, down to 30 seconds on Pro) and click Add monitor.

If a plugin update leaves a white screen, the page still returns 200 but the text is missing, so the monitor goes down. That's the outage plain uptime checks miss most often. See fixing the white screen of death for what to do next.

2. Check a page your cache can't hide

Caching plugins and hosts serve saved copies of pages, so the home page can look fine while PHP or the database is down. Add a second Website monitor on a page that's never cached:

  • WooCommerce: /cart/ or /my-account/, with a keyword like “Cart”.
  • Any site: /wp-login.php, with the keyword “Password”.

3. Make sure WP-Cron actually runs

WP-Cron only runs when someone visits, so on quiet sites (or behind a full-page cache) scheduled posts, backups and emails quietly stop. The fix is a real cron job, plus a heartbeat so you know it's running. Turn off the visit-triggered version in wp-config.php:

php
define('DISABLE_WP_CRON', true);

Then add a Heartbeat monitor in Spot Downtime, copy its URL, and run WP-Cron from your server's crontab (or your host's cron panel) every 5 minutes, pinging the heartbeat when it succeeds:

*/5 * * * * curl -fsS -m 30 "https://example.com/wp-cron.php?doing_wp_cron" > /dev/null && curl -fsS -m 10 --retry 3 https://YOUR-HEARTBEAT-URL > /dev/null

If the job stops, the ping stops and you get an alert. Heartbeats are on paid plans; the heartbeat docs have more examples.

4. SSL and domain expiry come free

Every HTTPS monitor also watches the certificate and the domain registration, and warns you before either expires. Nothing to set up. Handy if your host's auto-renewal fails, or the card on your domain registrar expired.

Your host's monitoring isn't enough

Managed WordPress hosts like SiteGround, Cloudways, Kinsta and WP Engine watch their own servers. That's useful, but it's checked from inside their network and it watches the server, not your pages. An external check sees what visitors see: DNS, the CDN, the certificate and the page itself. When the host has a problem, you also hear about it from someone other than the host.

Free for one WordPress site and more

The Free plan covers 20 monitors with keyword checks, SSL and domain expiry warnings, and alerts to email, Slack and more. That's enough for steps 1, 2 and 4 on several sites. See website monitoring.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading