Find the obvious CASA review blockers before you pay an assessor.
PageLens checks the public frontend and policy evidence a reviewer is likely to see first, then packages the findings into a readiness report your team can remediate before formal Google OAuth CASA assessment.
PageLens does not certify your app or issue a Letter of Validation. Use this to prepare before a Google-authorized assessor review, not instead of one.
What PageLens can prove from the outside.
The scanner crawls, renders, inspects headers, records evidence and packages the findings for your builder, reviewer, buyer or assessor.
Security headers, CSP, HSTS, CORS, cookies and cache-control review
Third-party script and SRI evidence for assessor-visible supply-chain risks
Privacy policy, data deletion and OAuth disclosure page discovery
CASA / OWASP ASVS / CWE-style mapping for findings PageLens can verify
Assessor-facing evidence pack in Markdown and PDF exports
PageLens checks what outsiders can see before they see it.
This is public-surface readiness: crawlable pages, rendered UI, screenshots, headers, cookies, storage, scripts, policies, metadata and trust signals. It is designed to turn visible risk into a clear fix list.
PageLens does not certify your app or issue a Letter of Validation. Use this to prepare before a Google-authorized assessor review, not instead of one.
Evidence pack includes
- CASA rule mapping
- Header and cookie evidence
- Policy page signals
- Third-party script inventory
Run the right public-surface readiness scan.
Start with the product that matches the risk you need to remove, then use the report evidence to fix issues before reviewers, buyers, customers or assessors find them.