← Back
Social Connect / Configuration / Google Login Setup

Google Login Setup

Last updated: February 12, 2026

This page is where you enable Google login and connect Social Connect to a Google Cloud OAuth app (Client ID + Client Secret).

Path: WP Admin → Social Connect → Networks → Google

1) Enable Google Social Login

Use the Google Social Login toggle at the top:

  • ON = Google login can work (if buttons are enabled in Social Connect settings + keys are valid)
  • OFF = Google login is disabled everywhere

2) Create a Google OAuth app and get your keys

The “How to get your Google App keys” box walks you through Google Cloud Console. Here’s the clean version of what matters:

A) Create a project (Google Cloud Console)

  • Open Google Cloud Console (the doc calls it “API Manager”)
  • Create/select a Project

B) Configure OAuth consent screen (required)

When you create OAuth credentials, Google forces you to configure:

  • App name
  • Support email / contact email
  • User type (usually External for public websites)

For testing, you can keep it minimal. For production, Google may require more details depending on your setup.

C) Create OAuth credentials (Web application)

Create an OAuth Client ID and choose Web application.

You must add both:

Authorized JavaScript origins

This is your site’s base URL, like:

  • https://yourdomain.com

Authorized redirect URI (critical)

This must match the plugin’s callback URL exactly.

  • https://yoursite.com/socplug/auth?provider=Google

If the redirect URI is wrong, Google login will fail every time.

Rules:

  • Exact match required
  • Add both staging and live domains if you use them
  • If you switch http ↔ https or change domain, update this in Google Cloud

D) Enable required API access

Your doc mentions enabling “Google+ API” to allow email access. Google has changed naming over time, but the practical requirement is:

  • Ensure your OAuth consent screen includes scopes that allow retrieving the user’s email (commonly email + profile).

3) Paste the keys into Social Connect

In Your Google App Settings, fill:

  • Client ID = OAuth Client ID
  • Client Secret = OAuth Client Secret

Then save.

As with Facebook: treat the Client Secret like a password.

4) Publish vs testing (why it works only for you)

Google OAuth commonly works in these modes:

  • Testing: only “test users” you add inside the consent screen can authenticate.
  • In production: anyone can authenticate.

So if Google login works for you but not for customers, check the OAuth consent screen status and test-user list.

Common issues (fast troubleshooting)

  • redirect_uri_mismatch → Redirect URI in Google Cloud doesn’t exactly match .../socplug/auth?provider=Google
  • Works for admins only → app still in Testing + your customers aren’t added as test users
  • No email returned / accounts duplicated → ensure the consent screen + scopes allow email access