verapli
Sign inJoin free
Menu

Guides · analytics · Popular APIs

Google Search Console API

Enable the Search Console API, authorise with OAuth 2.0 using the webmasters or webmasters.readonly scope, and read Search Analytics / URL inspection data for properties the user can access.

Researched · not yet run liveLast researched 25 October 2026 · Google · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Google Cloud project holds the OAuth client; data access follows the signed-in user's Search Console property permissions.

  • Google Cloud project project
  • Search Console property otherThe authorising user (or service account) must have access to the property [to verify for service accounts].

Have ready

  • A Google Cloud project you own
  • A verified Search Console property
  • google/oauth-verification: For public External apps if the console marks the webmasters scopes as sensitive [to verify tier].

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Enable the Google Search Console API

    In your project's API Library, enable "Google Search Console API".

    • verapli co-pilot
    • Human step: You press submit

    Where: https://console.cloud.google.com/apis/library/searchconsole.googleapis.com

  2. Create an OAuth client ID

    Under Google Auth platform > Clients create a client with your redirect URIs and copy the ID and secret.

    • verapli co-pilot
    • Human step: You press submit
    • After: Configure the consent screen and scopes

    verapli captures GOOGLE_OAUTH_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://console.cloud.google.com/auth/clients

  3. Verify the OAuth app (public apps only)optional

    For External production apps whose scopes the console lists as sensitive, submit for verification.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Create an OAuth client ID
    The provider says
    Sensitive scope verification typically takes 3-5 business days. [3]

    Where: https://console.cloud.google.com/auth/verification

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Worth knowingThe rules say

URL inspection is limited to 2,000 queries per day per site. [2]

What you end up with

Env varSecretFormatWhat it is
GOOGLE_OAUTH_CLIENT_IDnot secret123456789012-abc….apps.googleusercontent.comOAuth 2.0 client ID
GOOGLE_OAUTH_CLIENT_SECRETsecretGOCSPX-…OAuth 2.0 client secret

Pricing

  • The usage limits page links to a separate pricing page; no charge found [to verify].

Source [2]

For agents

The same entry as JSON: /api/v1/entries/google/search-console-api · requirements /api/v1/requirements/google/search-console-api · terms /api/v1/terms/google/search-console-api.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Google Search Console API, and how long will it take?"
  → tools/call requirements { "provider_id": "google/search-console-api" }

Sources

  1. Authorize Requests Requests must use OAuth 2.0 by an authenticated user; scopes webmasters (read/write) and webmasters.readonly; register app in API Console for client ID/secret and activate the API; service accounts possible; Testing Tools API uses an API key for public data. · accessed 25 October 2026 · official
  2. Usage Limits | Search Console API Search Analytics 1,200 QPM per site and per user, 40,000 QPM and 30,000,000 QPD per project; URL inspection 600 QPM and 2,000 QPD per site; other resources 20 QPS / 200 QPM per user. · accessed 25 October 2026 · official
  3. Sensitive scope verification Public apps requesting sensitive scopes need verification; exemptions; typically 3-5 business days. · accessed 25 October 2026 · official
  4. Configure the OAuth consent screen and choose scopes Consent screen configuration steps. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Google is not affiliated with verapli.