Google Search Console turns connected first-party search data into evidence an agent can inspect, compare, and act on. It reports the exact property, query dates, source endpoint, freshness state, and truncation facts with every result.
Use it to replace vague traffic guesses with verified queries, pages, clicks, impressions, CTR, positions, index inspection, and sitemap state. Opportunity labels use fixed published rules, so the same rows and date windows always produce the same classification.
What you can do
- list_properties — find every property available to the connected account
- search_performance — query clicks, impressions, CTR, and average position by selected dimensions
- find_opportunities — detect low CTR, striking-distance rankings, decay, and cannibalization with deterministic rules
- compare_periods — compare explicit or equal-length adjacent windows
- inspect_url — normalize index, mobile usability, rich-result, and crawl evidence for one URL
- list_sitemaps and submit_sitemap — read sitemap state or separately submit one sitemap
Who it's for
SEO teams, site owners, growth agents, and developers who need first-party search evidence rather than estimated rankings. It is especially useful for audits, content refresh decisions, and indexation diagnosis.
How to use it
- Start with list_properties and copy the exact property identifier
- Run search_performance for the dates and dimensions needed
- Use find_opportunities or compare_periods only after choosing an explicit date window
- Use inspect_url for page-level index evidence and list_sitemaps for submitted-feed state
- Call submit_sitemap only when the user explicitly wants that external change
Getting started
Connect your Google Search Console account, then begin with the exact property returned by list_properties. Treat a sitemap acknowledgement as a submission, not proof of crawling or indexing.
