How to Monitor WordPress Uptime for a New Website

The first time a client asked me “how long was my site down?” and I had no real answer beyond “sorry, I only noticed when you called,” I set up uptime monitoring on every site I manage from that point on. A WordPress site can go offline for all sorts of ordinary reasons — a plugin conflict, a maxed-out server resource, an expired certificate — and unless something is actively watching, you usually find out from a customer rather than from your own dashboard.

Uptime monitoring closes that gap. It’s a small, free-to-cheap habit that turns “how long has this been broken?” into “I already know, and I’m already fixing it.” Here’s how to set it up properly for a new WordPress website, what to actually do when an alert fires, and how to read the data it collects over time.

Quick Answer

Sign up for an external uptime monitor, point it at your homepage URL, set the check interval to five minutes or less, and connect an alert method you’ll actually see quickly — email is fine, but a phone push notification or SMS is faster. Add a second monitored URL, such as your contact page, so a monitor failure on one page doesn’t get mistaken for the whole site being fine. If you’re monitoring a business site, check the free tier’s terms of service before relying on it long-term — see below.

Why This Matters

Downtime is expensive in ways that aren’t always obvious on a small site. Every minute your site is unreachable, search engine crawlers can log a failed visit, potential customers land on a browser error instead of your business, and any advertising spend driving traffic to that URL is being wasted in real time.

Monitoring doesn’t prevent downtime by itself — it shortens how long it lasts. In my experience, the sites that recover fastest from an outage aren’t the ones with the most robust hosting, they’re the ones where the owner found out in the first five minutes instead of the next morning. There’s also a pattern-spotting benefit that only shows up once you’ve collected a few weeks of data: a single short outage is usually a one-off, but if your monitor’s history shows the same site going down every Tuesday night, or every time a particular backup task runs, that’s a scheduling conflict you can actually fix — invisible without a log of past outages to compare against.

Two Real Options, With Actual Current Pricing

Rather than a generic “pick a monitoring service,” here’s what the two most commonly recommended tools actually offer as of this writing:

• UptimeRobot — the free plan covers 50 monitors at 5-minute intervals, one basic status page, and three months of data retention. There’s a real catch worth knowing before you rely on it: since October 2024, UptimeRobot’s free plan is restricted to personal, non-commercial use under its own terms of service. A business site technically needs a paid plan (Solo, from roughly $9-10/month) to stay within those terms, even though nothing in the signup flow stops a business from using the free tier in practice.
• Better Stack (formerly Better Uptime) — the free plan covers 10 monitors at 3-minute intervals, one status page, and a phone-call alert option built in even on the free tier. No personal-use restriction in its terms, which makes it the more straightforward free option for a small business site specifically, though the interval is slightly less frequent than UptimeRobot’s free tier and the monitor count is lower.

Neither tool needs a credit card to start, and both easily cover a single new WordPress site’s needs on their free tier. The practical decision point is simply which free tier’s terms and limits actually match your situation — a personal blog fits comfortably inside UptimeRobot’s restriction, while a client site or small business is better served starting on Better Stack’s free tier or UptimeRobot’s cheapest paid plan.

Step-by-Step Instructions

Step 1: Choose an External Monitoring Tool

Your monitor needs to run somewhere other than your own server, since a server that’s down can’t reliably report on itself. Pick based on the terms-of-service distinction above, not just feature comparison — paid tiers on either tool add faster check intervals and more monitored URLs, but aren’t necessary until your site has meaningful traffic to protect.

Step 2: Add Your Key URLs

Monitor your homepage first, since that’s the URL most visitors and search engines hit directly. Then add at least one second page that depends on a different part of your site working — a contact form page is a good choice, since it also confirms your forms haven’t silently broken even when the homepage loads fine. Two monitored URLs catch far more real failure modes than one.

Step 3: Set the Check Interval

Five minutes is a reasonable default for most small sites — frequent enough to catch outages quickly without generating excessive check traffic. If your monitoring service’s free tier only offers longer intervals, that’s still far better than no monitoring at all; a 15 or 30-minute check interval still beats finding out from a customer days later.

Step 4: Connect a Fast Alert Method

Email alerts are the default option almost everywhere, but email can sit unread for hours, especially outside working hours. If your monitoring tool supports it, add a phone push notification, SMS, or a messaging app integration as well, so a genuine outage reaches you within minutes rather than whenever you next check your inbox. If your site can’t reliably send email in the first place, don’t rely on email alone for this.

Step 5: Set a Response Plan Before You Need One

Decide now, not during an actual outage, what your first three checks will be: your host’s status page for known issues, your last-changed plugin or theme (since a plugin update is one of the most common causes of an unexpected outage), and your hosting account for a suspension or resource-limit notice. Having this list ready turns a stressful five-minute scramble into a calm five-minute checklist.

Practical Tips

• Review your monitor’s uptime percentage monthly rather than only reacting to individual alerts — a site sitting at 98% uptime has a real recurring problem worth investigating even if no single outage felt dramatic.
• Use the WordPress Site Health tool alongside external monitoring — Site Health catches internal warnings your uptime monitor can’t see, since it checks from inside WordPress rather than from outside.
• If your host offers a status page with subscription alerts, sign up for it separately — it often confirms whether an outage is on their end before your own monitor even finishes its next check.
• If you’re on UptimeRobot’s free tier for a client or business site, budget for the Solo plan once the site is generating real revenue — the terms-of-service gap is a low-probability enforcement risk today, but it’s an easy, cheap thing to fix properly rather than leave as a loose end.

Common Mistakes

• Monitoring only the homepage and assuming the rest of the site is fine — a broken checkout, form, or login page can sit undetected for weeks if nothing is watching it directly.
• Setting up alerts once and never testing them — trigger a test alert when you first configure monitoring so you know it actually reaches you, rather than discovering a broken notification setting during a real outage.
• Using a free tier without checking whether it’s actually licensed for the kind of site you’re running — the UptimeRobot restriction above is exactly this kind of easy-to-miss detail.
• Treating uptime monitoring as a one-off setup task instead of part of a recurring routine — it belongs alongside the other ongoing checks in a proper website maintenance plan, not as something configured once and forgotten.

When to Use This vs Alternatives

External uptime monitoring is worth setting up on every live WordPress site, regardless of size — even the paid tiers cost only a few dollars a month, and both tools above take minutes to configure. Some managed hosting plans include built-in uptime monitoring and alerting as part of the package; if yours does, it’s a reasonable primary layer, but I’d still add an independent external monitor too, since a host-provided monitor can’t reliably tell you when the problem is the host itself. For background on how hosting environment choices affect reliability more broadly, WordPress.org’s own guide to hosting WordPress is a good starting reference.

Conclusion

Set up an external monitor today if you haven’t already — pick UptimeRobot if the site is personal, or Better Stack (or a paid UptimeRobot plan) if it’s a business site, and it takes less time than reading this article. It’s the single easiest way to stop finding out about downtime from your customers instead of your own dashboard. For everything else a new site needs covered early on, see the step-by-step guide to building a WordPress website.