Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

You can add Google sign-in to WordPress with a social-login plugin such as Nextend Social Login. Install and activate the plugin, configure its Google provider with a Google OAuth web application, and copy the exact redirect URI shown in the plugin into that OAuth client. Nextend documents automatic placement on the standard WordPress login form; other placements may require a shortcode, widget, PHP integration, or a supported paid integration.

What you need before setup

  • Administrator access to your WordPress site so you can install and configure a plugin.
  • A Google account to create and manage the OAuth project and web application.
  • The exact authorized redirect URI displayed in Nextend’s Google provider setup. Do not try to construct this address yourself.

Nextend’s [Google provider guide] and [getting-started guide] document this approach. It is one documented option, not a ranking of all WordPress social-login plugins.

Set up Google login with Nextend Social Login

  1. Install the plugin. In your WordPress dashboard, go to Plugins > Add New, search for Nextend Social Login, then install and activate it.
  2. Open the Google provider setup. In Nextend Social Login, select the Google provider and follow its setup instructions to create a Google project and OAuth web application. Choose the application audience and publishing settings that match who should be able to sign in. Google Console labels and workflows can change, so follow the current prompts in the console.
  3. Copy the redirect URI from Nextend. The plugin displays an authorized redirect URI for the Google OAuth client. Copy it exactly, including its scheme, domain, path, and any query string, and add it as an authorized redirect URI in the Google client. Nextend identifies a mismatch as a cause of the redirect_uri_mismatch error.
  4. Enter the OAuth credentials in WordPress. Copy the client ID and client secret from the intended Google project into the corresponding fields in Nextend’s Google provider settings, then use the plugin’s verification step.
  5. Test with an eligible account. Sign in using a Google account allowed by the app’s current audience and publishing state. Nextend’s provider guide notes that testing-mode access is limited and describes publishing for broader Google-account access. Review Google’s current requirements before changing the app’s publishing status.
  6. Check where the button appears. Nextend documents automatic placement on the standard WordPress login form in its free plugin. For other locations, use the plugin’s documented shortcode, widget, or PHP integration. Some integrations with third-party forms are documented as Pro features.

Choose the button’s placement

For the standard WordPress login page, the default placement may be all you need. If you want Google sign-in on another page or form, choose the appropriate integration and verify that it is supported by your plugin edition.

  • Custom page or layout: Nextend documents shortcode and widget options, as well as PHP integration, for adding the button outside the default login form.
  • Membership, commerce, or another plugin’s form: Check Nextend’s current integration documentation and edition requirements. The vendor identifies selected third-party form integrations as Pro features.

Nextend also documents an OAuth redirect URI proxy-page option. If you use it, select a page dedicated to this OAuth flow, then update the authorized redirect URI in every OAuth app configured for the affected provider. The proxy page handles authentication and should not be treated as an ordinary content page. See Nextend’s [global settings documentation] for its redirect and registration-flow options.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Review account flow, redirects, and privacy

Social login connects a Google identity to a WordPress account. Nextend’s plugin listing says users can connect a social account to an existing WordPress account; its provider documentation says social-profile data is retrieved and stored when a user registers, logs in, or links an account. Review what data your site receives and stores, and make sure your privacy information explains the feature appropriately.

Decide where users should go after logging in or registering. Nextend documents a setting to prevent external redirect overrides; consider the destination deliberately and test both login and registration. If your registration flow needs to show terms and conditions, the vendor documents a global setting and requires the selected page to contain the [nextend_social_login_register_flow] shortcode.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix common Google login problems

redirect_uri_mismatch

Compare the authorized redirect URI saved in the Google OAuth client with the current URI displayed in Nextend. They must match exactly, including scheme, domain, path, and query string. Recheck the value after changing your site URL, the /wp-login.php endpoint, or the OAuth proxy-page setting.

invalid_client

Nextend lists this error when the OAuth client cannot be found. Confirm that the client ID and secret belong to the intended Google project and that you entered them in the correct provider settings.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The button is missing from a custom form

First check whether you are viewing the standard WordPress login form or a form supplied by another plugin. Nextend documents automatic placement on the standard login form; custom locations use its shortcode, widget, or PHP options, while some third-party form integrations may require Pro.

Before enabling Google sign-in for everyone

  • Complete a test registration and a later sign-in using an account permitted by the app’s audience and publishing settings.
  • Confirm the button appears on the intended form and that login and registration send users to the expected destination.
  • Verify that the Google OAuth client still contains the exact redirect URI displayed by the plugin.
  • Review the profile data handling and update relevant privacy disclosures.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.