Uptime monitoring for a small business website

Uptime monitoring for a small business website is only half the job. A check that pings your site is cheap, but it does nothing unless a named person gets the alert and knows what to do next. That pairing belongs in a care plan or managed hosting arrangement, written down before anything breaks.

What "nobody notices" looks like

A small business site with a booking page or a quote form can go down outside working hours. Nobody inside the business is looking at it, because why would they? They know what it says.

The first signal arrives later and from the wrong direction. A customer rings to say the booking link is broken. Or the Google Ads account has spent all weekend sending paid clicks to an error page. By then the outage has a cost, and you're finding out about it second hand.

This can happen to a site that was perfectly well built. The problem isn't the code. It's that nobody has been given the job of knowing.

Why a ping on its own isn't enough

Free uptime checkers exist and they work. Set one up and it'll email someone when your homepage stops responding. So far, so good.

But look at where that email lands. If it goes to an info@ address, you've got the same problem I described in the info@ inbox nobody owns. If it goes to the person who set it up three years ago, and they've since left, it goes nowhere. It's the same failure as a website form that still emails one person's Gmail.

And even when the right person sees it, an alert isn't a fix. They need the hosting and DNS logins, plus the authority to make changes outside office hours. Without that, the alert just means someone worries sooner.

What belongs in a care plan or managed hosting arrangement

When we look after a site, the useful question isn't "is there monitoring?" but "what happens after the alert fires?" These are the pieces worth asking any provider about:

• Uptime check: something outside your hosting that tests the site and raises an alarm when it stops responding.
• Named response path: an engineer who gets the alert, with the access and authority to act on it, and a written response time.
• Out-of-hours cover: agreed in writing if you need it. If your bookings happen at weekends, business-hours support won't match how your customers behave.
• Care plan or managed hosting: the arrangement that holds the above together, alongside hosting, SSL certificate maintenance, backups and security patches.

At Eight Mile, the managed website service includes domain registration, cloud hosting, SSL certificate maintenance, backups, security patches and framework updates, with direct contact with the engineers who built the site. Under a support retainer, monitoring can cover uptime and errors, with an engineer alerted when a threshold is crossed, and the coverage and response time are defined in writing. Out-of-hours cover is part of that agreement rather than an assumption. Ordinary enquiries are handled during London business hours, Monday to Friday.

If you'd rather run things yourself, that's a fair choice. Without a retainer, we set up monitoring for you and leave a runbook, so whoever gets the alert has a written next step.

When a rebuild doesn't fix monitoring

A common assumption is that a new website solves reliability. It can help: newer hosting and fewer plugins mean fewer things to break. But a shiny rebuild with nobody watching it is still a site that can be down all weekend.

That's the point I made in website care plan vs rebuild. The rebuild is a one-off. Monitoring and response are ongoing, and they need an owner after launch day. When you're budgeting, put the running side in the same conversation as the build. Our piece on how much a small business website costs in the UK covers why the monthly side matters as much as the upfront figure.

My view is simple. If your website takes bookings or receives paid traffic, uptime monitoring for a small business website should be agreed before launch, with a named person on the end of it. Treating it as an extra you'll sort out later is how customers end up being your alerting system.

Where to start

Ask yourself one question today: if the site went down this evening, who would know, and what would they do? If the honest answer is "a customer, eventually", that's the gap to close. You can see how we build and look after sites on our websites page.

If you want monitoring and a clear response path set up properly, on a site we built or one we've inherited, talk to an engineer.