# How to connect Google Search Console to OpenAI Dots

> Set up Google Search Console for OpenAI Dots with Agent200, then check which tools are available to your agent.

- Page: https://www.agent200.com/connectors/google-search-console/framework/openai-dots/
- Connector: [Google Search Console](https://www.agent200.com/connectors/google-search-console.md)
- Framework: OpenAI Dots
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect Google Search Console to OpenAI Dots with Agent200.
Guide: https://www.agent200.com/connectors/google-search-console/framework/openai-dots/

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. Make sure Google Search Console is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's Google Search Console account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Google Search Console.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "google_search_console" in the tools. The model decides when a Google Search Console tool is needed; Agent200 executes the call.
7. Check it works with this request: "Ask OpenAI Dots to list the Agent200 tools available for Google Search Console, including which are read-only."
   What should come back:
   - A list of the Google Search Console tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Google Search Console, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## Overview

This guide connects Google Search Console to OpenAI Dots through Agent200. When you finish, OpenAI Dots can call the Google Search Console tools for each of your users.

Every call runs with that user's own Google Search Console connection: Agent200 runs the OAuth flow, stores and refreshes the tokens, and executes the call. You do not build or maintain a Google Search Console integration.

- **Connector:** [Google Search Console](https://www.agent200.com/connectors/google-search-console/)
- **Works with:** OpenAI Dots · Your own agent code
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/google-search-console/framework/openai-dots/#tools)
- **Model in examples:** `openai/gpt-5.6-sol`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Google Search Console enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Google Search Console account.** They approve access once, on Google Search Console's own page.
- **A model for your agent.** The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

## Connect Google Search Console to OpenAI Dots

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Google Search Console and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

Create an API key: https://agent200.com/platform/apikeys/

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Set up the Agent200 SDK

Add the SDK to your project and create a client with the key from the environment.

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 3: Let your user connect Google Search Console

Each end user authorizes their own Google Search Console account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Google Search Console's own page. Agent200 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 4: Run with the Google Search Console tools

Name the user, the model and Google Search Console in the tools. The model decides when a Google Search Console tool is needed, and Agent200 executes the call with the user's own 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.)

## Test your connection

Ask: "Ask OpenAI Dots to list the Agent200 tools available for Google Search Console, including which are read-only."

What should come back:

- A list of the Google Search Console tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for Google Search Console and make sure its tools are enabled. Tool availability depends on your project setup.

## Google Search Console tools OpenAI Dots can call

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

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input, the end user's id and the Google Search Console tools.
2. **The model picks a tool.** The model decides whether a Google Search Console tool is needed, and with which arguments.
3. **Agent200 runs the call.** It uses that user's own Google Search Console connection, within the endpoints and scopes your project allows, and returns the result to the model.
4. **Your app gets the result.** Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Google Search Console account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Google Search Console enforces what its API grants.

## Troubleshooting

### Why not connect Agent200 to a dot directly?

A dot uses the plugins connected to your ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. Building the agent with the Agent200 SDK, as on this page, is the route that works.

### The request says Google Search Console authorization is required

The end user has not connected Google Search Console yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Google Search Console's own page, then run the request again.

### OpenAI Dots does not use the Google Search Console tools

Check that Google Search Console is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Google Search Console in the request, or in the instructions, also helps the model choose the right tool.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows (services, endpoints and scopes), and Google Search Console returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Google Search Console again so they can approve the new access.

### The results come from the wrong account

Every request names an end user (`user_123` in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Google Search Console connection, never another user's.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), update `AGENT200_API_KEY` wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

## Use Google Search Console with another framework

- [Google Search Console + Claude](https://www.agent200.com/connectors/google-search-console/framework/claude.md)
- [Google Search Console + ChatGPT](https://www.agent200.com/connectors/google-search-console/framework/chatgpt.md)
- [Google Search Console + Claude Code](https://www.agent200.com/connectors/google-search-console/framework/claude-code.md)
- [Google Search Console + Muse](https://www.agent200.com/connectors/google-search-console/framework/muse.md)
- [Google Search Console + Grok Bot](https://www.agent200.com/connectors/google-search-console/framework/grok-bot.md)
- [Google Search Console + Claude Duet](https://www.agent200.com/connectors/google-search-console/framework/claude-duet.md)
- [Google Search Console + Hermes Agent](https://www.agent200.com/connectors/google-search-console/framework/hermes-agent.md)
- [Google Search Console + OpenClaw](https://www.agent200.com/connectors/google-search-console/framework/openclaw.md)

---

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