OAuth branding verification still shows app-name mismatch after fixes — no Trust & Safety email

Google Cloud Cloud Foundations & Onboarding
1

Hello,

I’m requesting help with a Google OAuth branding verification that appears to be using stale information.

OAuth app name: superwoman
Homepage: (URL Removed by Staff)

The verification originally reported that the app name on the OAuth consent screen did not match the homepage.

On August 13, 2026, I completed the following:

  • Standardized the app name to lowercase superwoman across the landing page, application, metadata, and OAuth configuration.
  • Confirmed the homepage returns HTTP 200 and contains a server-rendered description of the application’s purpose.
  • Matched the application name in the title, headings, application-name metadata, Open Graph metadata, and web manifest.
  • Confirmed the homepage links to the privacy policy and terms of service.
  • Confirmed ownership of superwoman.so through Google Search Console.
  • Restored the configured OAuth homepage to (URL Removed by Staff).
  • Removed the temporary /about-superwoman/ verification page.

The Verification Centre currently says that branding and data access are under review, but the same app-name mismatch issue is still displayed. I have not received an email from the Trust & Safety/OAuth verification team, including in spam or archived mail.

Could a Google team member please confirm whether the review is using a stale crawl and manually trigger a fresh review of the current homepage?

I can provide the project ID and project number privately if required. Please let me know the appropriate secure channel.

1 Like