What is website monitoring? How it works and what to watch

Website monitoring explained: how checks work, what counts as down, how often to check, where alerts should go, and a starter list of what to monitor on any site.

· 4 min read · By the Spot Downtime team

Website monitoring is checking a site automatically, around the clock, and telling someone when it stops working. Without it, you find out the way most site owners do: a customer emails, a sale doesn't happen, or a colleague asks why the page is blank. With it, you usually know within a minute or two, often before anyone else notices.

How website monitoring works

A monitoring service requests your page from its own servers on a schedule, the way a visitor's browser would, and records what happened: the status code, how long it took, and whether the page contained what it should. When a check fails, it checks again to rule out a blip, then alerts you. When the site recovers, it tells you that too.

Every website monitor runs the same loop; the details of each step are what set tools apart.

What counts as down

A check fails when any of these happen:

FailureWhat it usually means
DNS lookup failsThe domain lapsed, or a DNS record was deleted or changed
Connection refused or timed outThe server or its web service is off, or a firewall is blocking it
TLS errorThe certificate expired or doesn't match the domain
5xx statusThe app crashed or a proxy can't reach it
Response too slowThe server is overloaded; Spot Downtime gives up after 10 seconds
Expected text missingThe page loaded but shows an error, a blank page or the wrong content

The last one matters more than it looks. Plenty of broken sites answer 200 OK while showing an error, so a monitor that only checks the status code reports them as fine. A keyword check, text that only appears when the page works, catches them.

Avoiding false alarms

The internet drops a packet now and then. If every failed request paged someone, people would learn to ignore the alerts. Good monitors confirm a failure before alerting. Spot Downtime retries after 2 seconds, then checks from California, Amsterdam and Singapore, and only opens an incident when the failure is real.

One failed check never alerts on its own: it's retried, then confirmed from the other regions.

How often to check

The interval is the longest an outage can go unnoticed. Every 5 minutes suits a blog or a brochure site. A shop, a SaaS app or an API customers depend on is worth checking every minute or faster. The free uptime monitoring guide shows what each interval means in detection time.

Where alerts should go

  • During the day: the team chat, Slack, Teams or Discord, where people already are.
  • At night: something that interrupts you, like SMS, a phone call, PagerDuty or a push alert from a monitoring app.
  • For customers: a status page, so they can see you know and stop emailing to ask.

What to monitor on any site

Start here

  • The home page, with a keyword from the footer
  • The page that earns money: checkout, sign-up or login
  • SSL certificate and domain expiry

Then add

Website monitoring isn't only uptime

Uptime is the core, but the term also covers performance, error tracking, change detection and traffic analytics. The website monitoring tools guide explains each kind and which ones a site actually needs.
Is it down? checkerSee whether any website is up right now, from our servers, without an account.Monitor your site free20 monitors with keyword checks and SSL warnings on the Free plan. No card needed.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading