Website uptime monitoring for a small business

Short answer: An uptime monitor visits your website every few minutes from outside and alerts you when it stops answering, returns an error, or no longer shows the content it should. For a small business, set up three things: an HTTP check on the home page, a keyword check on your most important page (booking, shop or contact), and warnings before your SSL certificate and domain expire. Send alerts to two people, and agree in advance what each alert means and who does what first.

Why you need it even with good hosting

Hosting companies watch their servers, not your website. Your site can be "up" from their point of view while your home page shows a database error, your booking widget is blank, or a plugin update has broken the checkout. Without monitoring, the first sign is usually a customer phoning to say "your website's down", or nobody saying anything and enquiries quietly drying up.

Monitoring doesn't prevent problems. It shortens the time between "broken" and "someone knows".

What a monitor actually checks

Most monitoring services offer the same core checks; the names below follow UptimeRobot's help centre, used here as one example (as of November 2026).

HTTP(S) check. The service requests a URL like a visitor would and judges the result by the HTTP status code it gets back. A 200 means fine; a 5xx code or no response means trouble.
Keyword check. The service loads the page and looks for a word or phrase, or for its absence. This catches the cases where the server answers normally but the page is wrong: an error message, a blank template, a "site under maintenance" screen left on.
Ping and port checks. Lower-level checks that a server or a specific service responds. Useful for custom apps and mail servers; less useful for a typical business website.
SSL certificate checks. Warnings before your certificate expires and alerts if it has errors. On UptimeRobot this is a paid-plan feature; its help centre notes that HTTPS monitors on the free plan aren't checked for certificate issues.
Domain expiry checks. UptimeRobot reads the expiry date from WHOIS records and alerts at 30, 14, 7 and 0 days before expiry, again on paid plans. Some domain extensions aren't covered because of their registry's WHOIS rules, so test that it works for yours.

Other services (Better Stack, Pingdom, Freshping and many hosting control panels) offer similar checks; compare which features sit on free versus paid tiers on their current pages.

Setup guide

List what matters. Usually: home page, the page that makes money (booking, shop checkout start, quote form), and any separate app or portal on a subdomain.
Create an HTTP(S) monitor for the home page. Use the exact address visitors use (https and www or not), so you're testing the real thing rather than a redirect.
Create a keyword monitor for the money page. Pick text that only appears when the page works properly, such as the label on your booking button or a product name, and set the condition to alert if it's missing. Avoid text that changes, like prices or dates.
Turn on certificate and domain expiry warnings if your plan includes them. If it doesn't, put both renewal dates in a shared calendar with reminders a month ahead.
Choose the check interval. Every five minutes is plenty for most small business sites. Faster checks mainly matter for shops with constant traffic.
Route alerts to two people. Email plus a push notification or SMS. One person is a single point of failure: holidays, a phone on silent, someone leaving.
Add your web developer or host as an alert contact if they're responsible for fixing things, and agree on that in writing.
Set up a quiet test. Temporarily point a keyword monitor at text that doesn't exist to confirm alerts arrive, then fix it.
Write the first-response table below into a shared document.

What each alert means and what to do first

Alert	What it usually means	First response (within 15 minutes)
Down: no response / timeout	Server or hosting outage, DNS problem, or the site is overloaded	Open the site on mobile data, not office Wi-Fi. Check the host's status page. Contact the host if it's down for you too
Down: 500 Internal Server Error	Something in the site's code or configuration failed; MDN describes it as a generic error for a situation the server doesn't know how to handle	Think about what changed recently (plugin update, new code, edits). Contact whoever made the change or your developer
Down: 502 Bad Gateway / 504 Gateway Timeout	A server in front of your site (proxy, CDN, load balancer) didn't get a valid or timely response from the server behind it	Check the CDN or host status; often temporary, but if it lasts more than a few minutes contact the host
Down: 503 Service Unavailable	Server not ready: maintenance mode or overload	Check whether maintenance mode was left on after an update
Keyword missing	Page loads but content is wrong: error message, broken template, plugin conflict, expired embed	Look at the page yourself. If the booking or shop widget is from a third party, check their status page
SSL expiring soon / SSL error	Automatic renewal failed or certificate misconfigured	Ask the host to renew or reissue; don't wait until the expiry day
Domain expiring soon	Auto-renew off or the card on file has expired	Log in to the registrar and renew now; see the next section

After the issue is fixed, write one line: what happened, how long, what fixed it. After a few incidents, patterns appear.

Don't forget the domain

Expired domains take websites and email down together, and getting them back can be slow. Expiry alerts are cheap insurance, but the real fix is auto-renew with a valid card and registrar login details you can actually access. Our separate guide on domain renewals and registrar access covers that in detail.

FAQ

Is a free monitoring plan enough?

For a basic "is the site up" check on a small site, often yes. Certificate and domain expiry checks, faster intervals and SMS alerts tend to sit on paid tiers, so check what each provider includes.

Will monitoring slow my site down?

No. A check every few minutes is a tiny amount of traffic, much less than a single visitor browsing.

Why did I get a "down" alert when the site worked for me?

Monitors check from several locations; a regional network issue or a brief server hiccup can trigger an alert. Check whether your monitor can confirm from a second location before alerting, and switch that on if it can. If false alarms repeat, look at the pattern rather than ignoring them.

Should customers see our uptime?

For most small business sites, no. Public status pages make more sense for software products that customers log in to.

If you'd like monitoring set up with alerts that reach the right people and a clear plan for each one, tell us what your website needs to keep doing.