Skip to content

Website monitoring

Website monitoring that checks the page, not just the server

Your uptime tool says everything is fine. Your customer is looking at a checkout page that does not work. Sitewatch catches the silent failures uptime monitors never see — missing scripts, missing stylesheets, redirects that loop, and pages quietly serving the wrong thing.

  • Confirms pages actually work, not just that a server answered
  • Checks every file your page needs is really there and usable
  • Alerts across 6 channels including Slack, email and PagerDuty
Monitor your first site freeSee pricing

Free scan

See what your uptime monitor misses — free

Scan any URL in 20 seconds. We check broken assets, JavaScript errors, Core Web Vitals, security headers, schema, and SSL — the issues visitors actually feel.

02Why it's different

Same page. Two very different answers.

The server is reachable

Uptime tools:
Detected
Sitewatch:
Detected

The page is missing its styling

Uptime tools:
Reported as healthy
Sitewatch:
Flagged with the file that failed

A script the page needs has gone missing

Uptime tools:
Reported as healthy
Sitewatch:
Caught on the next check

The page quietly changed after a deploy

Uptime tools:
Invisible until someone notices
Sitewatch:
Structural change flagged automatically

Redirects send visitors in circles

Uptime tools:
Followed silently
Sitewatch:
Loops detected and reported

The certificate or domain is about to lapse

Uptime tools:
A basic reminder, if any
Sitewatch:
Warned 30 days early

You can see what actually broke

Uptime tools:
Up or down — that's it
Sitewatch:
A full report naming the affected component

03The blind spots

Failures that happen while your uptime tool says OK.

The page loses its styling

CSS-GONE

A stylesheet goes missing or arrives as the wrong kind of file, and the page renders as raw unformatted text.

UptimeLoads fast, reports healthy.
SitewatchNames the missing file and the page it breaks.

Interactive parts stop working

JS-GONE

A script the page depends on disappears, so forms, menus and checkout silently do nothing when clicked.

UptimeServer responds — 100% up.
SitewatchChecks every script the page asks for is really there.

Redirects send visitors in circles

REDIR-LOOP

A misconfigured redirect bounces visitors back and forth until the browser gives up and shows an error.

UptimeFollows the redirect and reports OK.
SitewatchDetects the loop and reports where it starts.

A deploy quietly changed the page

PAGE-DRIFT

A release ships a change nobody intended, and the page stays different until a human happens to notice.

UptimeNo idea the page changed at all.
SitewatchCompares each check to the last good version and flags the difference.

The certificate lapses

SSL-EXP

A certificate expires and browsers replace your site with a full-page security warning.

UptimeA basic reminder, if any.
SitewatchWarns 30 days early and escalates as the date closes in.

The URL stops serving a page

NOT-A-PAGE

A route starts returning a file download or raw data instead of the webpage a visitor expects.

UptimeSomething answered — reported as up.
SitewatchConfirms the URL still returns a real webpage.

04Anatomy of a page

Every layer of your site, watched.

A website is far more than a server. Select any layer to see how it fails — and how Sitewatch catches it.

The page itself

document

How it fails — The URL hands back an error page, a file download or raw data instead of the webpage a visitor expects.

How Sitewatch detects it — Confirms every monitored URL still returns a real webpage with the content you expect.

Styles

stylesheet

How it fails — A stylesheet goes missing or arrives as the wrong kind of file, and the page renders completely unformatted.

How Sitewatch detects it — Checks every stylesheet the page asks for actually loads, as a stylesheet.

Scripts

scripts

How it fails — A script is renamed or dropped in a deploy, so buttons, forms and checkout stop responding.

How Sitewatch detects it — Confirms each script the page needs is present and usable — no test scripts to write.

Images & media

assets

How it fails — Product photos and hero images vanish because a path broke or the image host went down.

How Sitewatch detects it — Resolves every image the page references and flags the ones that fail.

Page content

integrity

How it fails — A deploy or a CMS edit silently changes the page, and it stays wrong until somebody notices.

How Sitewatch detects it — Compares each check against the last good version and flags unexpected structural changes.

Routing

redirects

How it fails — Redirects loop, or the domain quietly starts resolving to a different server than you expect.

How Sitewatch detects it — Follows the route on every check and reports loops and unexpected destinations.

Certificates & domain

transport

How it fails — A certificate expires or a domain registration lapses, and the site becomes unreachable or untrusted.

How Sitewatch detects it — Tracks certificate and domain expiry with 30-day warnings, plus chain, protocol and cipher health.

Search visibility

indexing

How it fails — A stray rule in robots.txt tells search engines to drop the whole site, and rankings quietly disappear.

How Sitewatch detects it — Watches robots.txt and your sitemap, and alerts on changes that would deindex you.

0520 detection rules

What we detect

Page integrity

  • Page output that differs from the last good check (fingerprint change)
  • URLs that stop serving a webpage and start serving data or a download
  • Files served as the wrong kind of file, which browsers then refuse

Infrastructure & routing

  • Redirect loops — circular redirects that leave visitors on a blank page
  • Host drift — your domain resolves to an unexpected server
  • Sites that cannot be reached at all

Security & expiry

  • Certificate expiry, broken certificate chains, outdated protocols and weak ciphers
  • Domain registration expiry, caught 30 days early

Content, search & DNS health

  • Watched keywords or phrases that were present and then disappeared
  • An accidental Disallow: / in robots.txt that would deindex the site
  • Unexpected DNS changes to MX (mail) and CNAME (alias) records
  • Broken URLs inside your own sitemap.xml, audited weekly

06How it works

What happens on every check.

No test scripts. No credentials. Point Sitewatch at a URL and it does the rest — around the clock, from up to 2 regions on Pro.

Start free
  1. 1

    Sitewatch opens your page

    We request your URL and retrieve the full page, the way a real visitor would.

  2. 2

    Reads what the page needs

    Every script, stylesheet, image and font the page references is identified and becomes something to verify.

  3. 3

    Checks each one is really there

    Each file is requested to confirm it exists and arrives as the right kind of file — a stylesheet that comes back as an error page is caught here.

  4. 4

    Compares against the last good check

    The page is fingerprinted so an unexpected structural change stands out immediately, even when nothing is technically broken.

  5. 5

    Finds a problem

    A missing file, a redirect loop, an expiring certificate — anything that breaks the page for a real visitor.

  6. 6

    Opens an incident and alerts you

    With the affected page, the exact component that failed and a plain-English summary. Confirmed by 2-of-3 retries first, so blips never page you.

07What you get

Outcomes, not a feature list.

Find out before your client does.

Every check verifies the whole page, not just the server. The stylesheet that vanished on Friday afternoon becomes an alert on Friday afternoon — not a Monday morning phone call from an angry client.

$ sitewatch check clientsite.com
✓ page real webpage · unchanged
✓ scripts 6/6 loaded
✓ images 31/31 loaded
✕ styles 3/4 — checkout-form.css missing
✕ incident opened · checkout unstyled

See the pages you are not protecting yet.

Most monitoring dashboards go green because you only added the homepage. Sitewatch scores your coverage and names the important pages nobody is watching, so a healthy dashboard never hides a gap.

▸ coverage report · clientsite.com
✓ monitored home · pricing · about
coverage score 42% — 3 of 7 important pages
✕ unmonitored /checkout · /login · /booking
✕ 3 high-value pages unprotected

20

Detection rules covering the failures a ping cannot see.

2-of-3

Retry confirmation before an alert fires, so blips never page you.

Every page

Not just the homepage — all your critical pages are checked.

See what your uptime tool is missing

Free plan. No credit card. Set up in 2 minutes.

Try it free See pricing

08Questions

Website monitoring questions, answered.