Google Search Console OAuth 2.0 connector profile – StackOne setup guide

Sign in at the Google Cloud console with an account that has Owner or Editor access to the project you want to use.

Click the project name in the top bar to open the Select a resource dialog. Pick an existing project from the list, or click New project to create one. An existing project is fine — the only requirement is that you can administer it.

In the Google Cloud console, go to APIs & Services > Library and search for “Google Search Console API”, then open the result.

On the Google Search Console API product page, click Enable.

• If the API is already enabled on this project, the button shows Manage next to an API Enabled marker instead, and no action is needed.
• Enable the API before configuring scopes. The scope editor only lists scopes belonging to APIs that are already enabled.

In the Google Cloud console, go to APIs & Services > OAuth consent screen. This opens Google Auth Platform, whose sidebar contains Overview, Branding, Audience, Clients, Data Access, Verification Center and Settings.

• If the platform is already configured, Overview shows the OAuth Overview page with usage metrics — go straight to Branding.
• If it has not been configured yet, complete the getting-started flow that Overview presents, then return to Branding.

Open Branding and fill in the App information section.

• App name — the name shown on the consent screen when a user authorizes access (for example, StackOne Integration).
• User support email — the address users can contact with questions about their consent.
• Click Save at the bottom of the page.

Open Audience and check User type.

• Internal — only users in your Google Workspace organization can authorize the app, and no verification is required.
• Click Make external to allow any Google account to authorize it. External apps need verification before general production use.
• Google warns that OAuth access is restricted to users within your organization unless the OAuth consent screen is published and verified.

In Google Auth Platform, open Data Access and click Add or remove scopes. The page groups what you already have into Your non-sensitive scopes, Your sensitive scopes and Your restricted scopes.

In the Update selected scopes side panel, use Filter to find each scope by name, then tick it in the table. Every scope this connector’s actions need is listed below.

• The panel notes that only scopes for enabled APIs are listed — if no Search Console scopes appear, enable the API first and reload the page.
• https://www.googleapis.com/auth/webmasters.readonly covers the read actions (listing sites, sitemaps and search analytics).
• https://www.googleapis.com/auth/webmasters is additionally required by the write actions (adding and deleting sites and sitemaps, and URL inspection).

If a required scope does not appear in the table, use the Manually add scopes section at the bottom of the panel.

• Paste the full scope URL into the text box — one scope per line, or separated by commas.
• Click Add to table.

Persist the selection in two steps.

• Click Update to apply the selected scopes. The side panel closes.
• Back on Data Access, click Save.

Go to APIs & Services > Credentials, click + Create credentials, and choose OAuth client ID.

On Create OAuth client ID, set Application type to Web application.

Fill in the client details, then create it.

• Name — a label used only to identify the client in the console (for example, StackOne Search Console Integration). It is never shown to end users.
• Under Authorized redirect URIs, click + Add URI and enter StackOne’s callback URL exactly — https://api.stackone.com/connect/oauth2/googlesearchconsole/callback
• Leave Authorized JavaScript origins empty — StackOne calls the API from a server, not a browser.
• Click Create.
• Google notes that it may take 5 minutes to a few hours for settings to take effect, so a newly added redirect URI may not work immediately.

The OAuth client created dialog shows both values, each with a copy button. Copy them before closing it.

• Google warns that you will no longer be able to view or download the client secret once you close this dialog, so copy it or use Download JSON first.
• The Client ID stays available afterwards from the Clients page in Google Auth Platform.
• Click OK to close the dialog.

Skip this step if you created a new client above. To reuse a client you already have, open it from the Clients page.

• Under Authorized redirect URIs, click + Add URI, enter https://api.stackone.com/connect/oauth2/googlesearchconsole/callback, then click Save.
• Under Client secrets, click + Add secret to generate a new secret, and copy it — an existing secret is only ever shown truncated and cannot be retrieved in full.
• Your Client ID is shown on the same page under Additional information.

Paste each value into the matching field in the StackOne Connector profile.

• Client ID — the public identifier of your OAuth client, ending in .apps.googleusercontent.com. Copy it from the OAuth client created dialog, or later from Additional information on the client’s page.
• Client Secret — the private half of the credential pair, beginning with GOCSPX-. Copy it from the creation dialog, or generate a new one with + Add secret.
• Scopes — optional. Leave it empty to request https://www.googleapis.com/auth/webmasters, which covers every action in this connector. Set it to a space-separated list only when you want to narrow access — for example https://www.googleapis.com/auth/webmasters.readonly for read-only use.