Skip to content
Request access

Guide

Show your store’s name on Google’s consent screen

When a shopper clicks Sign in with Google, Google shows a small page that says who is asking: “Choose an account to continue to …”. Out of the box that name is Store Social Login, the app that runs your sign-in; Google has verified its branding. If you would rather it said your store's name, with your logo and your privacy policy, follow the steps below. Nothing about how sign-in works changes; only what Google shows.

You will need about 30 minutes of your own time (plus waiting for DNS, usually minutes and sometimes an hour, and for Google’s brand check, which takes minutes or two to three working days), access to your domain's DNS settings (where you manage your website address), and a Google account. Google's parts are free. Every value you have to type is shown, with a Copy button, on the Google branding card on the Google page under Sign-in methods.

Before you start

  • Your store's own domain, for example shop.example. Google only shows a name for a website it can see you own, so this does not work on a mybigcommerce.com address.
  • A privacy policy page on your store. Google requires it to say that signing in with Google shares the shopper's name and email address with your store. A short paragraph on what you do with the shopper’s name and email is usually enough, but Google decides.
  • A square logo, 120 × 120 pixels, PNG or JPG, under 1 MB. Optional; it shows after Google has checked your details (step 6).

Step 1: Add one DNS record for your sign-in address5 minutes

Google names the website it sends shoppers back to. The app gives that website a name under your own domain, such as login.shop.example, and sets it up by itself. One DNS record at your domain host makes the name yours.

  1. In the app, open Sign-in methods, then Google. If no sign-in method is switched on yet, switch Google on for the sign-in page first: that is how the app learns your storefront address. The Google branding card's step 1 then shows your sign-in address and the record to add: type CNAME, name login, value cname.vercel-dns.com. Occasionally a second, TXT record is shown as well; add both.
  2. Add the record wherever your domain's DNS is managed. If BigCommerce hosts your DNS (common: your domain's name servers are ns1.bigcommerce.com and so on), that is in the control panel under Settings › Email & DNS records › Web Hosts: add a row, type CNAME, host login.shop.example, value cname.vercel-dns.com, then Save. Otherwise it is at your registrar or DNS provider (GoDaddy, Cloudflare, Namecheap, your web host). If you are not sure where, whoever set up your website will know.
  3. Leave the app open. It checks every half minute and marks the address connected as soon as the record is seen, usually within minutes, sometimes up to an hour; Check now asks straight away. A connected address is also secure: the certificate is issued automatically.

Step 2: Tell Google you own your domain5 minutes

  1. Open Google Search Console, opens in a new tab and sign in with the Google account you will use for the rest of this guide.
  2. Click Add property, choose Domain, enter your store domain without www (the “Authorised domain” value on the card), and click Continue.
  3. Google shows a TXT record. Add it to your DNS the same way as in step 1 (in BigCommerce: another Web Hosts row, type TXT, host your bare domain), then click Verify. Having the domain in Google Workspace for email does not count here; Search Console needs its own record. Google's own walkthrough: Verify your site ownership, opens in a new tab.

Step 3: Create your Google project10 minutes

  1. Open the Google Cloud console, opens in a new tab. If it asks you to accept terms, do so. Create a new project; call it your store name.
  2. Open Google Auth Platform › Overview, opens in a new tab and click Get started. Fill in: App name (your store's name, exactly as shoppers should see it), User support email, Audience External, and a contact email. Agree to the policy and click Create. The support email list only offers your own Google address and Google Groups you own; a plain mailbox such as help@shop.example appears only once it is a Google Group with you as owner.
  3. Open Branding, opens in a new tab and add your logo, your store's home page (the “Application home page” value on the card), your privacy policy page, your terms page if you have one, and under Authorised domains your store domain (the “Authorised domain” value). Save.
  4. Open Audience, opens in a new tab and click Publish app. Until you do, only people you list as testers can sign in.

Step 4: Create the sign-in credentials5 minutes

  1. Open Clients, opens in a new tab and click Create client.
  2. Application type Web application; name it anything.
  3. Under Authorised redirect URIs (the second list, not “JavaScript origins”) click Add URI once and paste the “Authorised redirect URI” value from the card. It must match exactly, so use the Copy button, and keep it to one row: Google refuses the form if the same address appears twice.
  4. Click Create. Google shows a Client ID (it ends in .apps.googleusercontent.com) and a Client secret. Keep this window open: the secret is shown only this once. If you close it too soon, open the client from the Clients list and use Add secret to get a new one, then disable the old one there so the client has a single secret.

Step 5: Connect it to the app and test2 minutes

  1. In the card's step 2, paste the Client ID and Client secret and click Save. The secret is stored encrypted and never shown again.
  2. In step 3, click Test sign-in. A new tab opens; sign in with any Google account. Google's page should now show your sign-in address (for example login.shop.example), and then the app says “Your Google client works”. Your store's name follows once Google has verified your brand (step 6). Nothing is created on your store by this test.
  3. Back in the app the badge reads Your Google · in use. From now on shoppers sign in through your own Google.

If the test says Google refused your client, the usual causes are the redirect URI not matching exactly (step 4.3), or the app still being unpublished (step 3.4). Fix it in Google, then test again. Shoppers are not affected while you do: they stay on the app's Google until a test succeeds.

Step 6: Get your name and logo shown

Google shows your store’s name and logo only after it has checked your branding; until then it shows your sign-in address. Open Branding, opens in a new tab and click Verify branding (or open the Verification Center, opens in a new tab). Google checks automatically within minutes; if a person needs to look it takes two to three working days and you get an email. The common reasons for a “no” are a privacy page that does not mention Google data, or a home page that does not describe your store. Google's full write-up: Brand verification, opens in a new tab.

Undoing it

Click Remove credentials on the card at any time. Shoppers go back to signing in through Store Social Login straight away; your Google project and your sign-in address can stay as they are, or be removed with the address's own Remove.