Here's a question worth sitting with for a second. If your website went down at 9 tonight, when would you find out? For most owners I talk to, the honest answer is "when a customer tells me." Maybe that's a text the next morning. Maybe it's a potential client who never calls back and never mentions why.
Most business owners find out their website is down from a customer, often hours or days late. Uptime monitoring checks your site every few minutes and alerts a person the moment it stops answering. But a site can be "up" and still broken, so real monitoring also watches your forms, your security certificate and the pages that bring in money.
Why you're usually the last to know
You don't visit your own website much. Why would you? You know what it says. Your staff doesn't either. So when it breaks overnight or over a weekend, nobody inside the business sees it.
Customers do see it. Most of them won't tell you. They'll hit an error, shrug and call the next company on the list. The few who do mention it are the polite ones, and by then the site may have been broken for a while.
Search engines notice too. Google's documentation on server errors explains that when your server keeps returning errors, "already indexed URLs are preserved in the index, but eventually dropped." A short outage isn't a disaster. A long one nobody notices can start to cost you in search too.
What uptime monitoring actually does
Uptime monitoring is a service outside your server that visits your site on a schedule, every minute or every few minutes, and checks that it answers. If it doesn't, the service sends an alert by email, text or a phone app.
It's simple, and it's the right place to start. It turns "a customer told me" into "I got a text within minutes." A few details make a big difference:
- It has to run from outside your server. If the monitor lives on the same machine as your site, it goes down with it.
- It should check more than once before alarming. Otherwise a single slow response wakes you up for nothing, and you learn to ignore alerts.
- It should tell you when the site comes back. That way you know how long you were down.
What "up" misses
This is where most basic monitoring falls short. A standard check asks one question: did the homepage answer? Your homepage can answer perfectly while the parts that make you money are broken.
A form that loads but doesn't send
The contact page looks fine. Visitors fill it out and see "thank you." The message never reaches your inbox. An uptime check will call that site healthy all day long. I cover this one in detail in is your contact form working.
An expired security certificate
The SSL certificate is what puts the padlock in the browser and lets your site load over https. When it expires, visitors see a full page warning instead of your site. Certificates from Let's Encrypt, a widely used free provider, are short lived. Its FAQ says "Our default certificates are valid for 90 days." Renewal is usually automatic, and usually works. When it doesn't, you may not hear about it. Let's Encrypt announced that it would stop sending expiration reminder emails, saying "We will be ending this service on June 4, 2025." If you were counting on that email as your warning, it's gone.
A broken checkout or booking page
A payment plugin update, a change at your payment processor or an expired API key (the password one piece of software uses to talk to another) can break checkout while the rest of the site looks normal. For an online store or a booking business, this is the outage that costs the most, and the one a basic check never sees.
A slow site
A page that takes ten seconds to load is technically up. Visitors don't treat it that way. Google's research with SOASTA found that as load time goes from 1 second to 5 seconds, the chance of a visitor bouncing rises 90%. If it's slow on phones, here's why your website is slow on phones.
These are all versions of the same problem I wrote about in silent website failures. The site stays up. The business quietly leaks.
An alert is only useful if a person acts on it
Monitoring that emails an inbox nobody reads is decoration. Before you set anything up, decide three things:
- Who gets the alert? A real person with a name, plus a backup for when they're on vacation.
- How does it reach them? A text or app notification gets noticed. An email to a shared inbox often doesn't.
- What happens next? Who logs into the hosting account, who calls the host and who can restore from a backup if needed.
Write that down somewhere your team can find it. The worst time to figure out who has the hosting login is while the site is down.
A checklist of what to monitor
- The homepage answers, checked every few minutes from outside your server.
- Your most important pages load, like contact, services and booking.
- Every form sends, tested with a real submission that confirms the message lands in the inbox and not spam.
- Your SSL certificate's expiration date, with an alert a couple of weeks ahead.
- Your domain's renewal date, so the address itself doesn't lapse.
- Checkout or booking, with a test transaction after any update.
- Page speed on a phone, checked regularly.
- Alerts that go to a named person by text or app, with a backup person listed.
Doing it yourself: what it takes
You can set up basic uptime monitoring in an afternoon. Free and low cost services exist, and they'll text you when the homepage stops answering. That alone beats hearing it from a customer.
The rest takes more. Form testing means submitting your own forms on a schedule and checking where the message lands. Certificate and domain dates need tracking. Checkout needs a test after every update. And someone has to be reachable when an alert fires, including nights and weekends, with the access and know how to fix it. Budget a little setup time plus a regular slot each week or month, and be honest about who picks up the phone at 11 on a Saturday. For some owners that's fine. For others it's the part they'd rather hand off.
How we handle it
Our care plan includes monitoring for downtime and broken forms, and alerts come to our team, the same people who know your site and run your server. Our hosting covers SSL certificates set up and renewed, and our forms service makes sure messages actually reach you. No one can promise a site never goes down. What monitoring does is make sure the first person to notice isn't your customer. You get the exact monthly price in writing before you sign.
If you'd rather not be the last to know, ask us about a care plan.
