How to Connect Google Search Console to Claude
Quick answer: Claude connects to Google Search Console through a remote MCP connector. Open Settings, choose Connectors, add a custom connector, and paste the MCP server URL. Sign in, select which Search Console properties Claude may read, and it can then answer questions about clicks, impressions, queries, pages, and sitemaps. Custom connectors require a paid Claude plan as of publication.
You ask Claude why a page lost traffic, paste in a Performance screenshot, and get a fluent answer built on numbers that are not in the image. Ask a follow-up about mobile CTR and it politely explains it cannot see that. So you export a CSV, upload it, and repeat the ritual next week.
A connector removes the ritual. Claude supports remote MCP servers, which means it can query your Search Console property directly after a one-time setup. This guide walks through the connection, what to verify before trusting it, and the questions that make it worthwhile.
SEARCH CONSOLE
How to Connect Google Search Console to Claude
PRIMARY KEYWORD
connect Google Search Console to Claude
READ TIME
8 minutes
What do you need before connecting?
Three things. A Claude plan that supports custom connectors, which as of publication means Pro, Max, Team, or Enterprise. A Google account with access to at least one verified Search Console property. And the URL of a Search Console MCP server, such as the free read-only one from SEO Receipts.
You do not need Search Console owner permissions to read performance data. Any permission level that lets you view the property in Google's interface is enough for read-only queries.
How do you add a Search Console MCP server to Claude?
The whole setup happens inside Claude's settings and one authorization screen. Anthropic documents custom connectors in its help center, and the flow is the same for any remote MCP server.
After connecting, start a new conversation and check that the Search Console tools appear in the tools menu. If nothing shows up, refresh the connector or remove and re-add it in the same browser session.
- Open Settings, then Connectors
- Choose Add custom connector and paste the MCP server URL
- Select Connect and complete the sign-in the server presents
- Choose which Search Console properties Claude may read
- Confirm the tools are listed in a new conversation
What can Claude answer once connected?
Ask bounded questions with explicit scope, the same way you would filter the Performance report. Claude picks the right tool, runs the query, and reasons over rows that Google actually returned.
Good starting points: which queries lost the most clicks in the latest finalized 28 days, which pages have high impressions with an average position between 4 and 12, what queries send traffic to a specific URL, and whether any submitted sitemap reports errors.
The compounding value is conversation. When Claude flags ten striking-distance queries, you can ask it to check the pages behind them and draft title alternatives in the same thread, with the data still in view.
Why does Claude sometimes give wrong Search Console numbers?
A connector grounds the rows Claude retrieves. It does not stop the model from summarizing loosely, mixing date ranges across a long conversation, or filling gaps when a question is vague. If a figure matters, ask Claude which tool call and date range it came from.
The data itself also has known edges. Google withholds some queries for privacy, final data arrives after a delay of a few days, and totals can differ across aggregation types. Those are Search Console properties, and no connector removes them.
How do you keep the connection safe?
Prefer servers whose tools are read-only, and share only the properties you are actively working on. The authorization step should let you pick properties individually rather than exposing everything the Google account can see.
Revoking access should not require touching your Google password. With the SEO Receipts server, the AI connection is a separate grant you can revoke on its own, and Google account access can be removed independently from your Google security settings.
TAKEAWAY CHECK
What belongs on the connect claude to search console without surprises?
- 01Confirm your Claude plan supports custom connectors.
- 02Copy the MCP server URL from a provider you trust.
- 03Add it under Settings and Connectors, then complete the sign-in.
- 04Share only the properties this work needs.
- 05Verify one known number against the Performance report.
- 06State the date range explicitly in every analysis question.
- 07Revoke the connection when a project ends.
What else do people ask about connect Google Search Console to Claude?
Does connecting Search Console to Claude cost anything?
Custom connectors require a paid Claude plan as of publication. The MCP server itself may be free; the SEO Receipts Search Console server is free in public beta and does not require a paid SEO Receipts plan. Google charges nothing for Search Console or its API.
Can Claude edit or break anything in my Search Console account?
Not through a read-only server. The tools cover listing properties, querying performance data, and reading sitemap status. Nothing can be submitted, changed, or deleted. Review any server's tool list during authorization to confirm what it can do.
Why does Claude show no Search Console tools after connecting?
Usually the connector needs a refresh. Remove and re-add it, completing authorization in the same browser session. If properties are missing instead, confirm the Google account you authorized actually has access to them in Search Console.
How fresh is the data Claude reads?
As fresh as Search Console allows. Final data arrives after a delay of a few days, so a default reporting window ends on the latest finalized date. You can ask for the newest partial days, but treat them as provisional until Google finalizes them.
Should I still export CSVs for reporting?
For a defensible client report, yes. A conversation is a working session; a report needs recorded scope, stable numbers, and a source someone else can check. Use Claude to find the story, then capture the evidence with a documented export or a verified report.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on July 27, 2026.
- 01Anthropic: about custom connectors using remote MCP
Anthropic's instructions and plan requirements for adding a remote MCP server to Claude.
- 02Model Context Protocol documentation
The open specification for connecting AI assistants to external tools and data sources.
- 03About Search Console data
Google's documentation on freshness, privacy omissions, row limits, time zones, and discrepancies.
- 04Google Search Console: clicks, impressions, CTR, and position
Google's definitions and counting rules for the four core Search performance metrics.
FREE GOOGLE SEARCH CONSOLE MCP SERVER
Ask your AI assistant about your own Search Console data.
Connect the free SEO Receipts MCP server once. Claude, ChatGPT, Cursor, or Codex can then read clicks, impressions, queries, pages, and sitemap status from the properties you select.