Public endpoints only
Scavo does not ask for your CMS password to run website health and uptime checks.
About Scavo
I have spent fifteen years building and looking after websites. Most problems were not dramatic launch-day failures. They were small changes that went unnoticed because nobody had time to keep checking.
Scavo keeps that routine in one place: check the site, keep the evidence, and tell you what deserves attention.
The recurring problem
A plugin changes a header. A consent banner behaves differently after an update. A new AI crawler arrives with rules nobody had to consider last year.
Most of it is manageable when somebody spots it early. Scavo makes that check routine.
A note from Alex
I build the product, read the reports and answer the support messages. When something looks wrong, you can ask the person responsible for it.
I would rather say that a result can wait, that a check was inconclusive, or that Scavo is not the right tool than manufacture urgency.
Reliability in practice
Scavo does not ask for your CMS password to run website health and uptime checks.
Results keep the observed value, timing and fix guidance together.
The same monitoring product powers a public view of Scavo availability.
Questions reach Alex directly, including the awkward ones about whether Scavo is a fit.
Account data is encrypted at rest, status pages expose only what you choose, and you can delete your account data from Scavo. Read the privacy policy.