OAuth verification — Homepage flagged unresponsive, but confirmed reachable via multiple independent checks

Google Cloud Cloud Foundations & Onboarding
1

Project ID: project-(PII Removed by Staff)
App name: dayleap
Homepage: https://dayleap.net/
Privacy Policy: https://dayleap.net/dayleap-privacy-policy.html
Terms of Service: https://dayleap.net/dayleap-terms-of-service.html
(all three return HTTP 200; dayleap.net is listed as an authorized domain)

The Verification Center flags “Homepage requirements — Your home page URL is unresponsive” (Last reviewed: Jul 28, 2026).

We initially had three separate live domains pointing at the same app (dayleap.net, dayleap.xyz, dayleap.vercel.app), which may have caused ambiguity for the checker. Since then we’ve:

  1. Set up 308 permanent redirects so dayleap.xyz and dayleap.vercel.app both redirect to dayleap.net, leaving one canonical production domain.
  2. Added a <link rel="canonical" href="https://dayleap.net/"> tag to the homepage.
  3. Verified independently that the homepage is fully reachable:
    • curl -sI https://dayleap.net/ returns HTTP/2 200
    • Response is properly compressed (content-encoding: br)
    • No deployment protection, password protection, or bot-challenge is enabled on the domain
    • Google Search Console’s own “URL Inspection → Test Live URL” tool confirms: “URL is available to Google” / “Page can be indexed.” This is notable because it’s Google’s own crawler infrastructure confirming reachability — the same Googlebot that powers Search Console’s Live Test successfully fetched this exact URL, which strongly suggests the OAuth verification checker’s “unresponsive” result is stale or reflects a check made before these fixes went live, rather than an ongoing reachability issue.

Despite all of this, the verification homepage check still shows “unresponsive,” and resubmitting the form hasn’t updated the status.

We have never received any email from the Trust & Safety team (checked all inboxes, including spam), so we’re unable to follow the “reply to your email thread” instruction.

Could someone please manually re-check the homepage requirement, or escalate this to the Trust & Safety team?

Thank you.

2

Update: We checked our Vercel Observability logs. Over the last 12 hours we’ve had 38 requests from google-inspectiontool (73.5% cache-hit rate) and 3 requests from googlebot (100% cache-hit rate), both indicating successful responses rather than errors.

Combined with our earlier findings (Search Console’s Live URL Test confirming the page is available to Google, and the HTTP-to-HTTPS redirect enforced platform-wide by Vercel), everything we can verify points to the homepage being reachable by Google’s crawlers.

Would appreciate a manual look at the “unresponsive” flag given this. Thank you.