Skip to main content
Question

OAuth verification stuck "Under Review" — Homepage requirement resolved via Search Console but UI is locked

  • June 10, 2026
  • 1 reply
  • 48 views

k3lly_b

Hello Google Community Team,

My OAuth app verification is currently stuck and I need an internal engineer to manually trigger a status refresh or pass this along to the Trust & Safety team.

* Project ID: dev-workrate
* The Issue: The Cloud Console Verification Center shows a blocking error under "Homepage requirements" stating: "Your homepage website is not registered to you."
* The Resolution: I have successfully verified full domain ownership for our production homepage via Google Search Console using this exact same Google account. 

The Problem: The console instructs me to "Reply to your email thread with our Trust and Safety team," but I have never received an initial email from the compliance team to reply to. Because the UI is entirely locked in the "Your branding is currently under review" state, I cannot modify fields or trigger a re-scan myself. 

Could a community manager please escalate this project ID to the Trust & Safety team so they can pull the fresh domain status from Search Console?

Thank you!

1 reply

hzmndt
Staff
Forum|alt.badge.img+12
  • Staff
  • September 5, 2026
 

Hi @k3lly_b,

This is a known deadlock condition in the OAuth verification state machine when the automated review triggers a "Pending developer action" status before the initial Trust & Safety email reaches your inbox. Because the console is waiting for an email reply to register the update, the UI stays locked.

While we flag this for a **Community Manager** to escalate internally to the Trust & Safety team for project `dev-workrate`, here are a few quick checks you can perform in parallel:

---

### 1. Check the Developer Contact Email Address

* The Trust & Safety automated emails are sent specifically to the **Developer Contact Information** email address configured on your OAuth Consent Screen, which may differ from your current Cloud Console login / Project Owner account.

* Search across **All Mail**, **Spam**, and **Trash** for emails from:

* `api-oauth-dev-verification-reply@google.com`

* `oauth-verification-support@google.com`

### 2. Verify Search Console Delegation

* Confirm that the Google account registered as a **Verified Owner** in Google Search Console is also an **Owner / Editor** on the Google Cloud project `dev-workrate`. If they are separate accounts, add your project owner account as a delegated owner in Search Console to ensure the automatic ownership link resolves.

### 3. Alternative Support Channel (If on a Support Plan)

* If your Google Cloud organization has an active **Cloud Customer Care Plan** (Standard, Enhanced, or Premium), you can open a case directly under **IAM & Admin > OAuth Consent Screen**. Support can route the ticket directly to the Trust & Safety queue with SLA tracking.

---

I have noted your Project ID (`dev-workrate`). Tagging @Community_Manager / community team to help pass this Project ID to the Trust & Safety team to pull the updated Search Console status and unlock your verification.