Google Search Console

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

    Read
    google_search_console_list_sites

    List the properties the user can reach.

  • Query search performance

    Read
    google_search_console_query_analytics

    Get clicks, impressions, CTR and position by query, page, country or device.

  • Inspect a URL

    Read
    google_search_console_inspect_url

    See the index status and crawl details of a URL.

  • List sitemaps

    Read
    google_search_console_list_sitemaps

    List the sitemaps submitted for a site.

  • Submit a sitemap

    Write
    google_search_console_submit_sitemap

    Submit a sitemap for a site.

  • Delete a sitemap

    Write
    google_search_console_delete_sitemap

    Remove a sitemap from a site.

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_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

Connect Google Search Console
in three steps.

  1. 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.js
    Conceptual example
    Set 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. 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.js
    Conceptual example
    Let 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. 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.js
    Conceptual example
    Run 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.

Agent brief
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.

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.

  • Tavily

    Tavily

    Web search built for agents, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Exa

    Exa

    Search the web by meaning, read page contents and find similar pages, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Firecrawl

    Firecrawl

    Scrape pages into Markdown, crawl and map sites, and extract structured data, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Brave Search

    Brave Search

    Search the web, news, images and videos from Brave's independent index, reached with your Agent200 API key.

    Agent200 API key Search and data
200 OK

Start with Google Search Console.
Your agent does the rest.

Your users connect their own Google Search Console accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)