Prompt

What redirect URI should I use for Google login in development and production?

Technology / Identity & Access1 observationLast seen Oct 6, 2026

Latest observation

Oct 6, 2026OpenAI APIWeb search: off

For Google OAuth login, the redirect URI must exactly match what’s registered in Google Cloud Console.

Common setup

Development

Use a local callback URL, for example:

  • http://localhost:3000/auth/google/callback
  • or http://localhost:5173/auth/google/callback
  • or whatever your local app route is

Production

Use your real public domain, for example:

  • https://yourdomain.com/auth/google/callback

Important rules

  • The redirect URI must match exactly:
    • scheme: http vs https
    • domain
    • port
    • path
  • If you use multiple environments, register each redirect URI in Google Cloud Console.
  • If your app uses a backend API for the callback, the redirect URI should point there, not to the frontend.

Typical examples

If your app handles the OAuth callback in the backend:

  • Dev: http://localhost:4000/auth/google/callback
  • Prod: https://api.yourdomain.com/auth/google/callback

If the frontend handles the callback route:

  • Dev: http://localhost:3000/auth/google/callback
  • Prod: https://yourdomain.com/auth/google/callback

Google Console

In Google Cloud Console → APIs & Services → Credentials → OAuth 2.0 Client ID, add both:

  • your development redirect URI
  • your production redirect URI

If you tell me your stack (e.g. React + Node/Express, Next.js, Laravel, etc.), I can suggest the exact redirect URI format.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as Circuit. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.