Search and data
Google Search Console for AI agents.
Managed auth, ready-made tools.
Query search performance, inspect URLs and manage sitemaps in Google Search Console on behalf of each of your users.
About Google Search Console
With the Google Search Console connector, your agent works with the sites in each user’s own Search Console. It can pull clicks, impressions and positions by query or page, inspect how Google sees a URL, and list or submit sitemaps, using only the tools your project allows.
Google Search Console is Google’s tool for monitoring a site’s presence in Google Search.
Tools
What your agent can do in Google Search Console.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Search Console connection.
-
List sites
Readgoogle_search_console_list_sitesList the properties the user can reach.
-
Query search performance
Readgoogle_search_console_query_analyticsGet clicks, impressions, CTR and position by query, page, country or device.
-
Inspect a URL
Readgoogle_search_console_inspect_urlSee the index status and crawl details of a URL.
-
List sitemaps
Readgoogle_search_console_list_sitemapsList the sitemaps submitted for a site.
-
Submit a sitemap
Writegoogle_search_console_submit_sitemapSubmit a sitemap for a site.
-
Delete a sitemap
Writegoogle_search_console_delete_sitemapRemove a sitemap from a site.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Google Search Console, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read performance and inspect URLs, and switch off
google_search_console_delete_sitemapso it can never remove a sitemap. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example search analytics but not sitemaps. A call outside them is refused.
Get started
Connect Google Search Console
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google Search Console
Each end user authorizes their own Google Search Console account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google Search Console account, once. const connection = await agent200 .user("user_123") .connect("google_search_console"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google Search Console tools
Name the user, the model and the tools. The model decides which Google Search Console tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Which queries brought the most clicks last month", tools: ["google_search_console"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Google's own sign-in page. You never see or store their Google Search Console password.
-
What access is requested
The scopes the connection needs, such as viewing Search Console data or managing it, listed on Google's consent screen. Users can remove the app later from their Google account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Search Console connector and how to use it.
Connector: Google Search Console, through Agent200. In code: "google_search_console". What it does: Query search performance, inspect URLs and manage sitemaps in Google Search Console on behalf of each of your users. Page: https://www.agent200.com/connectors/google-search-console/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google Search Console's own page, through the authorization link Agent200 returns. Never ask a user for a Google Search Console password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_search_console_list_sites, google_search_console_query_analytics, google_search_console_inspect_url, google_search_console_list_sitemaps. Write tools: google_search_console_submit_sitemap, google_search_console_delete_sitemap. Name "google_search_console" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/google-search-console/framework/claude/ https://www.agent200.com/connectors/google-search-console/framework/chatgpt/ https://www.agent200.com/connectors/google-search-console/framework/claude-code/ https://www.agent200.com/connectors/google-search-console/framework/muse/ https://www.agent200.com/connectors/google-search-console/framework/grok-bot/ https://www.agent200.com/connectors/google-search-console/framework/openai-dots/ https://www.agent200.com/connectors/google-search-console/framework/claude-duet/ https://www.agent200.com/connectors/google-search-console/framework/hermes-agent/ https://www.agent200.com/connectors/google-search-console/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/google-search-console.md
Guides
Use Google Search Console with the AI you build on.
Step-by-step setup for Google Search Console with a specific model, assistant or agent framework.
-
Google Search Console + Claude
How to connect Google Search Console to Claude
-
Google Search Console + ChatGPT
How to connect Google Search Console to ChatGPT
-
Google Search Console + Claude Code
How to connect Google Search Console to Claude Code
-
Google Search Console + Muse
How to connect Google Search Console to Muse
-
Google Search Console + Grok Bot
How to connect Google Search Console to Grok Bot
-
Google Search Console + OpenAI Dots
How to connect Google Search Console to OpenAI Dots
-
Google Search Console + Claude Duet
How to connect Google Search Console to Claude Duet
-
Google Search Console + Hermes Agent
How to connect Google Search Console to Hermes Agent
-
Google Search Console + OpenClaw
How to connect Google Search Console to OpenClaw
FAQ
Google Search Console and Agent200, answered.
Who handles the Google Search Console OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Search Console.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Search Console connection, never another user's. It cannot reach anything the user or Google Search Console has not authorized.
Can I limit what my agent can do in Google Search Console?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.