
Website uptime monitoring is a service that checks your site from outside every minute or so and alerts you the moment it stops responding. You set up a check on your key pages, pick who gets the alert (email, SMS or a team chat channel), and let it run. That’s the core of it. The rest of this guide covers what to check, how often, how to avoid false alarms, and why it matters for your Google rankings.
TL;DR
-
Uptime monitoring pings your site from outside your own network and alerts you when it fails, so you find out before customers do.
-
Check your homepage, your key money pages (contact, checkout, booking) and your SSL certificate, not just one URL.
-
Use checks every 1 to 5 minutes, confirmed from more than one location, with alerts that reach a real person after hours.
-
Prolonged downtime can slow Google’s crawling, so use Search Console alongside your monitor.
-
Don’t chase 100%. Pick a realistic target, like 99.9%, and know what it means in hours.
Table of Contents
What uptime monitoring actually does
Your website is a server somewhere answering requests. When that server is overloaded, misconfigured, out of disk space or knocked offline by a bad plugin update, visitors see an error or a blank page. You won’t notice if you aren’t looking at the site at that moment. A monitor looks for you.
A basic monitor sends a request to your URL on a schedule and checks the response. If the page comes back with a normal status code (a 200), the site is “up”. If it times out or returns a server error (like a 500 or 503), the monitor marks it “down” and sends an alert. It also keeps a history, so you can see when problems happen and how long they last.
This is different from checking your site by hand. You’re on your own network, with your own cached copy of the page, and you might be logged in. A monitor sees what a stranger sees.

What to monitor (it’s more than the homepage)
Most small business owners set up one check on the homepage and call it done. That catches a total outage, but plenty of problems are narrower. Here’s what we’d cover:
-
Homepage. The obvious one.
-
Pages that make you money. Contact form, booking page, checkout, quote request. A site can load fine while the form behind it is broken.
-
Keyword checks. Many monitors can look for a specific word on the page, such as your business name or a phone number. If a hacked site or an error page loads with a “200 OK” status, a keyword check still catches it.
-
SSL certificate. An expired certificate throws a scary browser warning, and most visitors will leave. Set an expiry reminder at least two weeks ahead.
-
Domain renewal. Lapsed domains are more common than people think, and they take email down with the website.
-
DNS. If your DNS records break, your site can be perfectly healthy on the server and still unreachable.
-
Page speed. A site that takes 15 seconds to load is technically “up” but effectively down for most people.
If you run an online store or a booking system, give those pages the shortest check interval. A quiet outage on your contact page at 9 pm on a Friday costs you leads you’ll never know you lost.
How often to check, and from where
Check frequency
Most tools offer intervals from about 30 seconds up to 5 minutes or more, with the quicker intervals usually on paid plans. For a local service business, a check every 5 minutes is a sensible starting point. For an online shop or anything taking bookings and payments, go to 1 minute if your plan allows it.
The trade-off is simple. A 5-minute interval means an outage could run for up to five minutes before you’re told. For a brochure site, that’s fine. For a store during a sale, it isn’t.
Check location
This is where Australian sites differ from the global advice. Plenty of monitoring tools run their checks from the US or Europe. From there, your Sydney-hosted site can look slow even when it’s fine for your customers, and a routing problem on a local ISP might not show up at all.
If your customers are in Wollongong, Sydney or anywhere else in Australia, choose a tool with Australian check locations, or at least one that lets you pick them. Your results will be closer to what your customers actually experience.
Confirmation from a second location
A single failed check isn’t always an outage. Networks hiccup. Good monitors re-test from a second location before raising the alarm. If both fail, it’s real. If only one fails, it was probably a network blip between that checkpoint and your server. Turning this on cuts false alarms, and fewer false alarms means you’ll still take the 2 am SMS seriously.

