How to connect Claude to Google Search Console

Before you start

• A Claude account. Anthropic lists custom connectors on the Free, Pro, Max, Ultra, Team and Enterprise plans, and Free is limited to one custom connector. On Team and Enterprise an organization owner adds the connector first, then each member clicks Connect (Anthropic help center).
• Owner or full user access on the Search Console property. In Google's permissions table, owners and full users get the Performance report, URL Inspection and Submit sitemap. A restricted user still sees Performance data, gets URL Inspection as fetch only and cannot submit sitemaps, so the two sitemap tools will not work for that login. An owner can raise your level in Search Console under Settings, Users and permissions.
• Google's permission screen. When you connect Search Console in Ryze AI, Google shows its standard sign-in and consent screen. Keep every requested permission checked, as the Ryze AI help center asks. In Google's API, reading Search Analytics and URL Inspection works with the webmasters.readonly or webmasters scope, and submitting a sitemap needs the full webmasters scope (Search Console API reference).
• A verified property that matches how the site is served. A Domain property (sc-domain:example.com) covers every subdomain and protocol. A URL-prefix property (https://www.example.com/) covers only that exact prefix (Ryze AI help center).
• A Ryze AI workspace on a plan or free trial. Search Console is authorized in the workspace. The connector works with Paid Ads, Agency or an SEO plan. Without one, Claude can list workspaces and connect platforms, but every other tool replies that a subscription is required. SEO Starter is $129 per month with a 3-day free trial.

How to connect Claude to Google Search Console in claude.ai

Six steps across Ryze AI and Claude. The connector URL is the same for every user.

1. 1

   Connect Search Console in Ryze AI

   Create a Ryze AI account, open Integrations in the left sidebar and find Google Search Console (the Analytics filter narrows the list). Click Connect, sign in on Google's screen with the login that has access to the property, keep every requested permission checked and approve. Back in Ryze AI, check the Site it pre-selected and click Save. No Google Cloud project and no service account are needed.

2. 2

   Copy the connector URL

   The address is the same for every user: https://connector.get-ryze.ai/mcp. In Ryze AI it is also on the Connect Claude card on Home and on the Claude MCP card under Integrations.

3. 3

   Open Connectors in Claude

   On claude.ai open Customize, then Connectors, click + Add and choose Add custom connector. Some builds still show Settings, Connectors with an Add custom connector button and a note that connectors moved to Customize; both open the same dialog.

4. 4

   Paste the URL and add the connector

   Name it Ryze AI, paste https://connector.get-ryze.ai/mcp into the MCP server URL field and click Continue (Add in older builds). If Claude shows the detected sign-in settings, keep the defaults and click Add. There is no client ID, secret or key to enter.

5. 5

   Click Connect and allow access

   Click Connect on the new Ryze AI connector. On the Ryze AI page Connect your data sources to AI, sign in, tick the workspace that holds your Search Console property (up to 20 workspaces per connection) and click Allow connection. A Connected to Ryze AI message confirms it.

6. 6

   Start a new chat and ask your first question

   Connectors reach only the chats started after you connect, so open a new chat. Ask: List my Search Console properties and my permission level on each. Claude calls listSites and answers from your account.

Connection errors on the Claude side are covered in the Ryze AI Claude connector FAQ, and the steps follow Connect Claude and Connect Google Search Console in the Ryze AI help center.

Claude Desktop

Claude configures remote connectors through your Claude account, so a connector added on claude.ai is already in the desktop app. To add it from the app instead, open Customize, Connectors, click + Add, Add custom connector, paste the URL, click Continue, then Connect. Local MCP servers configured in claude_desktop_config.json are a separate mechanism, and a hosted connector does not need one (Anthropic help center).

Claude Code

Claude Code reads MCP servers from the command line. One command registers the connector for every project on your machine:

Then open Claude Code, type /mcp, pick the Ryze AI server (ryze) and finish the sign-in in the browser tab that opens. Use --scope project instead if the whole team should get it from a shared .mcp.json. claude mcp list confirms the server is connected.

Claude Code can also authenticate with a Ryze AI API key instead of the browser sign-in: create one in Workspace Settings, Profile, API keys and send it as an Authorization: Bearer header (Ryze AI API for agents). ChatGPT: on Plus, Pro or Business open Settings, Apps, Advanced settings, turn on Developer mode, click Create app, paste the same URL with Server URL selected and OAuth as the authentication, then sign in with Ryze AI (ChatGPT steps). Cursor: add the URL under mcpServers in .cursor/mcp.json, as shown on the developers page.

Ryze AI connector vs open-source Search Console MCP servers vs CSV export

Three ways exist to get Google Search Console data in front of Claude. They differ on setup, freshness and whether Claude can act.

We found no Search Console MCP server published by Google when we checked on November 7, 2026, so every MCP option is either a hosted connector or a server you run yourself. mcp-gsc is MIT-licensed and documents both an OAuth client and a service-account setup; a service account has to be added to each property with Full access. Other hosted Search Console MCP services also skip the Google Cloud project, for example Advanced GSC, linked from the mcp-gsc README, with a limited free version and paid plans from $15 per month, and Search Console MCP, a read-only server with a free plan, as listed on November 7, 2026. The Google Search Console MCP page lists every Ryze AI tool with its parameters.

Alternative: upload a Google Search Console CSV to Claude

When you cannot authorize a connector, a manual export still gets you a useful first audit.

1. In Search Console open Performance, then Search results, and set the date range and any filters you need.
2. Click the export button on the report and choose CSV. Google Sheets and Microsoft Excel are also offered.
3. Expect a sample: Google truncates exported data to 1,000 rows of representative examples, so large sites lose most of the long tail.
4. In Claude click the plus button in the chat box, attach the file and ask: Group these queries by topic and list the ones in positions 5 to 15 with CTR under 2%.

Limits: the data is frozen at export time, Google truncates the export to 1,000 rows, and Claude cannot apply anything back to Search Console. Use it for one-off checks. Source: Google's export Search Console data help page.

First prompts to run once Claude is connected

Copy these as written. Each one maps to a tool the connector exposes, so Claude answers from your Search Console data.

What comes back. The first prompt returns each property's siteUrl with a permission level of siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser. The second returns rows keyed by query and page with clicks, impressions, CTR and average position; one call returns up to 25,000 rows. The third returns Google's verdict, coverage state, last crawl time, robots.txt state, the canonical you declared, the canonical Google selected and rich result status. Example output, labeled: on Ryze AI's own site (our property, not a client account) on November 7, 2026, the third prompt for /google-search-console-mcp returned verdict PASS, coverage state Submitted and indexed, last crawl on November 3, 2026, crawled as mobile, and a Google-selected canonical equal to the declared one. For repeatable SEO checks, see Claude skills for SEO and a nightly striking-distance pages agent with Claude and Search Console.

Troubleshooting

No sites to pick when connecting Search Console

The Google login you used has no access to a verified property. Connect with the login that does, or add it in Ryze AI with Add one more account on the Search Console card.

Card shows Reconnect needed in Ryze AI

Google access was revoked, for example by a password change or an admin policy. Click Reconnect on the Search Console card and sign in to Google again.

Sitemap submit or removal fails on one property

Ask Claude for your permission level (listSites). Google gives Submit sitemap to owners and full users only, so a restricted user cannot change sitemaps. An owner can raise your level under Settings, Users and permissions.

Data looks incomplete or misses a host

A URL-prefix property such as https://www.example.com/ excludes https://example.com/ traffic. Use the Domain property (sc-domain:example.com) when the site serves several hosts or protocols.

The last few days are empty

Search Console reports with a 2 to 3 day delay. End the date range 3 days back, or ask Claude to use dataState all to include fresh, unfinalized data.

inspectUrl says the URL is not part of the property

The inspected URL must sit under the siteUrl Claude passes. Inspect from the Domain property, or use a URL that starts with the URL-prefix property exactly.

URL Inspection stops answering after many checks

Google allows 2,000 URL Inspection calls per site per day and 600 per minute. Inspect a sample of URLs and spread large checks over several days.

Search Console tools missing in Claude

Claude caches the tool list when the connector is added, so a platform connected afterwards has no tools. Remove the Ryze AI connector in Customize, Connectors, add it again and open a new chat.

Claude says a subscription is required

The tools need an active Ryze AI plan or free trial. Start the trial or update the card in Organization Settings, Billing, then retry in the same chat.

Authorization with the MCP server failed

Remove the Ryze AI connector in Customize, Connectors, add it again with https://connector.get-ryze.ai/mcp and start a new chat.

Google Analytics 4, Google Ads and the rest

The same connector URL also carries the Google Analytics 4, Google Ads, Meta Ads, Shopify and TikTok Ads tools once those platforms are connected in the same Ryze AI workspace, so Claude can put Search Console clicks next to GA4 sessions in one chat. See how to connect Claude to Google Analytics, how to connect Claude to Google Ads and the integrations hub. Agencies with many client sites can use the workspace setup from how to connect multiple Google Ads accounts to Claude: one Claude connection covers up to 20 Ryze AI workspaces, and each workspace can hold several Google logins. For the SEO side of an AI agent setup, connect an AI agent to Google Search Console covers the workflow end to end.