OAuth Branding Verification rejected 4x with identical reasons despite meeting all documented requirements

Google Cloud Cloud Foundations & Onboarding
,
1

Summary

My Google Workspace add-on (Mail Merge for Sheets) has been rejected 4 consecutive times with identical reasons, even though both requirements are clearly met:

  1. “Homepage does not explain the purpose of your app”
  2. “App name in OAuth consent screen does not match the app name on your homepage”

Details

  • Cloud project: (PII Removed by Staff)
  • OAuth Consent Screen app name: Mail Merge for Sheets
  • Homepage URL: https://mailmerge.lazri.net/

Homepage HTML (raw curl output, no JS required):

  • <title>Mail Merge for Sheets</title> ← exact match to Consent Screen app name
  • <h1>Mail Merge for Sheets</h1> ← exact match
  • <meta name="description" content="Mail Merge for Sheets is a Google Sheets add-on for sending personalized bulk emails...">
  • OGP meta tags (og:title, og:description, og:type, og:url) all matching
  • h1 followed by 3 paragraphs explaining the app purpose
  • Features section (8 items), How to use (4 steps), Pricing plans
  • No JavaScript-only rendering; static HTML

Domain lazri.net is verified in Google Search Console (Domain property).

Similar patterns from other developers

The same rejection loop is currently being reported by 10+ developers in this forum (Cloud Foundations & Onboarding), all within the past 2 days. Examples:

  • “OAuth branding verification: both findings are factually incorrect on the live homepage (project byg-platform-(PII Removed by Staff))”
  • “Brand verification: name mismatch flag persists though consent screen and homepage match (PII Removed by Staff))”
  • “OAuth branding verification still shows app-name mismatch after fixes”
  • “OAuth brand verification stuck in instant-rejection loop — findings provably false, checker appears to not refetch”
  • “Verification Center stuck: ‘Prepare for verification’ disabled (project realtyworld-crm)”
  • “OAuth verification stuck on Homepage requirements, no Trust & Safety email after 10+ days”

All meet documented requirements; all stuck in the same automated rejection with no Trust & Safety email received. This strongly suggests a systematic issue with the automated verification checker.

Interesting comparison

Another add-on I own (Invoice Auto-Generator for Google Sheets, same GCP org, same developer) was verified successfully in 2026-05 with a much simpler homepage. No public documentation changes between then and now that I can find.

Request

Please have the Trust & Safety team manually review this project. I’ve tried multiple homepage HTML structures (OGP tags, meta descriptions, verified Search Console domains, purpose explanation paragraphs) without any change in the automated rejection response.

Thank you.

1 Like