My OAuth consent screen is stuck on a single failing check: Purpose not explained

Google Cloud Cloud Foundations & Onboarding
1

Title: Brand verification stuck at “home page does not explain the purpose of your app” — homepage is compliant, no Trust & Safety email to reply to

Project number/ID: (PII Removed by Staff)
App name: Kloti
Homepage: (URL Removed by Staff)
Support/developer email: (PPI Removed by Staff)
Scopes requested: basic only (openid, email, profile) — used solely for “Sign in with Google”

Summary

My OAuth consent screen is stuck on a single failing check:

Your home page does not explain the purpose of your app.
Update your home page to outline the purpose of your application.

The privacy policy and branding checks have passed. Only the homepage check keeps failing, and it fails again immediately each time I resubmit, even though the homepage clearly and prominently states the app’s purpose.

The Verification Center tells me to “reply to your email thread with the Trust & Safety team,” but I have never received any email from Trust & Safety (checked inbox, spam, and all folders on the support/developer email above). So there is no thread for me to reply to.

What the homepage contains

Kloti is an AI visual studio for small brands and online sellers. The homepage states this in the page title, the meta description, and the first lines of visible body text. A plain HTTP GET returns HTTP 200 with the purpose in server-rendered HTML (it does not require JavaScript to read), robots.txt allows the homepage, and http redirects cleanly to https.

Steps I have already taken to resolve it

  1. Added a server-rendered, plain-text statement of the app’s purpose in the initial HTML so it is readable without executing JavaScript.
  2. Fixed a brief blank-render state in our single-page app by adding a purpose-stating fallback, so the page is never blank at any point during load.
  3. Published real, crawlable static Privacy Policy and Terms pages (privacy check now passes).
  4. Moved the registered homepage to a fresh URL /home in case a stale verdict was cached against the previous URL.
  5. Verified with a Googlebot user-agent fetch that the live page returns 200 with the purpose present in the title, meta description, and body.

Request

Because the homepage is compliant and there is no Trust & Safety email thread for me to reply to, could someone please manually re-review or advance the verification for this project? Happy to provide any additional details.

Thank you.

1 Like