Used worldwide. Most users already have a Google account, so this is the highest-converting social login outside Korea.
Go to console.cloud.google.com and sign in with your Google account. If this is your first time, accept the terms.
Click the project dropdown at the top, then "New Project". Name it something like "MyApp Auth". This name is only visible to you.
In the left sidebar, go to "APIs & Services" → "OAuth consent screen". Choose "External" (so anyone with a Google account can sign in), fill in your app name, support email, and developer contact. You can leave scopes empty for now.
Go to "APIs & Services" → "Credentials" → "Create Credentials" → "OAuth client ID". Choose "Web application".
Under "Authorized redirect URIs", paste your DontCode redirect URL (https://<your-deployed-domain>/api/auth/oauth/callback). Click Create.
Google shows you a Client ID and a Client Secret. Copy both. DontCode needs the Client ID to start sign-in (it ends in .apps.googleusercontent.com) and the Client Secret to securely complete sign-in on the server. Treat the secret like a password.
Back in your DontCode project, go to Auth → Social Login → Google, paste both the Client ID and the Client Secret, click Save, then redeploy your app.
Also check the troubleshooting section on the main guide for issues that apply to all providers.
During development, Google shows this warning to users outside your test list. You can either submit your app for verification (takes a few days) or add testers under "OAuth consent screen" → "Test users" while you finalize the UX.
You need to add the new domain to "Authorized redirect URIs" in the same OAuth client. Multiple URIs are allowed. Register every variant you might use (custom domain + dontcode.cafe subdomain).