# 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.

- Page: https://www.agent200.com/connectors/google-search-console/
- Category: Search and data
- Authentication: Managed OAuth
- Identifier in code: `google_search_console`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## Google Search Console tools

- **List sites** (`google_search_console_list_sites`, read): List the properties the user can reach.
- **Query search performance** (`google_search_console_query_analytics`, read): Get clicks, impressions, CTR and position by query, page, country or device.
- **Inspect a URL** (`google_search_console_inspect_url`, read): See the index status and crawl details of a URL.
- **List sitemaps** (`google_search_console_list_sitemaps`, read): List the sitemaps submitted for a site.
- **Submit a sitemap** (`google_search_console_submit_sitemap`, write): Submit a sitemap for a site.
- **Delete a sitemap** (`google_search_console_delete_sitemap`, write): Remove a sitemap from a site.

## Limits you can set

**Turn single tools on or off.** Let the agent read performance and inspect URLs, and switch off `google_search_console_delete_sitemap` so 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "Which queries brought the most clicks last month"
- "Is the pricing page indexed"
- "Show pages that lost impressions this week"
- "Submit the new sitemap for example.com"

## Guides: Google Search Console with your AI framework

- [Google Search Console + Claude](https://www.agent200.com/connectors/google-search-console/framework/claude.md): Set up Google Search Console for Claude with Agent200, then check which tools are available to your agent.
- [Google Search Console + ChatGPT](https://www.agent200.com/connectors/google-search-console/framework/chatgpt.md): Set up Google Search Console for ChatGPT with Agent200, then check which tools are available to your agent.
- [Google Search Console + Claude Code](https://www.agent200.com/connectors/google-search-console/framework/claude-code.md): Set up Google Search Console for Claude Code with Agent200, then check which tools are available to your agent.
- [Google Search Console + Muse](https://www.agent200.com/connectors/google-search-console/framework/muse.md): Set up Google Search Console for Muse with Agent200, then check which tools are available to your agent.
- [Google Search Console + Grok Bot](https://www.agent200.com/connectors/google-search-console/framework/grok-bot.md): Set up Google Search Console for Grok Bot with Agent200, then check which tools are available to your agent.
- [Google Search Console + OpenAI Dots](https://www.agent200.com/connectors/google-search-console/framework/openai-dots.md): Set up Google Search Console for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [Google Search Console + Claude Duet](https://www.agent200.com/connectors/google-search-console/framework/claude-duet.md): Set up Google Search Console for Claude Duet with Agent200, then check which tools are available to your agent.
- [Google Search Console + Hermes Agent](https://www.agent200.com/connectors/google-search-console/framework/hermes-agent.md): Set up Google Search Console for Hermes Agent with Agent200, then check which tools are available to your agent.
- [Google Search Console + OpenClaw](https://www.agent200.com/connectors/google-search-console/framework/openclaw.md): Set up Google Search Console for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### 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.

## Related connectors

- [Tavily](https://www.agent200.com/connectors/tavily.md): Web search built for agents, reached with your Agent200 API key.
- [Exa](https://www.agent200.com/connectors/exa.md): Search the web by meaning, read page contents and find similar pages, reached with your Agent200 API key.
- [Firecrawl](https://www.agent200.com/connectors/firecrawl.md): Scrape pages into Markdown, crawl and map sites, and extract structured data, reached with your Agent200 API key.
- [Brave Search](https://www.agent200.com/connectors/brave-search.md): Search the web, news, images and videos from Brave's independent index, reached with your Agent200 API key.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
