Useful
The scan identifies the most important defects first, names the affected evidence, and gives a practical correction rather than generic advice.
Release acceptance standard
Would we rely on this report ourselves?
Every release must be useful enough to guide a real repair decision, honest about uncertainty, mobile-friendly, and technically deployable.
Release criteria
Accurate
Optional signals do not become AdSense failures. Unknown account or human-review requirements are never silently counted as passes.
Fast enough
Independent network checks use bounded concurrency, timeouts, response-size limits, and clear progress messages.
Safe
Private-network targets are blocked, input is validated, API responses are uncached, and email secrets stay in Cloudflare.
Accessible
The core scan works on mobile, controls have labels, long domains wrap, and the report remains understandable without color alone.
Verifiable
Deployment health, API routing, technical files, JavaScript syntax, XML, links, and archive integrity are tested before handoff.
What a release must not do
- Promise or predict AdSense approval.
- Show a perfect verified score when meaningful requirements remain unverified.
- Penalize a site merely for lacking Analytics, social profiles, a search box, CSP, or an old domain.
- Call an edge fetch time a full browser page-load measurement.
- Hide scanner limitations or incomplete crawl coverage.
Current public scan coverage
Version 31 samples up to 16 internal pages, 18 homepage assets, technical publisher files, structured data, trust signals, domain-history context, and 134 mapped requirements. It also includes a live scanner smoke test in the deployment integrity page. Full account and editorial review remain separate.