The rejection: The app name does not match the branding on your website

App name does not match on the Google OAuth consent screen

Google cross-checks the name on your consent screen against the name on your public homepage. If they differ — even slightly — that's a rejection, and it's an easy one to fix.

01 — Why this happens

Reviewers verify that the app requesting access is the app your site presents. A consent screen that says 'My Project' while the site says 'Acme Scheduler', a leftover default project name, or a rename on one surface but not the other all read as a branding mismatch. It compounds because any branding change after you submit silently restarts the review.

02 — What Google says

Each fix below traces to a requirement Google publishes.

Nothing here is our opinion. Every requirement links to Google’s own page — open it and verify the fix yourself before you resubmit.

The app name on your OAuth consent screen must match your public site/app name — a name mismatch is one of the most common rejection triggers.

Google requirement · R18Read it on Google’s docs

The app name shown on your homepage must match the app under review.

Google requirement · R7Read it on Google’s docs

Your Google sign-in button must follow the official 'Sign in with Google' branding guidelines — approved assets and wording ('Sign in with Google' / 'Continue with Google').

Google requirement · R10Read it on Google’s docs

After you submit, changing the app name, logo, homepage, policy URL, or authorized domains restarts the review — freeze branding until you're approved.

Google requirement · R4Read it on Google’s docs
03 — The fix

Do these in order.

  1. 01

    Pick one exact app name

    Choose the precise name (including capitalization) you want reviewed, and make it the name on your homepage.

  2. 02

    Set the identical name on the consent screen

    In the OAuth consent screen, set the app name to exactly that string — no 'Project 12345', no old name, no variant.

  3. 03

    Align the sign-in button wording

    Use the approved 'Sign in with Google' / 'Continue with Google' wording and official button assets, so branding is consistent end to end.

  4. 04

    Freeze branding until approved

    Once submitted, don't touch the name, logo, homepage, or authorized domains — a mid-review change resets the process and costs you a cycle.

Check it before you resubmit

See exactly what Google’s crawler sees — free.

Paste your URL and scopes. The pre-check fetches your homepage the way Google does, finds your privacy-policy link, and flags the blockers this rejection is about — in seconds, no signup.

Questions

Straight answers.

How exact does the name match need to be?

Treat it as exact — same words, same capitalization — between the consent screen and your homepage. Small differences are enough to trigger a mismatch rejection.

Can I fix branding while my app is under review?

Fix it before you submit. Changing the name, logo, homepage, or authorized domains during review restarts the whole verification.