SocialMati
SEO & AnalyticsOAuth 2.0 (Google)Pricing verified 2026-10-06

Google Search Console

Search performance data — queries, pages, clicks, impressions, CTR and average position — for SEO opportunities, decay and anomaly alerts.

AProvider definition

Provider
Google Search Console
What it does
Search performance data — queries, pages, clicks, impressions, CTR and average position — for SEO opportunities, decay and anomaly alerts.
Why we need it
Search performance data — queries, pages, clicks, impressions, CTR and average position — for SEO opportunities, decay and anomaly alerts.
Used in
SEO → Search Console · SEO opportunities & reports · Advanced SEO

BAccount requirements

Account type
Google account with access to a verified Search Console property
Prerequisites
  • Google OAuth client
  • Search Console API enabled
  • Property verified (domain or URL-prefix)

CConnection method

Authentication
OAuth 2.0 (Google)
Credentials
Uses the Google OAuth client (Google Cloud Console) credentials — no separate key.
Where to enter it
  • Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
  • Per brand: App → Integrations → Connected accountsAnyone who manages the brand. Each brand connects its own accounts.

Setup steps

  1. 1Verify your site in search.google.com/search-console (DNS for a Domain property is recommended).
  2. 2Enable “Google Search Console API” in the Cloud project and add the scope below to the consent screen.
  3. 3SEO → SEO settings → Integrations & CMS → Connect Search Console and pick the property.

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
openidSign the user in with OpenID Connect.Google sign-in for this product
emailShow which account is connected.Google sign-in for this product
https://www.googleapis.com/auth/webmasters.readonlyRead search analytics, sitemaps and property list. Read-only — nothing is changed in Search Console.Google sign-in for this product

This list is generated from the scopes the application's code requests.

EFree vs paid

Free account / free API access
Yes.
Card or billing account required?
No.
Paid plan / costs
No subscription.
Quota and usage limits
1,200 queries per minute per site and per user; up to 50,000 page-query rows per property per day per search type; URL Inspection 2,000 per day per property.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.

FSetup screenshots

Capture each step with real values masked. Save images as public/docs/integrations/search_console/1.png … 10.png and they appear here automatically.

  1. Screenshot to add
    1. Account login / creation
    The provider's sign-in or sign-up page.
  2. Screenshot to add
    2. Developer console
    The developer console or dashboard home.
  3. Screenshot to add
    3. Project / app creation
    Creating the app or project used for this integration.
  4. Screenshot to add
    4. API enablement
    The API or product enabled for the project.
  5. Screenshot to add
    5. OAuth configuration
    Consent screen / OAuth settings with the redirect URIs.
  6. Screenshot to add
    6. API key / credentials creation
    Creating the key, secret or token (mask the value).
  7. Screenshot to add
    7. Permissions / scopes
    The scopes or permissions requested or approved.
  8. Screenshot to add
    8. Billing / quota settings
    Billing, credits or quota page.
  9. Screenshot to add
    9. Application connection
    The provider card in our application with fields filled (secrets masked).
  10. Screenshot to add
    10. Successful connection
    The green Test result or the connected account listed.

GApplication configuration

Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.

Nothing to enter for this product — it uses the Google OAuth client (Google Cloud Console) credentials. Connect it from the location in section C.

HTesting

  1. 1Connect the property; SEO → Search Console should show the last 28 days of clicks and impressions.

ITroubleshooting

ProblemWhat to do
No properties listedThe Google account has no access to a verified property — add the user in Search Console → Settings → Users and permissions.
Empty dataNew properties need a few days of data; Search Console data lags 2–3 days.
Invalid credentialsCheck the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure.
Missing permissionsReconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved).
OAuth failureSign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app.
Redirect URI mismatchCopy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings.
API not enabledEnable the API/product for the project or app in the provider console and wait a few minutes.
Quota exceededWait for the quota window to reset (see section E) or request a higher quota / add credits.
Account not eligibleCheck the account requirements in section B (e.g. business/professional account, verified property, registered organisation).
App review requiredPermissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions.
Billing requiredAdd a payment method or prepaid credits on the provider account (see section E).

JDisconnect & security

Revoke access at the provider
Remove the app in Google account → Third-party apps, or disconnect in SEO settings.
Disconnect in the application
App → Integrations → Providers & API keys or App → Integrations → Connected accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
Rotate credentials
Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
How credentials are stored
Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
What data the application can access
Read-only search performance and sitemap data for properties you select.

Other SEO & Analytics providers

Start Free