How to Set Up Free Uptime Monitoring for a Small Website
The worst way to learn your website is down is from a customer. The second worst is noticing it yourself on a Monday morning after it has been offline since Saturday night.

The worst way to learn your website is down is from a customer. The second worst is noticing it yourself on a Monday morning after it has been offline since Saturday night. Uptime monitoring fixes both, and for a small site it costs nothing and takes about 15 minutes to set up.
A monitor is simply a service that visits your site on a schedule, say every five minutes, and sends you a message when it gets no answer or a bad answer. That is the whole idea. The details that matter are what it checks, how often, and who it alerts, and getting those right is the difference between a useful warning and a stream of noise you learn to ignore.
What an Uptime Monitor Actually Checks
Most free monitoring services offer the same handful of check types. Knowing what each one proves helps you pick the right mix instead of switching everything on.
| Check type | What it does | What it catches |
|---|---|---|
| HTTP or HTTPS | Requests a page and reads the status code | Server down, 500 errors, expired hosting |
| Keyword | Loads a page and looks for a word you choose | Blank pages, error screens that still return 200 |
| Ping | Sends a network ping to the server | Server unreachable, network outage |
| SSL certificate | Reads the certificate expiry date | Certificates about to expire |
| Domain expiry | Checks the registration end date | A domain you forgot to renew |
For a typical brochure site or blog, an HTTPS check on the homepage plus an SSL expiry check covers most real outages. A keyword check is the upgrade worth making next, because plenty of broken sites still answer with a cheerful 200 status while showing a database error.
Choosing a Free Service
You do not need a paid plan to start. Free tiers from the common monitoring providers usually allow somewhere between 10 and 50 monitors with checks every five minutes, which is more than enough for one to three small sites. When comparing them, look at four things:
- Check interval. Five minutes is fine. One minute is nice but rarely necessary for a personal or small business site.
- Alert channels. Email is the minimum. A phone app with push notifications or a text message is better, since email is easy to miss.
- Multiple locations. Services that confirm an outage from two or more regions before alerting send far fewer false alarms.
- Status page. Some include a free public page showing whether your site is up, useful if you have regular visitors or clients.
Pick one service and stick with it. Running three overlapping monitors just triples the notifications without telling you anything new.
Setting Up Your First Monitor Step by Step
The interface differs between providers, but the steps are almost identical everywhere.
- Create an account and confirm your email address.
- Add a new monitor, choose HTTPS, and paste your full homepage address including https.
- Set the interval to five minutes and give it a clear name such as "Main site homepage".
- Add yourself as an alert contact and, if possible, install the provider's phone app.
- Create a second monitor of the SSL type for the same domain, alerting 14 days before expiry.
- Save, then wait for the first check to show green.
Then test it. The easiest safe test is to add a temporary monitor for a page that does not exist, such as /monitor-test-404, and confirm the alert arrives. Delete it once you have seen the message land on your phone.
Which Pages to Watch Besides the Homepage
The homepage is the obvious choice, but it is often cached and can stay up while other parts of the site are broken. Add a keyword monitor on one page that depends on your database or CMS, such as your latest blog post or a product page, and pick a word that only appears when the page renders correctly, like the site name in the footer.
If your site has a contact form, booking page or shop checkout, monitor that page too. A homepage that loads while the checkout returns errors is still a broken business. Three to five monitors is a sensible ceiling for a small site; beyond that you are mostly watching the same server several times.
Tuning Alerts So You Do Not Ignore Them
An alert that fires for a 30 second blip at 3am will teach you to mute the app within a week. Most services let you set how many failed checks in a row trigger a notification. Two consecutive failures, which with five minute checks means about ten minutes of downtime, is a good balance for small sites.
Also turn on recovery alerts, the message that says the site is back. Without them you are left refreshing the page to find out whether the problem cleared on its own. If you share responsibility with a developer or a business partner, add them as a contact so the right person hears about it, and agree in advance who reacts first.
What to Do When an Alert Arrives
When the message comes in, work through a short checklist before contacting anyone.
- Open the site on your phone using mobile data, not your home wifi, to rule out a local network problem.
- Check your host's status page for a reported incident.
- Look at what changed recently: a plugin update, a theme change or a DNS edit. Our guide on how often to update website plugins explains why updates are the most common cause of sudden breakage.
- If the site is badly broken and the cause is unclear, restore from your last good backup. That only works if you have one, which is why backing up your website and testing the restore belongs alongside monitoring.
Keep a simple log of each incident with the date, length and cause. After a few months it shows whether your host is reliable or whether a pattern points to one plugin or one time of day.
Reading Your Uptime Percentage Honestly
Monitoring dashboards show uptime as a percentage, and the numbers are less impressive than they look. 99 percent uptime sounds excellent but allows more than seven hours of downtime in a month. 99.9 percent allows about 43 minutes. For a small business site, anything consistently below 99.5 percent over three months is a reasonable trigger to talk to your host or start shopping around.
FAQ
Will an uptime monitor slow down my website?
No. A check every five minutes adds up to under 300 requests a day, which is a tiny fraction of normal bot traffic. Even a cheap shared hosting plan handles that without any measurable effect on speed.
Does my hosting company already monitor my site?
Your host usually monitors its servers, not your individual site. A server can be healthy while your site shows a database error or an expired certificate, so your own monitor still adds value.
How often should I review my monitoring setup?
Once a quarter is enough. Check that the alert contacts are still correct, remove monitors for pages you deleted, and add any new important pages, such as a new booking form.
A Small Habit With a Big Payoff
Fifteen minutes of setup gives you a quiet assistant that checks your site around 8,600 times a month and only speaks up when something is wrong. Start with a homepage check and an SSL check, add one keyword monitor, test the alert once, and browse the rest of the maintenance guides to keep the site healthy between alerts.
More in Maintenance and Security
Maintenance and Security
How to Stop Spam Comments Without Killing Real Ones
The first spam comment on a site I built for a friend's bike repair shop arrived nine days after launch, before the site had a...
Maintenance and Security
How to Fix an Expired SSL Certificate on Your Website
A site I help with went dark on a Sunday morning in March. Not down, exactly.
Maintenance and Security
How to Update PHP Version Safely on a Small Website
Your hosting dashboard shows a yellow warning that your site runs on an outdated PHP version, and you are worried that trying...