Check 1: Homepage accessibility
Check whether your homepage is publicly accessible and visible in server-rendered HTML.
Check public homepage HTML, policy links, brand and origin consistency, and submitted OAuth scope categories before verification.
Built for developers preparing sensitive or restricted scope verification.
Critical finding
Privacy link missing from initial HTML
Render the policy link in the server response so reviewers can discover it without JavaScript.
Preflight coverage
Six practical checks turn a scattered submission into a concrete remediation list.
Check 1: Homepage accessibility
Check whether your homepage is publicly accessible and visible in server-rendered HTML.
Check 2: Privacy policy links
Compare submitted privacy and terms URLs with links in the initial homepage HTML.
Check 3: Domain consistency
Highlight origin differences across the submitted homepage, privacy, and terms URLs.
Check 4: OAuth scope risk
Identify basic sign-in scopes, Google API scopes, duplicates, and permissions that require confirmation in Google Cloud Console.
Check 5: Brand consistency
Compare your app name and website metadata for obvious branding mismatches.
Check 6: Explicit scan limits
See which Console settings, policy wording, demo videos, logos, and ownership signals were not checked.
How it works
Add the public URLs, client type, and OAuth scopes you plan to submit.
Review the readiness areas and issue categories in one focused pass.
Resolve visible website, configuration, and evidence gaps before review.
Organize justifications and demo materials around reviewer needs.
Pricing
Start with the public details reviewers will see. No account is required in this validation build.