Google One-Tap turns the Google sign-in button into a personalised one: a visitor already signed in to Google sees their own name and picture on it, and one click signs them in. No form, no password, no provider screen to pass through. It uses the same Google OAuth client as Login with Google, so set that up first.
Turning it on
Under Settings → Social Login → Google, turn on Google One-Tap. Nothing else is required; it uses your existing client ID.
Google serves it only over HTTPS, and a visitor with no Google session in the browser simply gets the ordinary button.
Where it appears
On wp-login.php and anywhere the Google social button is shown, including the
shortcode forms. Google draws its own button in place of the plain one, and
for a visitor already signed in to Google it carries their name and picture, so signing in is a
single click.
To load it on a page that has no Google button of its own, use the shortcode:
[fluent_auth_google_one_tap delay="2"]| Attribute | Default | Meaning |
|---|---|---|
type | inline | inline outputs a container for the Google button where the shortcode sits |
delay | 2 | Seconds to wait before loading, so it does not compete with the page |
Signed-in visitors see nothing.
Security
The token Google hands back is verified server-side against your client ID before any session is issued, so a forged token from the browser is rejected. The login then passes through the same checks as any other: second factor, IP rules and redirects. The audit log records it as a Google login.
Authorised origins
One-Tap needs your site’s origin listed under Authorized JavaScript origins on the Google
OAuth client, in addition to the redirect URI. Add https://example.com (no path, no trailing
slash). Without it the prompt renders but sign-in fails with an origin error in the browser
console.