What SitesProof is, and what it refuses to do
SitesProof crawls the client sites a web agency looks after, once a week, and turns what it saw into one document per client that the agency sends on as its own work.
It exists because of a gap that is easy to describe. A care plan is sold on visible work, and the work is invisible. The monthly report that agencies already send lists updates applied, backups taken and uptime held — and nothing at all about the three things clients started asking about: whether the checkout loads scripts nobody approved, whether cookies fire before the banner, whether someone using a screen reader can get through the form. Those questions arrive by email, usually at the worst moment, and there is no tool that answers all of them across a portfolio in one place.
What it will not do
This matters more than the feature list, so it is near the top.
It does not certify anything. There is no score, no grade, no percentage and no pass mark. A crawler can check a fraction of WCAG's success criteria, cannot read a privacy notice and judge it, and cannot know that an unfamiliar script should not be there. Every one of those is a human judgement, and a number out of 100 hides the judgement rather than making it. The FTC fined accessiBe $1M over claims an automated product made sites compliant; that is the regulator agreeing with what accessibility practitioners have said for years.
It does not change anything. No overlay, no auto-fix, no widget, nothing installed on the client's site. The crawler loads pages the way a browser does and writes down what it saw.
It does not put our name on your work. The report carries the agency's logo, colours and the client's name. The only thing on it that is ours is the disclaimer, and that paragraph exists to protect the agency from the claim it refuses to make.
Who builds it
One person, working in the open about what is and is not finished. Where a plan lists something that is not built yet, the pricing page says so in those words rather than leaving the bullet to do the lying.
Where it is
Support is documentation, email and in-app chat. There is no call to book, no demo to sit through and no sales process — signing up, adding a site and paying all work without talking to anyone, and that is deliberate rather than a stage we have not grown out of.