Use google-search-console when an agent needs first-party search performance or indexing evidence from a property the connected Google account can access. It keeps the property, date window, source endpoint, freshness, row limit, and warnings with the result.
Evidence example
Method date: 2026-08-26. Source: the search_performance manifest example and the mocked provider response asserted in tests/unit/google-search-console.test.ts; this is a schema example, not live property data or a customer result.
Input:
{"property_url":"sc-domain:example.com","start_date":"2026-07-01","end_date":"2026-07-31","dimensions":["query"],"row_limit":2}Output: Representative schema example; identifiers and values are [redacted] except the fixture-backed evidence shape.
{"available":true,"property":"sc-domain:[redacted]","query_dates":{"start_date":"2026-07-01","end_date":"2026-07-31"},"row_limit":{"requested":2,"returned":2,"truncated":true},"data_freshness":{"data_state":"final","first_incomplete_date":"2026-07-30"},"warnings":["row limit reached","incomplete date present"]}Limitations: Search Console data can lag, incomplete dates and row caps matter, average position is not a stable rank, and sitemap acknowledgement is not proof of crawling or indexing.
Permissions: A Google Search Console connector with explicit access to the exact property is required; submit_sitemap is an external write and must be requested separately.
Cost/latency: These skills are listed as free in the manifest, but Google quotas and account terms still apply; provider and network latency varies and no response-time guarantee is stated.
Safe next action: Run list_properties, let the user choose the exact property, then start with the read-only search_performance skill for a bounded date range.
See what a connector can access and the Google Search Console tool.