Hi, my OAuth branding verification for my project has been flagged with: “The app name shown on your OAuth consent screen does not match the app name on your homepage.”
Project number: (PII Removed by Staff)
App name in the console: omotto
Homepage: (URL Removed by Staff)
I have been through several rounds of this. I think I have now found and fixed the actual cause, but I cannot get a re-review or any correspondence, so I am posting here.
For anyone who hits the same thing: our logo is a wordmark where the three o’s in “omotto” are not text glyphs. They are circles drawn with CSS borders on empty span elements. It reads as the word omotto to a person, but the header’s text content was literally “m tt”. The name was in the page title, in the (URL Removed by Staff) Organization name, in the first sentence of the copy and in the footer, so every check I ran told me the name was present. The one place it was missing was the header, which based on another thread here seems to be what the check actually reads.
That is now fixed. The o characters sit inside the rings in the markup, so the header text reads “omotto”. It is live on both locales and I have confirmed it in the served HTML rather than just locally.
Two things I can confirm in case they rule something out:
Googlebot is fetching the page successfully at verification time. I enabled access logging at the origin, and during a verification run I can see requests from 66.249.83.x and 66.249.93.x hitting the exact homepage URL with HTTP 200, plus a fetch of the privacy policy. So this is not a fetch or robots problem, and the content served at that moment did contain the app name.
I have never received an email from Trust and Safety about any of these attempts (checked spam of course). The console shows the findings but there is no message thread I can reply to.
Could someone either trigger a re-review, or tell me which address the reply email should have gone to so I can check the right inbox? Happy to provide anything else useful.
Thanks,
Oded