Google Search Console
The Google Search Console API provides programmatic access to Search Console data, allowing you to monitor and maintain your site's presence in Google Search results.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Google Search Console the way a machine reads it — 99 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Google Search Console scores 60.0/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Google Search Console
Each block below is one kind of artifact we hold for Google Search Console. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Google Search Console URL Testing Tools API
Provides tools for running validation tests against single URLs, including mobile-friendly testing and rich results validation for structured data.
Google Indexing API
The Indexing API allows any site owner to directly notify Google when pages are added or removed, enabling faster crawling and indexing of content such as job postings and lives...
Google Search Console Search Analytics API
Query search traffic data for your site. Retrieve impressions, clicks, click-through rate, and average position grouped by dimensions such as query, page, country, device, searc...
Google Search Console Sitemaps API
Submit and manage sitemaps and sitemap indexes for your site. List submitted sitemaps, check their processing status, submit new sitemaps, and delete previously submitted sitemaps.
Google Search Console Sites API
Manage site-level access and verification. List verified sites, get details about a specific site, add new sites, and remove sites from your Search Console account.
Google Search Console URL Inspection API
Inspect individual URLs to retrieve detailed indexing, crawling, and serving information. Check whether a URL is indexed, view crawl details, mobile usability status, and rich r...
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Google Search Console API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Google Search Console Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Search Analytics
Analyze search traffic data including impressions, clicks, CTR, and average position by query, page, country, device, and date.
Sitemap Management
Submit, monitor, and manage XML sitemaps and sitemap indexes to optimize crawling and indexing.
URL Inspection
Inspect individual URLs for indexing status, crawl details, mobile usability, and rich results eligibility.
Index Coverage
Monitor which pages are indexed, identify indexing errors, and track coverage status across your site.
Mobile Usability Testing
Test pages for mobile-friendliness and identify mobile usability issues.
Rich Results Validation
Validate structured data markup and check rich results eligibility for individual URLs.
Site Verification
Manage site ownership verification and access permissions for Search Console properties.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Google Search Console API Rules
SPECTRALGoogle Search Console API Rules
SPECTRALJSON Schema 22
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
DetectedItems
JSON SCHEMADimensionFilterGroup
JSON SCHEMADimensionFilter
JSON SCHEMAError
JSON SCHEMAIndexStatusInspectionResult
JSON SCHEMAInspectUrlIndexRequest
JSON SCHEMAInspectUrlIndexResponse
JSON SCHEMAItem
JSON SCHEMAMobileUsabilityInspectionResult
JSON SCHEMAMobileUsabilityIssue
JSON SCHEMAGoogle Search Console Search Analytics Query
JSON SCHEMARichResultsInspectionResult
JSON SCHEMARichResultsIssue
JSON SCHEMASearchAnalyticsQueryRequest
JSON SCHEMASearchAnalyticsQueryResponse
JSON SCHEMASearchAnalyticsRow
JSON SCHEMASitemapsListResponse
JSON SCHEMASitesListResponse
JSON SCHEMAUrlInspectionResult
JSON SCHEMAWmxSite
JSON SCHEMAWmxSitemapContent
JSON SCHEMAWmxSitemap
JSON SCHEMAScroll within the panel for all 22 ·
JSON Structure 21
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Google Search Console Detected Items Structure
JSON STRUCTUREGoogle Search Console Dimension Filter Group Structure
JSON STRUCTUREGoogle Search Console Dimension Filter Structure
JSON STRUCTUREGoogle Search Console Error Structure
JSON STRUCTUREGoogle Search Console Item Structure
JSON STRUCTUREGoogle Search Console Mobile Usability Issue Structure
JSON STRUCTUREGoogle Search Console Rich Results Issue Structure
JSON STRUCTUREGoogle Search Console Search Analytics Row Structure
JSON STRUCTUREGoogle Search Console Sitemaps List Response Structure
JSON STRUCTUREGoogle Search Console Sites List Response Structure
JSON STRUCTUREGoogle Search Console Url Inspection Result Structure
JSON STRUCTUREGoogle Search Console Wmx Site Structure
JSON STRUCTUREGoogle Search Console Wmx Sitemap Content Structure
JSON STRUCTUREGoogle Search Console Wmx Sitemap Structure
JSON STRUCTUREScroll within the panel for all 21 ·
Examples 21
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 21 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
SEO Performance Monitoring
Track organic search performance metrics to identify trends, measure optimization impact, and report on search visibility.
Technical SEO Auditing
Identify and resolve indexing issues, crawl errors, and mobile usability problems affecting search performance.
Content Optimization
Analyze which queries drive traffic to specific pages and optimize content to improve rankings and click-through rates.
Automated Sitemap Submission
Programmatically submit sitemaps when content is published or updated to accelerate indexing.
Multi-Site Management
Monitor and manage search performance across multiple websites from a single integration.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Google Analytics
Combine Search Console data with Google Analytics for comprehensive website performance analysis.
Google Ads
Connect search performance data with advertising campaigns to optimize paid and organic strategy together.
Google Cloud
Deploy Search Console API integrations on Google Cloud Platform infrastructure.
BigQuery
Export Search Console data to BigQuery for advanced analytics and cross-platform reporting.
Data Studio / Looker
Visualize Search Console metrics in dashboards for stakeholder reporting and trend analysis.
Resources
Every other property we hold for Google Search Console — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/google-search-console · machine-readable index on apis.io