OAuth verification: homepage flagged "unresponsive" although Google's own fetch got HTTP 200, no Trust and Safety email

Hello,

My app’s OAuth verification (Glass OS, an Android launcher requesting the Google Tasks scope) is blocked at “Homepage requirements” with “Your home page URL is unresponsive.” Branding guidelines have passed.

The homepage is https://glass-os.app, with the privacy policy and terms in the footer, matching the Branding page exactly. Every URL returns HTTP 200 over both https and plain http, with no redirect, login or bot challenge. robots.txt allows all crawlers and the domain is verified in Search Console.

I have edge request logs. When I resubmitted at 18:12 UTC on 27 October, requests arrived from Google LLC (74.125.210.x, user agent “Google”) for the privacy policy page and the homepage’s media files. Every response was 200 or 206, with no errors. Within seconds the Verification Center again showed “Your home page URL is unresponsive.”

I have never received a Trust and Safety email, so I have no thread to reply to as the Verification Center asks.

Could someone on the OAuth verification team review the homepage check manually? I can share the project ID and logs privately.

Thank you.

One detail in your post stands out: your logs show Google fetching the privacy policy and the homepage’s media files, but you don’t mention a GET for the homepage document itself (/). I’d check that first:

  • Look for a request to the exact homepage URL from the Branding page, with or without the trailing slash, and its response time.
    • Check whether the domain has an AAAA (IPv6) record. If it does, make sure the site actually answers over IPv6. A checker that tries IPv6 first can time out while IPv4 tests look fine.
      • Make sure the main text is in the initial HTML rather than rendered by JavaScript after load, and that large media doesn’t hold the page back.
    • If all of that is clean, use “I believe the issues found are incorrect. Request additional review” from View issues. That’s the documented way to get a person to look instead of the automated check (it’s described in the Google Cloud Help article “Manage OAuth App Branding”).