Google Search Console API: how to automate SEO data (2026)

Manual CSV exports do not scale when you manage ten or twenty GSC properties. The Search Console API lets you pull clicks, impressions, and queries in code — as long as you accept OAuth, quotas, and the limits of what the API does not expose (Page indexing card totals, bulk indexing).

The Google Search Console API automates extraction of Search Analytics (queries, pages, device, country) and limited inspection endpoints. Use it for recurring reports and alerts; it does not replace SEO strategy or force indexing across dozens of URLs.

When to automate (and when to stay in the UI)

• Automate when you need the same data slice every week (top queries, pages with impressions and low CTR, 28 vs 28 day compare) across many clients.
• Stay in the UI for one-off checks, Rich Results, a single URL Inspection, or while you are still shaping the template from our Google Search Console reporting for agencies guide.
• Hybrid: API feeds your datastore; analysts interpret — the same pattern as multi-client GSC reporting in the product.

GSC UI vs Search Console API

If the main issue is «Crawled – currently not indexed», the API helps cross-check URLs with zero impressions — but the fix stays editorial. See Crawled – currently not indexed.

Google Cloud prerequisites

1. A Google Cloud project (billing enabled if you use other APIs; the Search Console API itself has no per-call fee).
2. Enable the Google Search Console API (searchconsole.googleapis.com).
3. OAuth 2.0 credentials as a Desktop app → download JSON (below: credentials.json).
4. A Google user with owner or full-user access to the target GSC property.

Recommended Python dependencies:

pip install google-auth-oauthlib google-auth-httplib2 google-api-python-client

Optional with the gcloud CLI:

gcloud services enable searchconsole.googleapis.com

Python script: OAuth + Search Analytics

The sample uses a readonly scope, secrets file credentials.json, and stores token.json for refresh. Set PROPERTY to a URL prefix (https://www.example.com/) or domain (sc-domain:example.com).

from google.oauth2.credentials import Credentials
from google_auth_oauthlib.flow import InstalledAppFlow
from google.auth.transport.requests import Request
from googleapiclient.discovery import build
import os.path

SCOPES = ['https://www.googleapis.com/auth/webmasters.readonly']
PROPERTY = 'https://www.example.com/'

def gsc_credentials():
    creds = None
    if os.path.exists('token.json'):
        creds = Credentials.from_authorized_user_file('token.json', SCOPES)
    if not creds or not creds.valid:
        if creds and creds.expired and creds.refresh_token:
            creds.refresh(Request())
        else:
            flow = InstalledAppFlow.from_client_secrets_file('credentials.json', SCOPES)
            creds = flow.run_local_server(port=0)
        with open('token.json', 'w', encoding='utf-8') as token:
            token.write(creds.to_json())
    return creds

def list_properties():
    service = build('searchconsole', 'v1', credentials=gsc_credentials())
    response = service.sites().list().execute()
    for entry in response.get('siteEntry', []):
        print(entry['siteUrl'], entry.get('permissionLevel'))

def query_page_report():
    service = build('searchconsole', 'v1', credentials=gsc_credentials())
    body = {
        'startDate': '2026-09-01',
        'endDate': '2026-09-30',
        'dimensions': ['query', 'page'],
        'rowLimit': 1000,
    }
    response = service.searchanalytics().query(siteUrl=PROPERTY, body=body).execute()
    for row in response.get('rows', []):
        query, page = row['keys']
        print(
            query,
            page,
            row.get('clicks', 0),
            row.get('impressions', 0),
            round(row.get('ctr', 0) * 100, 2),
            round(row.get('position', 0), 1),
        )

if __name__ == '__main__':
    list_properties()
    query_page_report()

On first run a browser opens for OAuth consent. Keep token.json out of git — treat it like a password.

From raw JSON to SEO actions

Typical agency pipeline after the query:

• Filter rows with impressions ≥ N and CTR below position benchmark → title/meta rewrite queue (see CTR in GSC: improve titles).
• Aggregate by page to spot cannibalisation or orphan URLs.
• Compare this week vs last in your warehouse — the API does not send email; that is your cron or SaaS layer.

Quotas, 403 errors, and URL Inspection

Search Analytics has per-request row limits and daily quotas per project. 403 quotaExceeded means backoff and cache — not scripts every minute. The URL Inspection API suits automated sampling (index status for priority URLs), not inspecting hundreds of legacy URLs in one day.

Indexing requests: after inspection the API may allow a one-off submission — there is no substitute for quality, sitemap, and internal links. Do not confuse data automation with «forcing» the index.

Multi-client: why local scripts break early

Each client needs OAuth consent, secure refresh token rotation, and data isolation per organisation — why tools like DENVORA SEO centralise GSC sync instead of sharing one token.json on Slack. For monthly delivery, pair API extraction with the GSC reporting for agencies workflow and Google Search Console reporting in the product.