Website Uptime Monitoring for Small Business: A Setup Guide
By Nemanja Vukmirović, Lizzard Solutions. Last updated 14 November 2026.
Your website went down at 2 a.m. on Saturday. The hosting company fixed it on Monday at noon. In between, the contact form returned errors, ads kept sending paid clicks to a blank page, and you found out only when a client called to ask if you were still in business.
Website uptime monitoring is the cheap fix for that story. A small, automated check tells you about a problem in minutes, not days. This guide explains what to monitor, how to set it up in under an hour, and how to react when an alert fires.
TL;DR
- Uptime monitoring checks your site from outside every few minutes and alerts you when it fails.
- Monitor more than the home page: the contact form or checkout, the SSL certificate, the domain expiry and a keyword on the page.
- Send alerts to a phone, not only to an inbox, and decide in advance who reacts and what they check first.
What is website uptime monitoring?
Website uptime monitoring is an automated service that requests your website from outside servers at regular intervals, for example every one to five minutes, and alerts you by email, SMS or a chat app when the page fails to load, returns an error code, loads too slowly or no longer contains expected content. It measures what visitors actually experience.
Your hosting dashboard may say everything is fine while visitors see an error. An outside check does not care why the site is broken. It only reports that it is, which is exactly what you need to know first.
What 99.9% uptime really means
Hosting plans love to promise 99.9% uptime. It sounds like perfection, but the remaining 0.1% is real time. Here is the plain arithmetic for a 30-day month:
| Uptime | Allowed downtime per 30-day month | Allowed downtime per year |
|---|---|---|
| 99% | about 7 hours 12 minutes | about 3.65 days |
| 99.5% | about 3 hours 36 minutes | about 1.8 days |
| 99.9% | about 43 minutes | about 8.8 hours |
| 99.99% | about 4 minutes | about 53 minutes |
Two things follow. First, a hosting promise is not a measurement, so you need your own numbers to hold a provider to its terms. Second, when the downtime happens matters as much as how long it lasts. Forty minutes during a Monday campaign launch costs more than forty minutes at 4 a.m.
Key takeaway
Uptime percentage tells you how often the site was reachable. It does not tell you whether the form worked, the certificate was valid or the page was fast. Monitor those separately.
What to monitor: 6 checks for a small business site
The Google SRE book chapter on monitoring distributed systems groups what matters into four golden signals: latency, traffic, errors and saturation. For a small business website, that translates into a short, practical list:
| Check | What it catches | Suggested interval |
|---|---|---|
| HTTP status of the home page | Server down, 5xx errors, wrong redirects | 1-5 minutes |
| Keyword on the page | A blank page or hosting error page that still returns 200 | 5 minutes |
| Key business page (contact form, checkout, booking) | The page that makes money is broken while the home page works | 5 minutes |
| Response time | The site is technically up but painfully slow | 5 minutes, alert on a sustained slowdown |
| SSL certificate expiry | Browser security warnings that scare visitors away | Daily, alert 14-30 days before expiry |
| Domain expiry | The site and company email both disappear | Weekly, alert 30-60 days before expiry |
Certificate checks matter more than they used to. Let's Encrypt, which issues many free certificates, stopped sending expiration notification emails in June 2025 and now suggests a third-party service for those reminders. If your auto-renewal silently breaks, nobody will warn you unless you monitor it yourself.
Action for today: write down the one page on your site that brings in leads or orders. That page gets a monitor, not just the home page.
How to set up uptime monitoring in 5 steps
- Choose a tool with external checks from several locations. Many uptime services have a free tier that covers a handful of monitors, which is enough for most small sites. Prefer one that confirms a failure from a second location before alerting, to cut false alarms.
- Add the six checks above. Use the exact production URLs, including https and the www or non-www version your site actually uses.
- Set a keyword check. Pick a word that only appears on the working page, such as your company name in the footer or the submit button text.
- Route alerts to two people and a phone. Email alone gets missed on weekends. Add a push notification, SMS or a team chat channel, plus a backup person.
- Turn on a simple status history. Keep the monthly uptime and incident log. It is your evidence when you talk to the hosting provider.
Common mistake
Alerting on every single failed check. One timeout from one location is often noise. Alert after two or three consecutive failures, or after confirmation from a second location, so people keep trusting the alerts.
The SRE book makes the same point: every alert that wakes someone up should require a real action. If your team learns to ignore alerts, the monitoring is worse than useless.
What to do when the alert fires
A short, written routine stops panic and wasted time. Keep it next to your incident response plan:
- Confirm. Open the site on mobile data, not office Wi-Fi, and check the monitor's error message.
- Check the obvious. Is the domain or hosting bill unpaid? Did someone just deploy a change or update a plugin?
- Contact the host. Send the monitor's timestamp and error code. Ask whether the issue is on their side.
- Communicate. If the outage lasts, post a short note on social media and pause paid ads that point to the site.
- Write it down. Start time, cause, fix and end time. Three such notes a year will tell you if it is time to change hosting.
Planned maintenance: use a 503, not a broken page
If you take the site down on purpose for an update, return a maintenance page with HTTP status 503 Service Unavailable. MDN describes 503 as the code for a server that is temporarily unable to handle the request. Google's guidance on pausing an online business recommends a 503 for an urgent shutdown of one to two days, not longer. Pause your monitors during the window so the team is not flooded with alerts.
Example: a dental clinic booking page
A clinic in Niš has a WordPress site with an online booking form. The home page monitor stays green for weeks. Then a plugin update breaks the booking page, which now shows a PHP error but still returns status 200. The home page check would never notice.
Because the clinic also has a keyword check on the booking page looking for the text of its submit button, the alert reaches the office manager's phone within minutes. The developer rolls back the plugin before the morning rush. Without the check, the clinic would likely have learned about it from patients who could not book.
Uptime monitoring is part of maintenance, not a one-time setup
Monitoring tells you when something breaks. Regular care makes it break less often. Add monitor review to your website maintenance checklist, keep tested backups for fast recovery, and treat slow response times as a warning sign. Our guide to website speed optimization explains how to fix the causes, and Core Web Vitals shows what Google measures.
FAQ
How often should I check my website uptime?
For most small business sites, a check every one to five minutes is enough. Faster checks rarely change how quickly someone can react. Certificate and domain expiry need only daily or weekly checks, with alerts several weeks before the date.
Is free uptime monitoring good enough?
Often, yes. Free tiers usually cover a few monitors with checks every few minutes and email or app alerts. Paid plans add more frequent checks, SMS alerts, more locations and status pages. Start free and upgrade when you need more monitors or faster alerts.
Why does my host say the site was up when it was not?
The host may measure its own server, not the page your visitors load. A site can be unreachable because of DNS, an expired certificate, a broken plugin or a firewall rule while the server itself runs. That is why an external check with a keyword is more reliable.
Does downtime hurt SEO?
Short outages are normal and rarely matter. Longer or repeated outages can lead search engines to crawl less and eventually drop pages. For planned work, Google recommends a 503 status for no more than a day or two.
Want to know how fast and reliable your site really is?
Run our free website speed check, then let us set up monitoring and alerts that fit your team, so you hear about problems before your clients do.
Run the free speed check