How often are checks run?

Uptime checks run every 15 minutes. Security and SEO sweeps run daily, and heavier crawls run on their own schedule so a large site does not slow the rest of the portfolio.

Does it need anything installed on the sites?

No. Every check works from the outside against the public site. WordPress sites can optionally run a small reporter plugin for exact component versions, and applications can post their errors to an ingest endpoint, but neither is required.

What happens when a check fails?

A single failure is not an outage. Failures are confirmed across consecutive attempts before an incident opens, and only then does an alert go out — separately worded for your team and for the client.

Website monitoring that covers the whole site, not just the ping

Most monitoring answers one question: is the server responding? That leaves the failures that actually reach a client unwatched — an expired certificate, a contact form that silently stopped delivering, a plugin two versions behind a published CVE, a checkout that broke while every page still returned 200. SiteIntact runs all of those checks against every site you look after and puts the results in one place.

Monitor your first site See how it works

One portfolio, every signal

Each website gets uptime, TLS, DNS and email-authentication, security headers, exposed files, dependency advisories, on-page SEO, accessibility risk, and — where the stack supports it — WordPress component currency and store order flow. The portfolio view ranks sites by what needs attention, so a morning check is one screen rather than twenty tabs.

Uptime checks every 15 minutes, confirmed across attempts before anything is called an outage
Certificate expiry and chain problems, caught weeks before a browser warning
Security headers, publicly reachable files, and published advisories for detected components
DNS and email authentication drift — the records that decide whether mail and traffic arrive
Site-wide SEO crawls reported as what changed, not the same audit every week

Automated checks detect roughly 30–40% of accessibility issues. This report reduces risk; it is not a compliance determination, a certification, or legal advice.

Findings that say what to do

A finding that reads 'missing header' teaches nobody anything. Every finding here carries a plain description of what it means, the concrete fix for whoever does the work, and a separate one-sentence version written for the client — because the person paying the retainer should not have to parse a header name to know whether they need to worry.

Built for a book of clients

Sites belong to clients, clients belong to a workspace, and access follows that structure. A client sees their own sites and nothing else. Alert routing, report recipients, check sensitivity and maintenance windows are all set per client, so a demanding retainer and a small brochure site do not have to share one policy.

Questions people ask

How often are checks run?: Uptime checks run every 15 minutes. Security and SEO sweeps run daily, and heavier crawls run on their own schedule so a large site does not slow the rest of the portfolio.
Does it need anything installed on the sites?: No. Every check works from the outside against the public site. WordPress sites can optionally run a small reporter plugin for exact component versions, and applications can post their errors to an ingest endpoint, but neither is required.
What happens when a check fails?: A single failure is not an outage. Failures are confirmed across consecutive attempts before an incident opens, and only then does an alert go out — separately worded for your team and for the client.

Point it at a site you already know

One website is free, with the full product — the same checks, alerts, status page and monthly report. Adding a site whose history you already know is a fairer test of SiteIntact than any demo.

Monitor your first site