A client calls, upset. Customers are complaining — orders not going through, people leaving. You check your monitoring tool immediately. Green light. No alerts. Everything fine.
So you open the website. The homepage loads perfectly. You click checkout: blank white screen. Nothing.
The uptime monitor never sent a single alert — because technically the website was responding. The server was running. HTTP 200 was coming back. But the site was completely broken for anyone trying to actually use it.
This is one of the most common gaps in website monitoring, and it costs businesses real money every week.
What Basic Uptime Monitoring Actually Checks
When a basic uptime monitor checks your website, it does one simple thing: sends a request to your URL and waits for a response. If the server responds with HTTP 200 — it marks your site as UP and moves on.
That's it. It does not read the page. It does not check what is on the page. It does not verify that your checkout works, your contact form submits, or your images load.
A server can respond perfectly fine with HTTP 200 even when your website is showing nothing but errors to real visitors. Understanding which status codes mean what is covered in the HTTP status codes guide — but even a perfectly healthy 200 response can hide a broken site.
8 Ways Your Site Can Be "Up" But Completely Broken
1. Database connection error
Your server is running fine. Your database has crashed or disconnected. The result: your website loads but shows "Error establishing a database connection" or a blank page. Your uptime monitor sees HTTP 200. Your visitors see an error. This is one of the most common failures for WordPress sites — a plugin update, a server resource limit, or a MySQL crash can cause it instantly.
2. Maintenance mode left on
A developer enables maintenance mode at 11pm, finishes the work, and goes to sleep forgetting to turn it off. Your site is technically running and the uptime checker shows green. But every visitor sees "Site Under Maintenance." The monitoring tool never alerts anyone — and the site stays in maintenance mode all night.
3. SSL certificate expired
Your server is up. Your website is loading. But your SSL certificate expired. Now every visitor sees a full-page red warning: "Your connection is not private." Most people close the tab immediately. Basic uptime monitoring doesn't check SSL — it just checks if the server is responding, and the server responds fine with an expired cert. SSL monitoring is a separate check entirely. See SSL Certificate Expiry: What Happens When It Expires for what this looks like to visitors and how to prevent it.
4. A specific page is broken while the homepage is fine
Most uptime checkers monitor only your homepage URL. But what if your homepage loads fine and your checkout page throws a 500 error? The monitor checks the homepage, sees HTTP 200, reports everything is fine — meanwhile customers hit a broken checkout and go to your competitor. For e-commerce this is a critical monitoring gap.
5. Site broken after a plugin or code update
You pushed a code update or upgraded a WordPress plugin. Everything looks fine on the surface. But something broke — a JavaScript file isn't loading, two plugins are conflicting, your forms aren't submitting. Your uptime monitor stays green. Real visitors are confused and leaving.
6. Website is extremely slow — up but unusable
Sometimes a website doesn't go down. It just becomes very slow. Loading time goes from 1 second to 18 seconds. Technically the server is still responding, so the uptime monitor says UP. But nobody waits 18 seconds. Without response time monitoring, you'd never know — your site is technically up but not working for anyone who visits.
7. Domain blacklisted — emails going to spam or site blocked by browsers
Your website loads fine, but your domain has been added to a spam or malware blacklist. Your emails go to spam for everyone. Some browsers and security tools warn visitors that your site is dangerous. Your uptime checker sees a healthy HTTP 200 response and reports everything is green. But a large portion of your audience can't actually reach you.
8. robots.txt accidentally blocking search engines
Someone accidentally added one line to your robots.txt file: Disallow: /. This tells Google: do not crawl this website. Your site monitor stays green. But Google stops indexing your pages. Over weeks your search rankings drop quietly. Traffic falls. You have no idea why — and nobody gets alerted.
What a Complete Website Health Check Covers
Beyond basic uptime, here's what proper site monitoring should check:
- Uptime — is the server responding at all
- Response time — is it loading fast enough for real visitors
- SSL certificate — is it valid and when does it expire
- Domain expiry — when does the domain itself lapse
- robots.txt — present and not blocking search engines
- Blacklist status — is the domain on any spam or malware lists
- Keyword/content check — does a specific string still appear on the page (catches maintenance mode, broken pages, defacements)
When all of these run together from one dashboard, you get a complete picture of whether a website is actually healthy — not just whether the server is alive and returning HTTP 200. This is what separates basic uptime monitoring from full website health monitoring. For a deeper explanation of what uptime monitoring is and what to look for in a tool, see What Is Uptime Monitoring? A Guide for Businesses.
A Quick Health Check You Can Do Right Now
Open your website and manually verify these:
- Does the homepage load properly with all images and styling?
- Does the padlock icon appear in the browser? (SSL check)
- Does your contact form actually submit and send an email?
- If you have a shop — does "add to cart" actually work end to end?
- Check
yourdomain.com/robots.txt— does it sayDisallow: /anywhere it shouldn't? - How fast does the page load? More than 3 seconds is a serious problem.
- Send yourself an email from outside your domain — does it land in inbox or spam?
Why This Matters for Agencies
If you're managing websites for clients, this gap becomes a much bigger problem. You're responsible for their online presence. The worst call you can get is a client saying "my website has been broken for three days and nobody told me" — because that means your monitoring was showing green the whole time.
One incident like this can damage a client relationship permanently. Complete website health monitoring — covering uptime, SSL, domain expiry, response time, blacklist status — is the baseline, not a nice-to-have. Domain expiry is the other silent killer that works the same way: for how that plays out, see What Happens When Your Domain Expires.