Website monitoring for small businesses, in plain terms.

Website monitoring sounds heavy. It isn't. For a small business, it is exactly four moving pieces, and once you know what they are you can decide whether the cheapest tool that does all four is enough for you, or whether you actually need the platform with the team behind it. Most small shops need the cheap one.

The four pieces you actually need

First, you need a probe. A probe is a small program that, on a schedule, asks your website a question that has a yes-or-no answer. The simplest question is "are you reachable?" The next-simplest is "did you answer in under three seconds?" Anything beyond that is optional for a small shop.

Second, you need a destination. A destination is the thing the probe measures against. For most people this is the homepage and one or two other URLs — the contact page, the order page, the booking page. The rule of thumb I use is one URL per thing you would be embarrassed to have offline on a Tuesday afternoon.

Third, you need a cadence. A cadence is how often the probe asks. The monitor that asks every minute will catch most outages within a minute. The monitor that asks every fifteen minutes will, on average, take seven and a half minutes to find a problem you already have. For most small shops, every minute is the right cadence.

Fourth, you need a single binary outcome. When the probe gets a no-answer, or a slow-answer, somebody has to find out. The cleanest outcome is one email to one inbox. If you want to be clever, also a second email when the site comes back. That is the whole product. The rest — dashboards, on-call rotations, status pages, post-mortem timelines — is for software teams with more than three people on them.

What the four pieces look like together

A probe pings your storefront every minute. If the storefront answers in time, nothing happens; the dashboard shows a green check, the inbox stays quiet. If the storefront doesn't answer, you get one short email — site, time, what it saw. If your storefront is fixed fifteen minutes later, you get one more short email saying so. You do not learn a new tool. You do not configure anything. You do not consult a chart.

How SiteGuardian lines up with the four pieces

SiteGuardian is the boring smallest one. It does the four pieces and nothing else. No status page for your customers. No synthetic transaction recorder. No anomaly detection you have to tune. Add a URL, pick a slow threshold that fits that site, and SiteGuardian starts probing within a minute. If you would rather own the four-piece tool once and stop paying attention to your site, the cheapest way to do that is to wire it into SiteGuardian's pricing and let it mail you. The lifetime tier exists for the shop that wants to pay once and stop thinking about it altogether.

The closest free alternative to compare against is SiteGuardian versus UptimeRobot. UptimeRobot still runs one of the broadest free tiers in the category. Worth a fair comparison if free is part of your buying criteria.

What you don't need yet

Status pages. Synthetic checkout flows. Real-user monitoring. Per-region latency reporting. Most of those are enterprise answers to enterprise questions. If your store has fewer than ten staff, your question is almost always simpler: is it up, is it fast enough, and does somebody know when it isn't. That is the whole game.

If you would rather check whether the four pieces are actually working on your site right now, run the free URL audit: it pings the home page, looks at the TLS cert, crawls a handful of outbound links, and reports what it sees in under thirty seconds.

The SiteGuardian pricing page lists what each tier unlocks and how often it bills.