How to Connect Google Search Console to ChatGPT (About a Minute, No Code)

Connect Google Search Console to ChatGPT with one URL: enable Developer mode, add the hosted Search Console MCP as a connector, sign in with Google, and ask ChatGPT about your real rankings.

ChatGPT is happy to theorize about SEO all day. Connect it to Google Search Console and it stops theorizing: it reads your actual queries, clicks, impressions and positions, and answers about your site. The connection is one URL through the hosted Search Console MCP. No code, no API keys, no Google Cloud project; about a minute end to end.

What you need

A ChatGPT plan that supports connectors (Plus, Pro, Business or Enterprise). On Business and Enterprise, a workspace admin may need to allow custom connectors.
A Google account with access to the Search Console property you want to query.
That's it. The MCP server is hosted and read-only; nothing gets installed.

Connect it, step by step

Open Settings → Connectors in ChatGPT and enable Developer mode (under Advanced). This is what unlocks adding custom MCP connectors.
Create the connector. Click Create (or Add custom MCP server), name it something like Search Console, and paste the server URL: https://mcpsearchconsole.com/mcp. Authentication is OAuth.
Sign in with Google. A Google window opens; approve the read-only Search Console scope. The connector shows its tools once connected.
Verify it. Start a new chat, enable the connector for that conversation (in the composer's tools menu if it isn't on already), and ask: "List my Search Console properties." If your sites come back, you're done.

From then on ChatGPT can call the server's tools on demand: search performance with filters and period comparisons, URL inspection, sitemaps, PageSpeed and site-health checks. Everything is read-only by design, so it can analyze your site but never change anything.

What to ask once it's connected

Try this promptPull Search Console data for my site for the last 28 days versus the previous 28. Summarize clicks, impressions, CTR and average position, then name the five queries that gained the most clicks and the five that lost the most.

Try this promptFind my striking-distance keywords: queries ranking between position 8 and 20 with at least 100 impressions in the last 28 days. Rank them by potential and suggest which existing page should target each one.

Try this promptList my ten most-impressed pages with CTR under 1.5%. For each, look at the query it ranks for and draft a better title tag and meta description.

Prefer a different assistant? The picker below has the same one-minute setup for Claude, Claude Code, Cursor, Codex and more.

Connect Google Search Console to Claude

Open Settings → Connectors in Claude Desktop or claude.ai.
Click Add custom connector and paste the URL below.
Click Add, then sign in with Google when prompted.

https://mcpsearchconsole.com/mcp

Connect Google Search Console to Claude Code

Add the server from your terminal:

claude mcp add --transport http search-console https://mcpsearchconsole.com/mcp

Run /mcp inside Claude Code and complete Google sign-in.

Connect Google Search Console to ChatGPT

Go to Settings → Connectors and enable Developer mode.
Click Create / Add custom MCP server and paste the URL below.
Authenticate with Google to finish.

https://mcpsearchconsole.com/mcp

Connect Google Search Console to Codex

Add this to ~/.codex/config.toml:

[mcp_servers.search-console]
url = "https://mcpsearchconsole.com/mcp"

On Google sign-in, Codex opens your browser to authorize. (If your Codex version only supports stdio servers, bridge it with npx mcp-remote https://mcpsearchconsole.com/mcp.)

Connect Google Search Console to Mistral Vibe

In Mistral Vibe → Settings → Connectors, choose Add MCP connector.
Paste the URL below and save.
Sign in with Google when prompted.

https://mcpsearchconsole.com/mcp

Connect Google Search Console to Cursor

Add to ~/.cursor/mcp.json (or Settings → MCP → Add server):

{
  "mcpServers": {
    "search-console": { "url": "https://mcpsearchconsole.com/mcp" }
  }
}

Reload, then authorize with Google from the MCP panel.

Connect Google Search Console to any MCP client

Any client that supports remote MCP servers over Streamable HTTP. Point it at the URL and it handles Google sign-in via OAuth.

{
  "mcpServers": {
    "search-console": { "type": "streamable-http", "url": "https://mcpsearchconsole.com/mcp" }
  }
}

Troubleshooting

No Developer mode in settings. Connectors with custom MCP servers need a paid plan, and on Business/Enterprise workspaces an admin has to allow them. Free-tier ChatGPT cannot add custom connectors.
The connector exists but ChatGPT won't use it. Connectors are per-conversation: open the tools menu in the composer and toggle it on, then ask again and mention Search Console explicitly the first time.
Google sign-in loops or closes. Allow pop-ups for chatgpt.com and retry; the OAuth window must complete in the same browser session.
Empty results for your site. Ask ChatGPT to list your properties first. sc-domain:example.com and https://example.com/ are different Search Console properties; queries must use the exact one.
"Yesterday" looks empty. Search Console data trails by about two days. Ask for trailing windows (last 7 or 28 days) instead of yesterday.

Quota and pricing

Connecting is free: discovery and site-health tools are unlimited, and data pulls (performance queries, URL inspection, sitemaps, PageSpeed) are metered per day, week and month on the free plan. Occasional analysis fits comfortably; if you run daily reporting or an agent on top, Solo removes the caps for a few euros a month.

Go further

Once the connection works, the interesting part is what you do with it: our seven MCP workflows for SEO turn these prompts into a repeatable practice, and the best SEO MCP servers comparison covers what to stack next to Search Console when a project needs backlinks, crawling or conversion data.

Ready to put your search data in your AI?

Set up the Search Console MCP, free