Alerts: The part people get wrong
A monitor that emails an inbox nobody reads is decoration. Think through the alert path:
-
Who gets told? At least two people, so a sick day or a flat phone doesn’t leave you blind.
-
How? Email is fine for warnings like an SSL expiry. For a full outage, use SMS or a push notification to a phone, or a team chat channel someone watches.
-
What happens next? Write down a short checklist: check the hosting dashboard, check for recent updates, restart the server or restore a backup, call your host or developer.
-
Who do you call? Keep your hosting support number and your developer’s number somewhere you can find them when the site is down.
It’s also worth giving staff and customers an easy way to tell you something’s broken. Automated checks catch the obvious failures, but a human saying “the booking form isn’t sending” will often find the problem first.
What uptime percentages really mean
The numbers sound similar, but the gaps are big. Here’s the downtime each target allows (simple arithmetic on a 365-day year):
| Uptime target | Downtime per year | Downtime per month (30 days) |
|---|---|---|
| 99% | about 3 days 15 hours | about 7 hours 12 minutes |
| 99.9% | about 8 hours 46 minutes | about 43 minutes |
| 99.99% | about 52 minutes | about 4 minutes 19 seconds |
| 100% | none | none |
No one can honestly promise 100%. Servers need updates, networks fail, and data centres have bad days. When a hosting provider or agency quotes you an uptime guarantee, ask three things: what does it measure, what’s excluded (planned maintenance usually is), and what do you get if they miss it?
For most small business sites, 99.9% is a sensible target. It leaves room for the occasional fix without being a fantasy.
Why downtime matters for SEO
Google can’t rank a page it can’t reach. If Googlebot hits repeated server errors, it may slow how often it crawls your site, and long or repeated outages can cause pages to drop out of results until things settle. A short blip once in a while isn’t going to wreck your rankings. A site that’s regularly flaky might.
Two practical tips:
-
Use Search Console as a second set of eyes. The Crawl Stats report shows when Google had trouble reaching your site, including DNS and server connection problems. If you’re new to it, our Google Search Console for Beginners guide walks through setup. Your uptime monitor tells you what happened to visitors, and Search Console tells you what happened to Google.
-
Use a 503 for planned maintenance. If you’re taking the site down on purpose, have the server return a 503 (Service Unavailable) status, ideally with a Retry-After header. That tells search engines the outage is temporary and when to come back, rather than leaving them to assume your pages are gone. Keep it under about 48 hours — Google treats a 503 lasting more than a couple of days as permanent and starts dropping pages from the index. A 404 or a redirect to the homepage sends the wrong signal.
Uptime is also a trust signal for people. A site that’s slow or erratic feels unreliable, and we’ve written about why web design affects trust if you want the broader picture.
Free or paid monitoring?
Free plans from the major monitoring providers typically cover a handful of sites with checks every few minutes. For a small local business, that’s often enough to start. Paid plans make sense when you need:
-
faster check intervals (1 minute or less),
-
SMS or phone call alerts,
-
multiple check locations with Australian options,
-
a public status page,
-
longer history and reports for clients or your own records.
Paid plans for small sites are usually priced per month in the tens of dollars, though prices change often, so check the current rate with whichever provider you’re considering. We’re not going to name a winner here. Compare tools on the criteria above: locations, interval, alert channels and how easy it is to set up. The best monitor is the one you actually configure properly.
Self-hosted, open-source monitors are another route. They’re free to license, but you’ll need somewhere to run them, and that somewhere shouldn’t be the same server as the site you’re watching. If the server dies, so does the monitor. For most small businesses, a hosted service is simpler.
Setting it up in about 20 minutes
-
List your URLs. Homepage, contact page, your most important service page, checkout or booking page.
-
Create a monitor for each using HTTP(S) checks. Add a keyword check on at least one page.
-
Set the interval. 5 minutes for a brochure site, 1 minute for anything transactional.
-
Choose locations. Pick Australian checkpoints if offered, and switch on confirmation from a second location.
-
Add your alert contacts. Two people, two channels.
-
Add SSL and domain expiry alerts.
-
Test it. Point a test monitor at a URL that doesn’t exist, or pause the site briefly on a staging copy, and confirm the alert arrives. Many people skip this step and find out the alerts were misconfigured during a real outage.
-
Review monthly. Look at the response time trend, not just the red and green. A slow creep upward often warns you of a problem before an outage does.
If you track your SEO results monthly, add the uptime report to that routine. Our guide on tracking local SEO results monthly shows a simple way to do it.
Our take: Monitoring is cheap insurance, not a fix
We’ve been building and optimising websites for 12 years, and the pattern is consistent: most outages we see are boring. An expired certificate. A plugin update on a Friday afternoon. A hosting plan that quietly ran out of resources. A domain renewal email that went to a former employee.
Monitoring catches these quickly, but it doesn’t prevent them. Three things do more than any tool:
-
Decent hosting that matches your traffic. A cheap shared plan is fine for a small brochure site and a poor choice for a busy store.
-
A sensible update routine. Update on a quiet weekday morning, not at 5 pm before a long weekend, and keep a recent backup you’ve tested.
-
A fast site to begin with. A lean, well-built site is far less likely to fall over when traffic spikes. That’s why we build sites with performance in mind from the start, and why we look at speed as part of SEO.
We’d also push back on the idea that you need a complex setup. A small business needs a handful of checks, two alert contacts and a written “what do we do when it’s down” note. That covers most of the real-world risk.
Beyond the website: Other things worth a regular look
A few things won’t show up as “downtime”, but each one costs you enquiries: broken links, form submissions actually arriving in your inbox, and your Google Business Profile details staying current. Add them to the same monthly review as your uptime report.
How we can help
We’re a Wollongong digital agency, and a lot of our work is about making sure your site is built well, loads quickly and stays visible in search. If your site is slow or unreliable, a few things we offer may help:
-
Speed Optimisation at $79 per year, through our SEO services page.
-
Website design from A$590 one-off for a Wix site, if it’s time for a rebuild. See the web design page.
-
WordPress hosting and support in Wollongong, covered on our WordPress hosting page.
-
Ongoing SEO from $170 per month with the SEO Essentials plan.
Not sure where to start? Get in touch, and we’ll have a look at your site with you.
FAQs
What is uptime for a website?
Uptime is the share of time your website is reachable and working for visitors, usually shown as a percentage over a month or year. A site with 99.9% uptime is down for roughly 43 minutes in a 30-day month. Downtime includes both full outages and times when the site is too broken or slow to use.
How often should I check my website?
Every 5 minutes is fine for most brochure and local service sites. If you take bookings, payments or leads online, use 1-minute checks where your plan allows. Turn on confirmation from a second location so you’re not woken by network blips.
Can downtime hurt my Google rankings?
Yes, if it’s frequent or lasts a long time. Google may crawl a struggling site less often, and pages it can’t reach for an extended period can slip in results. A short, rare outage usually causes no lasting harm. For planned maintenance, return a 503 status so search engines know it’s temporary.
Do I need monitoring if my host guarantees uptime?
Yes. A host’s guarantee is their own measurement, often with exclusions, and it won’t catch problems in your site’s code, DNS, SSL or forms. An independent monitor tells you what visitors really see, and gives you your own records if you need to raise a claim.
Is free uptime monitoring good enough?
For a small site, often yes. Free plans usually cover basic HTTP checks with email alerts. Move to paid when you need faster checks, SMS alerts, Australian check locations or a public status page.
Sources
This guide draws on Google’s Search Console documentation for Crawl Stats and on standard HTTP status code behaviour. Related reading on our own site: