Skip to content

Cluster hub

Website monitoring.

One long-form hub for the six monitoring checks a non-engineer runs on one site.

Uptime, SSL, broken links, form failures, checkout failures, page speed — six checks, one inbox, six deep dives below. Read the comparison table once, then follow each link to the page that runs the check in plain English.

How this fits together

The six checks, side by side.

Each row is one monitoring check and the trigger that fires its alert email. The capability name links to the deep page that explains the check end-to-end; the final column points at a free on-demand tool that runs the same probe against your URL.

CapabilityTriggerCatchesCadenceFree tool
Uptime monitoringHTTP probe from outside5xx, host suspension, DNS drift, CDN edge dark1–5 min/free-website-monitor
SSL monitoringTLS handshake + cert inspectionExpiry < 14d, broken chain, SHA-1 fallbackDaily/tools/ssl-checker
Broken-link checkingWalker across the page or sitemap404s, redirect loops, dead outbound citesWeekly/tools/broken-links
Form-failure detectionProbe email submitted to the form200-but-no-inbox, spam-folder drops, JS errors5–15 min/audit
Checkout-failure detectionFull funnel walk on the platform/thank-you w/o order, payment-redirect fails1–5 min/ecommerce-uptime-monitoring
Page-speed monitoringHeadless browser LCP/CLS/INP probeLCP > 2.5s, CLS > 0.1, INP > 200msHourly/tools/page-speed

Is this for you

Read this once before you click through.

The fit is structural, not personality. If the project you are running matches the left column, the rest of this site is built for you; if it matches the right column, the free tool at /tools/uptime-check is the cleaner pick.

SiteGuardian fits

  • You run a site that customers, donors, or readers have to reach today, not next week.
  • You have not tested your SSL expiry, contact form, or checkout funnel with a probe in the last 30 days.
  • You do not want to learn a monitoring dashboard — you want one quiet inbox and one loud email when something breaks.
  • You want PageSpeed / Core Web Vitals tracked against the 2.5s LCP threshold without installing a Lighthouse scheduler.

Skip this if…

  • Your site is a static brochure with no contact form, no payment, and no editorial cadence — uptime alone is enough.
  • You already run Datadog / Pingdom / UptimeRobot and have an on-call rotation that reads a dashboard.
  • You are shipping a one-off landing page with a one-week runway — the free tool at /tools/uptime-check is the right fit.

Methodology

How this page was assembled.

The editorial surface above is identical regardless of who visits. There is no login flow, no personalised content, no cookies beyond the theme preference — the page is a navigable index into the six capability deep pages, paired with a comparison table that points at the same leaf pages plus the free single-shot tools.

Each row of the comparison table is sourced from its matching /features/<slug> page. Trigger, catches, and cadence are the same wording the deep page uses under "What it is". The link map at the bottom of the page derives from src/content/capabilities.ts directly, so adding or removing a capability in the source updates the link map — and only the link map — without touching this page.

The "Is this for you" test is editor-grade reasoning, not a quiz or a runtime decision; it is honest about the operators SiteGuardian was designed for and the operators a different tool would fit better.

Next steps

Pick where you go from here.

If you are picking the monitor that gets installed — Read the plans, compare the cadence. If you are still feeling out what your site needs — Run the free audit and let one report tell you what is failing today.