Project ID: (PII Removed by Staff)
OAuth branding verification returns the same two findings on every attempt, instantly, with no email ever sent:
- “Your home page does not explain the purpose of your app.”
- “The app name ‘ContentLynx’ configured for your OAuth consent screen does not match the app name on your home page.”
My homepage (https://contentlynx.app) is a full landing page titled “ContentLynx — The YouTube Production OS” that clearly explains the product and matches the consent-screen app name exactly (verified character-for-character, present in server-rendered HTML — title, h1, and meta). Domain ownership is verified in Search Console under the same account.
To rule out every possible cause on my end, I have tried, each returning the identical result:
- Added an explicit Google user-data disclosure to the homepage footer next to the privacy policy link.
- Pointed “Application home page” at a brand-new, never-before-crawled URL (
/about) with all required content server-rendered — confirmed live (HTTP 200). Failed identically. - Created a completely new Google Cloud project with a fresh consent screen pointing at the same verified homepage. Branding verification returned the identical two findings, instantly, with no email.
A brand-new project cannot have a stale cached verdict, and the homepage demonstrably meets both requirements. This strongly indicates a bug in the automated branding check. Could a Trust & Safety team member investigate?