OAuth branding verification stuck — app name mismatch fixed and live, no Trust & Safety email received

Google Cloud Cloud Foundations & Onboarding
1

Project: (PII Removed by Staff)

My app’s branding verification is stuck. The original flag was: “The app name shown on the OAuth consent screen doesn’t match the app name on the home page.”

I have fixed this and deployed to production:

  • OAuth consent screen app name: WooCalen
    • Home page (URL Removed by Staff): the brand name “WooCalen” appears in the page title, the main H1 heading, og:site_name, JSON-LD, and the footer — matching the console app name character-for-character.
      • Privacy policy (the /privacy path) and Terms (the /terms path) are live on the same domain and branded “WooCalen”.
        • The app requests no sensitive or restricted scopes (the Data access status confirms verification isn’t required for scopes).
      • The change is live (verified in an incognito window). However, the “Last reviewed” date predates my fix, and I never received any email from the Trust & Safety team (checked inbox and spam thoroughly), so the console’s instruction to “reply to the email thread” is impossible to follow.
    • Could a community manager please trigger a re-review, or point me to where the verification reply should go? Happy to provide any additional details. Thanks.
2

Update — I’m genuinely confused. I have now verified every single requirement I could find across the solved threads in this forum, and the branding status still shows “in review / pending developer action” with the exact same finding (“the app name on the OAuth consent screen does not match the app name on the home page”), and the “Last reviewed” date still predates all my fixes.

Here is everything I have confirmed on my project (PII Removed by Staff):slight_smile:

  • Exact name match (incl. capitalization): the OAuth consent screen app name is exactly “WooCalen”. The identical string “WooCalen” appears in the home page document title, the H1 heading, og:site_name, og:title, application-name, author, JSON-LD structured data, and the footer — character for character. I checked application-name and apple-mobile-web-app-title for stale casing variants; there are none.
  • Dedicated, fresh home page: I pointed the OAuth “App home page” field at a brand-new server-rendered URL Google had never crawled (URL Removed by Staff) that states the app’s purpose first and explains how it uses Google Calendar data, with links to Privacy and Terms.
  • Crawlability: the page returns HTTP 200 with 0 redirects and a byte-identical body for Googlebot, Google-InspectionTool, curl, and an empty user-agent. No login wall, no bot challenge. robots.txt allows Google
  • Search Console: the domain is verified as a Domain property under the project-owner account. URL Inspection → Test Live URL returns “URL is available to Google” and “page can be indexed”. I also requested indexing.
  • Privacy Policy and Terms: live on the same domain, HTTP 200, linked from the home page.
  • Scopes: non-sensitive only (Data access status confirms scope verification is not required).
  • Logo: I even removed the app logo from the consent screen.
  • Despite every one of these checks passing, the finding never changes — including on a resubmission where I changed nothing at all. And there is still no Trust & Safety email thread anywhere to reply to (inbox, spam, and all owner/editor accounts searched with in:anywhere).
  • At this point I’ve run out of things to verify on my end. Could a community manager please trigger a fresh re-review, or route this to the Trust & Safety team? Thank you.