Uptime monitoring for WordPress sites
Monitor the home page every 60 seconds with a rule that the page must contain your site name or footer text, so a white screen or a plugin error that still answers 200 counts as down. Add wp-login.php and the certificate reminder, and schedule plugin updates in a maintenance window.
The five ways a WordPress site goes down
- 503 Service Unavailable during a plugin or core update: WordPress puts up a maintenance page. It should last seconds; when an update hangs, the .maintenance file stays and the site is down until someone deletes it.
- A fatal error after a plugin update: either a plain 500, or a 200 with "There has been a critical error on this website" in the body. The second one fools a status-code-only monitor.
- A white screen: 200 with nothing on it, usually PHP memory or a theme error.
- Certificate didn't renew: the Let's Encrypt cron on the host failed quietly, and 90 days later browsers show a warning.
- Shared hosting timeouts: the page takes 20 seconds or never answers at 9 a.m. when every site on the box is busy.
What to monitor
| Page / URL | Check | Why |
|---|---|---|
| Home page | Status 200 and contains your site name or footer text, every 60 s | A text rule catches white screens and "critical error" pages that still answer 200. |
| Home page (same monitor) | Does not contain "critical error" or "Briefly unavailable" | Names the two most common WordPress failure pages as down. |
| /wp-login.php | Status 200 and contains "Log In" | If you can't log in, you can't fix anything else. |
| A key page (/shop/, /contact/, /book/) | Status 200 and contains a phrase from the form | The page that earns money breaks separately from the home page. |
| /wp-json/ | Status 200 and contains "namespaces" | The REST API; when it fails, the block editor and many plugins fail with it. |
| Certificate (automatic) | Reminders at 14, 7, 3 and 1 days | Auto-renewal fails more often than hosts admit. |
Plugin updates without false alarms
Schedule a maintenance window before you update plugins, themes or core. Checks keep running and are recorded, so you still see whether the site came back, but nothing is alerted and the status page shows planned maintenance. If the update breaks something after the window ends, you're told the normal way, with the status code or the matched text as the cause.
A good habit: update on staging first, monitored by a separate monitor that alerts only a quiet channel, then update production inside a 15-minute window.
Cheap hosting and timeouts
Shared hosting is slow at busy times rather than down. heyUptime records response time on every check, and the weekly summary shows the average per monitor, which is the number to put in front of your host when asking for a better plan. A request that takes longer than the check timeout counts as down; two in a row and you're alerted with "timed out" as the cause.
Every failure is confirmed by a second check before anyone is alerted, so a single slow response doesn't wake you up.
Certificates, domains and DNS
Every HTTPS monitor also watches the certificate and sends reminders 14, 7, 3 and 1 days before expiry; most of the time that means your host's auto-renewal failed and there is still time to fix it. Domain registration gets reminders at 30, 14, 7 and 1 days, and DNS change alerts tell you when the site's records change, which is how you find out a migration or a hijack happened.
Questions
Does a 503 from WordPress maintenance mode count as down?
Yes. 503 is a server error, so if two checks in a row see it, you're alerted. Updates normally finish in seconds, inside the gap between checks; if the alert fires, the update hung and the .maintenance file needs deleting. Schedule a maintenance window for planned updates.
How do I catch a white screen or a critical error that returns 200?
Add a text rule to the monitor: the page must contain a phrase that only appears when the site works (your site name in the footer), or must not contain "critical error". A page that fails the rule counts as down.
Will heyUptime tell me why the site is down?
It tells you what it saw: the status code (500, 502, 503), a timeout, a certificate problem, a DNS change or a failed text rule. For WordPress that usually points at the cause: a 503 means an update is stuck; "critical error" means a plugin or theme fatal.
How often should a WordPress site be checked?
Every 60 seconds on Starter, every 30 seconds on Pro and Business. Either way the outage is confirmed by a second check before you're told, so you're alerted within about one to two minutes of the site breaking.
See it on your own site.
heyUptime checks every 30 seconds, confirms before alerting, and tells you why it's down in plain words. Free for 14 days, no card.
Related
- Uptime monitoring for online shops
- Uptime monitoring for web agencies
- SSL certificate checker
- What a 503 means
- Website speed test
- Uptime monitoring for online shops
- Uptime monitoring for web agencies
- Uptime monitoring for SaaS and startups
- Uptime monitoring for Shopify stores
- Uptime monitoring for freelancers and small studios
- Uptime monitoring for side projects and indie developers
Updated October 8, 2026.