Google Search Console API

Name: Google Search Console API API
Brand: Google Search Console API
Availability: InStock

✓ Official Vendor SpecMarketingSeo Semoauth211 EndpointsREST

For Agents

Pull Google Search performance data, inspect URL indexing status, and manage sitemaps for verified websites.

Quickstart

Get started with Google Search Console API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pull google search console performance data"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Search Console API API.

Query search analytics by query, page, country, device, and date with up to 16 months of history

Inspect a specific URL's indexing status, canonical, and rich result eligibility through the URL Inspection API

Run live mobile-friendly tests on any public URL and retrieve resource-level issues

List, add, and remove verified sites in a Search Console account

GET STARTED

Start building with Google Search Console API API

Explore with Jentic

View OpenAPI Document

Use for: Get the top 100 search queries driving clicks to my site last month, Check whether a specific URL is indexed by Google, List all sitemaps submitted for example.com, Submit a new sitemap.xml to Search Console

Not supported: Does not handle ad campaigns, on-site analytics, or content publishing — use for Search Console performance reporting, sitemap management, and URL indexing diagnostics only.

The Google Search Console API gives programmatic access to Search Console data for verified site owners and to public URL inspection tools. Agents can query search analytics dimensions like clicks, impressions, CTR, and average position, manage verified sites, submit and inspect sitemaps, and run live URL and mobile-friendly checks. Results mirror what site owners see in the Search Console UI and cover the rolling 16-month performance window.

Use Cases

Patterns agents use Google Search Console API API for, with concrete tasks.

★ SEO Performance Reporting

Pull daily search performance data into a BI tool or agent dashboard to track organic clicks, impressions, CTR, and average position by query, page, country, and device. The Search Console API exposes the same 16-month dataset visible in the UI but in raw, dimension-broken-down form, ready for joins against site analytics. Most reporting jobs run in under a minute per site once OAuth is set up.

Call POST /webmasters/v3/sites/{siteUrl}/searchAnalytics/query with dimensions [query, page] for the last 28 days and return the top 50 queries by clicks.

Sitemap Management Automation

Automate sitemap submission and monitoring across many properties. The API lets you list submitted sitemaps, add a new sitemap when content ships, remove stale ones, and read the last-processed timestamp plus any errors or warnings. This replaces manual UI work for agencies and platforms managing dozens of sites.

Call PUT /webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath} to submit https://example.com/sitemap.xml, then GET the same path to confirm processing.

URL Indexing Diagnostics

Diagnose why a specific URL is or is not in Google's index. The URL Inspection endpoint returns the indexing verdict, last crawl time, canonical chosen by Google, mobile usability, and rich result eligibility. Useful for content QA pipelines and editorial agents that flag pages with indexing issues before launch.

Call POST /v1/urlInspection/index:inspect with inspectionUrl=https://example.com/blog/post-123 and return the indexStatusResult.verdict and coverageState.

AI Agent SEO Audit Workflow

An AI agent runs end-to-end SEO audits across a portfolio of sites, combining search analytics, sitemap status, and per-URL inspection. Through Jentic the agent searches for the right operation, loads its schema, and executes calls without hand-coding OAuth flows. Useful for content teams that want a daily audit summary delivered to Slack.

For each verified site, call searchAnalytics:query plus sitemaps.list, then run urlInspection:index:inspect on the 10 newest URLs and produce a summary report.

Key Endpoints

11 endpoints — the google search console api gives programmatic access to search console data for verified site owners and to public url inspection tools.

METHOD

PATH

DESCRIPTION

POST

/webmasters/v3/sites/{siteUrl}/searchAnalytics/query

Query search performance by dimension

GET

/webmasters/v3/sites

List verified sites

PUT

/webmasters/v3/sites/{siteUrl}

Add a site to the account

GET

/webmasters/v3/sites/{siteUrl}/sitemaps

List submitted sitemaps

POST

/v1/urlInspection/index:inspect

Inspect a URL's index status

POST

/v1/urlTestingTools/mobileFriendlyTest:run

Run a live mobile-friendly test

POST

/webmasters/v3/sites/{siteUrl}/searchAnalytics/query

Query search performance by dimension

GET

/webmasters/v3/sites

List verified sites

PUT

/webmasters/v3/sites/{siteUrl}

Add a site to the account

GET

/webmasters/v3/sites/{siteUrl}/sitemaps

List submitted sitemaps

POST

/v1/urlInspection/index:inspect

Inspect a URL's index status

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Search Console OAuth client secrets and refresh tokens are encrypted in the Jentic MAXsystem vault. Agents receive only a short-lived scoped access token at execution time and never see raw client secrets.

Intent-based discovery

Agents search Jentic by intent (e.g. 'pull search analytics by query') and Jentic returns the matching searchAnalytics:query operation with its full input schema, so the agent can call it without browsing Google's discovery docs.

Time to first call

Direct integration: 1-2 days to set up an OAuth consent screen, refresh-token storage, and quota handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Indexing API

Notify Google about new or updated URLs to crawl, complementing the Search Console reporting view.

Choose Indexing API when you want to push URL change notifications. Use Search Console when you want to read performance and indexing status.

Complementary

Google Analytics Data API

Pulls on-site behaviour data that pairs with Search Console organic search metrics.

Use Analytics Data for on-site sessions and conversions. Use Search Console for pre-click impressions, clicks, and queries.

Alternative

Bing Webmaster API

Bing's equivalent for managing sites and pulling search performance from Microsoft Bing.

Use Bing Webmaster when the agent needs Bing search data instead of, or in addition to, Google.

Alternative

Semrush API

Third-party SEO data covering competitor keywords and rankings beyond a site's verified Search Console data.

Choose Semrush when the agent needs competitor intelligence. Use Search Console for first-party verified-site data.

FAQs

Specific to using Google Search Console API API through Jentic.

What authentication does the Google Search Console API use?

The Search Console API uses OAuth 2.0 with the webmasters or webmasters.readonly scope. Through Jentic the OAuth client and refresh tokens are stored encrypted in the MAXsystem vault, so the agent receives only a scoped access token at call time.

Can I pull historical search analytics data with the Google Search Console API?

Yes. POST /webmasters/v3/sites/{siteUrl}/searchAnalytics/query returns up to 16 months of data with dimensions for query, page, country, device, searchAppearance, and date. Anything older than 16 months is not retained by Google.

What are the rate limits for the Google Search Console API?

Google enforces a default per-project quota of 1,200 queries per minute and 30,000 per day for the Search Console API, with separate limits for the URL Inspection endpoint at 2,000 queries per day and 600 per minute. Quotas can be raised through the Google Cloud console.

How do I submit a sitemap through Jentic?

Run the Jentic search query 'submit a sitemap to google search console', load the resulting PUT /webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath} operation, and execute it with the encoded site URL and sitemap feed path. Jentic handles the OAuth token injection.

Is the Google Search Console API free?

Yes. The Search Console API is free to use within the published quotas. You only pay for any Google Cloud services you build alongside it.

Can the URL Inspection API check URLs on sites I do not own?

No. POST /v1/urlInspection/index:inspect only works for URLs on properties verified to the authenticated user in Search Console. Public URL inspection is not supported.