Hi, my OAuth branding verification for project (PII Removed by Staff) (app: Genify) has been flagged with: “The app name shown on your OAuth consent screen does not match the app name on your homepage.”
I fixed this on July 24, 2026 — the homepage title tag and header now both read “Genify” exactly matching the OAuth console app name field. I’ve double checked the live site and the fix is confirmed deployed.
The Verification Centre says: “Reply to your email thread with our Trust and Safety team after you have resolved the issues.” However, I have never received any email from a Trust & Safety team about this — I’ve searched my inbox (including spam) thoroughly and found nothing related to OAuth verification or branding review for this project.
Could someone help me either trigger a re-review, or point me to where this email should have been sent? Homepage: (URL Removed by Staff)
Thanks in advance.
I’m also dealing with this issue. Please let me know if you are able to find a resolution as I would really like to solve it for myself.
Update: Got verified — here’s what worked, in case it helps others stuck on this
For anyone landing here with the same issue (branding mismatch flag plus no email from Trust & Safety despite thorough inbox/spam checks), here’s what resolved it:
- Confirm the exact mismatch first. The flag is a literal string match between your OAuth consent screen’s app name field and your homepage. Check both your
<title> tag and your visible header/logo text. Google checks the rendered page, not just the title.
- Fix and redeploy, then verify it’s actually live. Don’t just push the change. Reload the live production URL yourself (ideally in an incognito window to rule out caching) and confirm the text matches character for character with the OAuth console.
- Don’t wait indefinitely for the Trust & Safety email if it never arrives. I checked spam thoroughly and had nothing. Rather than sitting in limbo, I posted here in the Developers forum with my project ID, what the original flag said, what I fixed and when, and a direct ask to either trigger a re-review or point me to where the reply email should have gone.
- Keep Project Owner/Editor accounts current in Cloud Console. The approval email specifically calls this out. Future verification comms depend on it.
- Re-verification isn’t optional if you touch the consent screen again. Any change to OAuth consent screen config or new scopes requires a fresh verification request. This one doesn’t carry over.
Got the approval from the Third Party Data Safety Team not long after posting here, so raising it in this forum seems to be the effective path when the email loop breaks. Hope this saves someone else the guessing.