Why Google shows the wrong name on your sign-in screen
Published · Last updated
In our experience as of October 2026, Google's branding review looks at four things on your own site: your home page, your privacy page, the domains tied to your sign-in, and the stated purpose of your app. If the consent screen shows a platform's name or domain instead of yours, one of those four is usually the reason.
What you see
When someone clicks Sign in with Google, the consent screen says "to continue to" followed by a name. If your app uses a sign-in client that your platform provides, that name and the domain behind it can belong to the platform, not to you. Visitors then see a brand they never chose to trust.
Why it happens
The consent screen belongs to the Google sign-in client your app uses. A client of your own, with your own name, logo and links, is what puts your brand there. Until Google verifies that branding, it can show other details, such as the domain your sign-in redirects through.
What Google looks at
- A home page that loads for a visitor who is not signed in and says why your app uses Google sign-in.
- A privacy page that explains how you use Google user data.
- Domains on your sign-in that you own and can prove you own.
- A plain statement of what your app is for.
What this does not tell you
Which client setup fits your platform, which domains and redirects to register, and how to make the change without locking out the people who already sign in. A wrong edit to a working sign-in can break it for everyone.