Hello,
I am the owner of a Google Cloud project for the app Unelma Task (PII Removed by Staff).
Our OAuth branding verification has been stuck for several days on two automated checks that keep failing on every resubmission, even though the underlying issues have been fixed:
- “Your home page does not explain the purpose of your app.”
- “The app name configured for your OAuth consent screen does not match the app name on your home page.”
Current state of the home page — (URL Removed by Staff) (server-side rendered, publicly accessible, no login required, returns HTTP 200 for any user agent, robots.txt allows all crawling):
- The first paragraph of visible content states the app name and purpose together: “Unelma Task is the internal project management platform of Unelma Technology: tasks, client requests, meeting recordings and call scheduling in one calm workspace.”
- A dedicated section “What is Unelma Task” describes the application’s functionality in plain text.
- A section “How Unelma Task uses Google user data” explains our use of Google Calendar data and links to the privacy policy at (URL Removed by Staff) (the same URL as configured on the consent screen).
- The app name “Unelma Task” is identical across every machine-readable field: , , application-name, og:title, og:site_name, apple-mobile-web-app-title, the web app manifest (name and short_name) and schema.org SoftwareApplication JSON-LD.
- The OAuth consent screen app name is set to exactly “Unelma Task” — a byte-for-byte match with the home page.
- The domain is verified in Google Search Console under this same account.
- Other checks (logo, privacy policy, domain ownership) have already passed; the two flags above are the only remaining ones.
We have resubmitted several times and the same two flags return each time, which suggests the automated check may be evaluating a cached copy of the page from before our fixes.
The Verification Center instructs us to reply to the email thread from the Trust & Safety team, but we have never received any email from api-oauth-dev@google.com. We checked Inbox, Spam, Promotions and Trash for both the developer contact and the support email address, so there is no thread we can reply to. We have also written to api-oauth-dev@google.com directly and received no response so far.
Could someone from the Google team please trigger a manual re-review of the current version of (URL Removed by Staff) against the branding checks, or advise how to escalate when no Trust & Safety email thread exists?
Thank you.