OAuth consent screen rejects "localhoston.com" — false positive localhost detection

Google Cloud Cloud Foundations & Onboarding
1

When adding “localhoston.com” as an authorized domain in the OAuth consent screen branding page, I get this error:

“Invalid URL: localhost domains cannot be included.”

This is a false positive. My domain is “localhoston.com”, NOT “localhost”. The validation incorrectly matches “localhost” as a substring within “localhoston”.

Steps to reproduce:
1. Go to Google Cloud Console > APIs & Credentials > OAuth consent screen > Branding
2. Enter my domain in the Application Homepage URL field
3. Error: “Invalid URL: localhost domains cannot be included.”
Same error for all three fields: Homepage, Privacy Policy, Terms

The domain is registered, verified in Google Search Console, and hosted on Vercel.

Is there a way to resolve this or get the domain whitelisted?

2

Hi Jongjin,

Yeah, that does look like a validation issue where it’s picking up “localhost” inside your domain.

You could try a couple of things just in case:

  1. Make sure the domain is added under Authorized domains in the OAuth consent screen
  2. Try entering the full URL with https (like https://localhoston.com)
  3. Maybe test with/without www and see if it behaves differently

If it still throws the same error, it honestly looks like a validation bug rather than something wrong on your side. In that case, raising it via the issue tracker or support might be the only way.

3

Thanks for confirming it’s a validation bug.

I tried all variations (https, with/without www) — same error since “localhost” is always a substring of “localhoston”.

I attempted to file via Issue Tracker but don’t have permission to create issues. Is there another way to escalate this to the Google team? Or could someone with access file it on behalf?

Thanks.