Hi,
I’m a solo developer preparing a calendar app for sensitive-scope verification. Branding verification has failed repeatedly with findings that do not reflect the live state of my homepage, and I have never received the Trust & Safety email that the console tells me to reply to.
Findings returned
- “The app name shown on your OAuth consent screen does not match the app name on your homepage.”
- “Your homepage does not explain the purpose of your app.”
A third finding about domain ownership disappeared after I verified the domain in Search Console, so that part of the checker clearly does work.
What I have already verified
- The app name on the consent screen and the title / h1 of the homepage are byte-identical. I compared the code points, not just the rendering.
- The homepage opens with a plain sentence stating what the app does, followed by a section listing exactly which Google Calendar scopes are used, what each one is used for, and what the data is not used for. Both Japanese and English.
- I used Search Console’s URL Inspection Live Test to confirm that Googlebot renders the page with the correct name and description. This is not a stale-index problem and not a client-side-rendering problem.
- I ran a control experiment: I replaced the app name and the homepage heading with the same pure-ASCII string on both sides simultaneously, then re-ran the check. The same two findings came back. That rules out a non-Latin-script or translation-mismatch explanation.
- Re-running the check returns the identical findings within seconds, which does not look like the result of a human review.
What I am unable to do
- No Trust & Safety email has ever arrived. I have checked spam and every filter.
- The console instructs me to reply to that email, but there is nothing to reply to.
- I have no support entitlement, so I cannot open a technical support case.
- Under “Data access status”, “Prepare for verification” is greyed out because branding has to pass first. So I am blocked from even requesting sensitive-scope verification.
Why I am posting
There are now well over a dozen threads in this category describing the identical symptom, none of which has a staff reply. A few examples: 381451, 385235, 385255, 386539, 388520, 388916, 389656, 389923, 390155, 390699, 391542, 394540.
Two posters have reported that their case was approved a few days after posting here, without any explanation of what changed.
If a community manager can trigger a re-review, or point me to a channel where I can confirm the fix, I would be very grateful.
I am deliberately not posting project identifiers or contact details here, because an earlier post of mine was removed for that reason. I am happy to provide the project number and consent-screen details privately to a staff member on request.
Thanks.