Set up your own Google access

For rankion.ai to read your data from Google Search Console, Google Analytics 4 and your Google Business Profile, your team needs its own Google access: an OAuth client in your Google Cloud project. You create it once and enter two values in rankion.ai, the client ID and the client secret. From then on every connection of your team runs through your own Google project.

Only owners and administrators of your team can set up the access. All other members can see whether one is stored.

Before you start

Open the Google integration page in rankion.ai (/integrations/google). At the top you will find the section Your team's Google access with two authorised redirect URIs:

Always take the addresses from that page, using the Copy button. Google compares them character by character; a missing or extra slash at the end leads to "Error 400: redirect_uri_mismatch".

Step 1: Create a Google Cloud project

1. Open the Google Cloud Console and sign in with the Google account that owns your Search Console and Analytics.
2. In the project picker at the top choose New project, give it a name (for example "rankion") and create it.
3. Make sure the new project is selected at the top before you continue.

Step 2: Enable the APIs

Under APIs & Services → Library search for each of the following APIs and click Enable:

• Google Search Console API
• Google Analytics Data API
• Google Analytics Admin API

Only if you want to fetch reviews from your Business Profile, also:

• My Business Account Management API
• My Business Business Information API
• Google My Business API

Google only unlocks the Business Profile APIs after an access request. You submit it through the form Google links in the Business Profile APIs documentation.

Step 3: Configure the consent screen

1. Open APIs & Services → OAuth consent screen (newer consoles call this area Google Auth Platform).
2. Choose External as the audience. If your Google account belongs to a Google Workspace organisation and only people from it use rankion.ai, Internal is enough.
3. Enter an app name, your support email address and a contact address.
4. Under Data access (or Scopes) add these scopes: .../auth/webmasters.readonly, .../auth/analytics.readonly and, for reviews only, .../auth/business.manage.
5. Set the publishing status of the app to In production. In the Testing status only listed test users can sign in, and Google lets the authorisation expire after seven days. The connection in rankion.ai then stops working.

For the read scopes Google may require a verification of an external app. Until it is complete, Google shows a notice "This app isn't verified" when connecting; via Advanced you can still continue for your own account.

Step 4: Create the OAuth client

1. Open APIs & Services → Credentials (or Google Auth Platform → Clients).
2. Choose Create credentials → OAuth client ID.
3. Application type: Web application. The name is up to you.
4. Under Authorised redirect URIs enter both addresses from rankion.ai, each on its own line.
5. Save. Google now shows you the client ID (ends in .apps.googleusercontent.com) and the client secret (usually starts with GOCSPX-).

Step 5: Enter the values in rankion.ai

1. Back on Google integration in rankion.ai: enter the client ID and the client secret in the section Your team's Google access.
2. Click Save access. The status changes to Own access active.
3. Now click Connect with Google. From here the sign-in runs through your Google project.

The client secret is stored encrypted and never shown again, not even in part. To keep the client ID and renew the secret, enter the new secret. If you leave the field empty, the stored secret is kept.

What happens to existing connections

• Connections your team made before the own access keep working unchanged.
• If you enter a new client ID or remove the access, connections that ran through the old access must be reconnected. Google binds every authorisation to exactly the client it was granted through. Such connections then show as "expired"; clicking Additional account with the same Google account restores them.

Common errors

Related: Getting started · API: Google Integrations API (GET /v1/google/oauth-client shows the state, without the secret).