One product system with multiple delivery layers.
Site Clinic exists because website risk is rarely one thing. Accessibility drift, broken links, weak metadata, crawl issues, security headers, AI retrieval, and proof of what changed all degrade quietly. The system is built to measure that reality, prioritize the next move, and keep the evidence trail honest across the app, API, and agent layers.
Different layers. One evidence standard.
We do not want a sales story, dashboard story, and delivery story that disagree. Support needs to be inspectable and claims need to be scoped.
Platform ambition does not grant shipping rights. Each capability has to earn its way into the app, API, MCP, and public marketing separately.
These products were built around the actual operator problem: the site drifts quietly while the owner is busy running the business.
John Liddy
John ran multiple small businesses long before Site Clinic existed. The product came from the operator view first: real websites break in quiet ways, owners are busy, and the harm shows up later unless someone is watching carefully and telling the truth about what changed.
ADA Audit Report remains an evidence-first entry product.
The one-time accessibility audit is still a valid way into the system, but it is not a fourth delivery layer. It is an evidence-first entry point that can hand off into the Site Clinic application layer when recurring monitoring or verification is the right next step.
Start with the layer that matches the job.
Need recurring monitoring and proof? Start with the Site Clinic app layer. Need a one-time accessibility artifact first? Use ADA Audit Report. Need to embed contract-ready checks into your own software or workflow? Use the developer layers. Present-tense claims always follow actual capability maturity.