Most website owners find out their site is down the worst possible way: a customer emails, a sale fails, or a client calls. Uptime monitoring flips that around. A monitor visits your site on a schedule, and the moment it stops answering correctly you get an alert, usually minutes before anyone else notices. This guide shows how to set it up for free, what to check besides the home page, and how to avoid the false alarms that make people switch alerts off.
What uptime monitoring actually checks
An uptime monitor is a robot that requests a URL every few minutes from a server outside your hosting. Each check records three things:
- Did it respond? A timeout or a refused connection means visitors cannot reach you.
- Was the response correct? A page that returns an error code such as 500 or 503 is technically online but broken. A good monitor treats it as down.
- How fast was it? Response time trends warn you about a slow database, a full disk or an overloaded plan before they become outages.
Because the check runs from outside your network, it sees your site the way visitors do, including DNS, SSL and CDN problems that internal server dashboards miss.
How to set up free uptime monitoring in five minutes
1. Create a free account
Sign up for My Site Alerts with your email address. There is no credit card and no trial clock: the free plan includes 10 website monitors with checks every 5 minutes.
2. Add your most important URL first
Start with the page that makes you money or brings you leads: the home page, a checkout, a booking form or a login page. Paste the full address, including https://, and keep the default 5-minute interval.
3. Choose where alerts go
Email is the minimum. If you live in a chat app, connect Slack, Discord, Telegram or Microsoft Teams as well, so an outage reaches you on the device you actually look at. Send alerts to at least two channels: if your email runs on the same server as your website, an outage can take both down at once.
4. Add a keyword check for pages that can fail silently
Some failures still return a normal page: a blank template, a database error message or a maintenance notice. Tell the monitor to look for a word that should always be there, such as your brand name or the text of your buy button. If the word disappears, you get an alert even though the server answered.
5. Publish a status page
A public status page gives customers one place to check when something feels wrong, and it saves you from answering the same question twenty times during an incident. The free plan includes two.
What else to monitor (it is not just the home page)
- SSL certificates. An expired certificate shows visitors a full-screen security warning. Get a reminder weeks before expiry; you can check any site right now with our SSL checker.
- Domain expiry. A lapsed domain takes your site and your email offline at once, and a competitor can register it. Domain monitoring warns you well before the renewal date.
- Cron jobs and backups. A heartbeat monitor expects a ping from your scheduled job. If the backup or the invoice script stops running, the missing ping triggers an alert.
- DNS records. An unexpected change to your A, MX or TXT records can break your site or your email deliverability. Look up your current records with the DNS lookup tool.
- Key flows on other domains. If your shop runs checkout on a subdomain or a payment provider, monitor that URL too.
How often should you check?
For most websites a 5-minute interval is the sweet spot. In the worst case you learn about an outage within about five minutes, which is far faster than waiting for a customer complaint, and it keeps the number of requests to your server tiny: 288 checks a day. One-minute checks matter mainly when every minute of downtime costs real money, such as a busy store during a sale. For SSL, domains and DNS, hourly or daily checks are plenty, because those problems build up over days, not seconds.
How to avoid false alarms
Nothing kills a monitoring setup faster than alerts that cry wolf. A few habits keep alerts trustworthy:
- Confirm before alerting. My Site Alerts re-checks a failure before it notifies you, so a single dropped packet does not wake you up.
- Use a realistic timeout. If your site normally answers in two seconds, a ten-second timeout separates slow from down.
- Monitor a stable URL. Avoid pages that redirect differently depending on location or cookies, and avoid URLs protected by a bot challenge that blocks automated checks.
- Silence planned work. Pause the monitor during maintenance so the history shows real incidents only.
What to do when you get a down alert
- Check it from outside. Open the site on your phone using mobile data, or run a quick ping test to see whether the server responds at all.
- Read the error. The alert tells you whether it was a timeout, a DNS failure, an SSL error or an error status code, which points you to the right fix: hosting, domain, certificate or application.
- Tell your users. Post a short update on your status page. People forgive outages much more easily when they can see you are on it.
- Look at the timeline afterwards. Response time history often shows the slowdown that came before the outage, which is the clue to preventing the next one.
Free vs paid uptime monitoring
Paid tools add things like one-minute or 30-second checks, dozens of check locations, SMS calls and large teams. For a personal site, a blog, a small business or a handful of client sites, the essentials are the same: reliable checks every few minutes, alerts on the channels you use, SSL and domain warnings, heartbeats for scheduled jobs and a status page. That is exactly what the free plan covers, without a trial that runs out.
Frequently asked questions
Is free uptime monitoring reliable?
Yes, as long as checks run from outside your hosting and failures are confirmed before you are alerted. The interval is the main difference from paid plans, and 5 minutes is enough for most websites.
Will monitoring slow down my website?
No. A check every 5 minutes is one lightweight request, 288 a day, which is less traffic than a single visitor browsing a few pages.
Can I monitor a website I do not own?
Only if you have permission. Monitoring a client site or a supplier you depend on is fine with their consent; please do not point monitors at systems you are not authorised to check.
How do I know if a website is down for everyone or just me?
Test it from another network, such as mobile data, or use an external tool like our ping test. An uptime monitor answers this automatically, because it checks from servers outside your connection.