Check a client site the moment something feels off.
Every connected website's homepage is checked every 5 minutes, and you are told when it has not served visitors for half an hour. The pages that matter, certificates, mail records and more run when you start them.
Ask the question that matters, when it matters.
Each check below runs on the website you choose, when you start it. Only the homepage is checked on its own, every five minutes.
Can the public website be reached, and does the response look like a real page?
The checkout, booking or contact page that matters most to that client.
Certificates, domains, mail path, database write probes and other slower-moving signals.
Cloaking and broken-link checks, typically after a website has moved.
Enough coverage to spot trouble without drowning in noise.
Different risks need different questions. SiteVigilante lets you ask each one when it matters instead of pretending everything needs constant scanning.
Reachability and response-quality checks catch obvious outages and broken responses.
Fatal signatures and abnormal responses help distinguish “up” from actually working.
Slow-moving infrastructure signals, read when you run the check.
Deeper checks add operational context beyond reachability.
See what needs attention before maintenance day arrives.
Monitoring belongs beside updates, findings, performance and reporting, so the website record tells one operational story instead of forcing you across separate tools.
Check one client site now.
Connect a WordPress website and run your first check in minutes.