How to connect Claude to Google Search Console

Connect Search Console in Ryze AI with your Google login, add one MCP URL to Claude, and ask about clicks, queries, indexing and sitemaps in a chat.

Your MCP URL
https://connector.get-ryze.ai/mcp

Copies the link and opens Claude, Customize, Connectors, Add custom connector. Connect Search Console in Ryze AI first. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026

Quick answer

The main way to connect Claude to Google Search Console is the Ryze AI connector. Sign in to Google for Search Console inside a Ryze AI workspace, then add https://connector.get-ryze.ai/mcp as a custom connector in Claude, click Connect and start a new chat. Claude then has 7 Search Console tools: 5 that read, 1 that submits a sitemap and 1 that removes one. Ryze AI is the best Google Search Console connector for Claude users who also want GA4, Google Ads and Meta Ads data in the same chat. The trade-off is that the tools need a Ryze AI plan or free trial, while open-source servers such as mcp-gsc are free if you run them yourself and some hosted Search Console MCP services have free plans.

  1. Ryze AI plan or free trial, Search Console connected under Integrations
  2. In Claude: Customize, Connectors, + Add, Add custom connector
  3. Name it Ryze AI, paste the URL, click Add, then Connect and Allow connection
  4. New chat, ask your first Search Console question

Claude to Google Search Console at a glance

FactDetail
Main way to connectThe Ryze AI connector, added in Claude as a custom connector after one Google sign-in inside Ryze AI
Address to paste in Claudehttps://connector.get-ryze.ai/mcp
How each side signs inGoogle OAuth inside Ryze AI. In Claude, an OAuth sign-in to Ryze AI with PKCE (S256)
Search Console tools7: five read, submitSitemap writes, deleteSitemap deletes
What Claude can change in Search ConsoleSitemap entries only. No tool requests indexing, removes URLs from Google or verifies a property
Google scope held by the connectionwebmasters, which Google labels read/write access
Claude planFree, Pro, Max, Ultra, Team or Enterprise. A Free account holds one custom connector
Ryze AI priceSEO Starter at $129 per month with a 3-day free trial. Any plan or trial runs the tools. Adding the connector is free
Google's own MCP server for Search ConsoleNone found on Google's pages on November 14, 2026
Other data in the same chatGA4, Google Ads and Meta Ads tools, once those platforms are connected in the same Ryze AI workspace
Last testedConnector address on November 13, 2026. Search Console calls on November 14, 2026

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 and gets URL Inspection as fetch only, and the table leaves Submit sitemap empty for that level. The table describes the Search Console interface, and a sitemap call from a restricted login was not tried for this guide. 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. 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. Until a Site is saved, the card shows Require setup.

  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. Open Connectors in Claude

    On claude.ai open Customize, then Connectors, click + Add and choose Add custom connector. Anthropic's pages print the button as Add or + Add, and one help article goes Add, then Custom, then Web instead. Older guides, the Model Context Protocol project's page among them, still send readers to Settings, Connectors.

  4. Paste the URL and add the connector

    Name it Ryze AI and paste https://connector.get-ryze.ai/mcp into the MCP server URL field exactly, /mcp included. Where Claude can read the server's settings, it marks them Detected: keep those, and do not choose No sign in under Authentication. Click Add, or Continue first if your dialog has two steps. The Ryze AI help center says no key or request header is needed.

  5. Click Connect and allow access

    If the new Ryze AI connector shows Connect, click it. On claude.ai the sign-in page opens in the same tab. 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. Claude then lists Ryze AI as Connected under Your connectors.

  6. Start a new chat and ask your first question

    Open a new chat, as the Ryze AI help center asks. 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.

Sources: Anthropic, add a custom connector, Anthropic help center on custom connectors, Model Context Protocol, remote servers. Checked November 14, 2026.

Claude Desktop

A connector added on claude.ai belongs to your Claude account, so it is already in the desktop app. To add it there instead, open Customize in the sidebar, then Connectors, and follow the same steps; the Ryze AI sign-in opens in your browser. Claude still reaches the connector from Anthropic's cloud, not from your computer. Local servers set up in claude_desktop_config.json are a separate mechanism that uses your own network, and Anthropic says they are not available in claude.ai or in Cowork sessions that run in the cloud. A hosted connector does not need one.

Claude connectors: what Anthropic documents

TopicWhat Anthropic's pages say
Where you add itCustomize > Connectors, then Add (+ Add on some pages) and Add custom connector. In the desktop app, Customize is in the sidebar
Fields in the add dialogName, MCP server URL, Authentication, OAuth client, Request headers and Advanced > Transport. Request headers is a beta only some organizations see
TransportsStreamable HTTP for remote servers; the older HTTP+SSE still works and is being deprecated. Desktop extensions use stdio
Sign-inOAuth 2.0 with PKCE S256. Claude registers with its published identity, Dynamic Client Registration or an OAuth client you enter, and renews tokens itself
Tool approvalAllow once or Always allow when Claude asks. Standing rules under Tool permissions: Always allow, Needs approval or Blocked, per tool or per group
PlansFree (one custom connector), Pro, Max, Ultra, Team and Enterprise. On Team and Enterprise an Owner adds it under Organization settings > Connectors and members click Connect
Where connectors are managedCustomize > Connectors > Your connectors: Tool permissions, Disconnect, or Remove from the three-dot menu. A row reads Connected, Connect or Reconnect
Ryze AI in the Connectors DirectoryListed at claude.ai/directory/ryze-ai with the Community label: automated checks, not verified by Anthropic. Signed out, the button reads Sign in to add
Local serversDesktop app only, as a desktop extension (.mcpb) or a command in claude_desktop_config.json

Sources: Anthropic help center on custom connectors, add a custom connector, connectors, getting started, building connectors, connector authentication, Ryze AI in the Connectors Directory. Checked November 14, 2026.

Claude Code

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

claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope user

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 get ryze shows whether the server is connected.

Claude Code itself needs a Pro, Max, Ultra, Team, Enterprise or Console account; the free claude.ai plan does not include it.

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: OpenAI gives full custom MCP servers to Business and Enterprise/Edu workspaces and read and fetch only to Pro. Go to Plugins, select the plus button, then Add custom MCP server, paste the same URL, choose OAuth and sign in with Ryze AI (see also the Ryze AI ChatGPT guide). Cursor: add the URL under mcpServers in .cursor/mcp.json, as shown on the developers page.

Search Console access and scope

Claude reaches your data through two sign-ins, Google inside Ryze AI and Ryze AI inside Claude. Three settings then limit what it can do.

The Google scope
webmasters, Google's read/write scope, which covers the reads and the two sitemap changes.
Your level on the property
Claude reaches only what your Google login reaches. listSites shows your level per property.
Tool permissions in Claude
Always allow, Needs approval or Blocked per tool. On Team and Enterprise, an Owner's per-tool policy is the ceiling.

The Google scope behind each tool

The Ryze AI connection asks Google for https://www.googleapis.com/auth/webmasters. Google requires it for the two sitemap changes and accepts it, or the read-only scope, for the reads. Each Google method is paired with the Ryze AI tool whose description matches it.

Google methodScope Google requiresRyze AI tool
searchanalytics.querywebmasters.readonly or webmastersrunRawSearchAnalytics
urlInspection.index.inspectwebmasters.readonly or webmastersinspectUrl
sites.listwebmasters.readonly or webmasterslistSites
sitemaps.listwebmasters.readonly or webmasterslistSitemaps
sitemaps.submitwebmasters onlysubmitSitemap
sitemaps.deletewebmasters onlydeleteSitemap

What each property level allows

Your level on the property is the second limit. Google's permissions table gives its three user levels these rights in the Search Console interface:

Level (listSites value)What Google saysPerformanceURL InspectionSubmit sitemap
Owner (siteOwner)Full control over the propertyYesYesYes
Full user (siteFullUser)View rights to all data and some actionsYesYesYes
Restricted user (siteRestrictedUser)Simple view rights on most dataYesFetch onlyCell left empty

Not part of the connection: indexing requests, URL removals, property verification, and adding or deleting a property (sites.add and sites.delete). The API has no site-wide index coverage, so URL Inspection goes one URL per call. getIndexationSummary has no row in the scope table because this guide could not match it to a single Google method.

Sources: Search Console API authorization, searchanalytics.query, urlInspection.index.inspect, sitemaps.submit, sitemaps.delete, Search Console permissions. Checked November 14, 2026.

Removing access

To cut Claude off, open Customize > Connectors, pick Ryze AI and click Disconnect, which signs Claude out and keeps the connector in the list, or choose Remove from the three-dot menu. Anthropic adds that access can also be withdrawn in the connected service's own security settings.

What Claude can do in Search Console

Seven Search Console tools, each named google_search_console__ plus the short name used on the rest of this page. Every tool takes the workspace and an optional connection_id, and all but listSites need the property's siteUrl, which listSites returns.

ToolAccessWhat it does
google_search_console__listSitesReadLists the properties your Google login can reach, with your level on each.
google_search_console__runRawSearchAnalyticsReadSearch Analytics by query, page, country, device, search appearance or date, for web, image, video, news or Discover results, up to 25,000 rows per request.
google_search_console__inspectUrlReadIndex status of one URL: coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results.
google_search_console__listSitemapsReadSitemaps with last submitted and downloaded dates, errors, warnings and submitted counts. Google marks the per-sitemap indexed count as deprecated.
google_search_console__getIndexationSummaryReadA sitemap summary: how many sitemaps, submitted URLs, errors, warnings and pending items.
google_search_console__submitSitemapWriteSubmits or resubmits a sitemap URL.
google_search_console__deleteSitemapDeleteTakes a sitemap off the property's list in Search Console. The file on your site stays.

To review sitemap changes, open Customize > Connectors > Ryze AI > Tool permissions and set submitSitemap and deleteSitemap to Needs approval, or Blocked. In Research mode Claude can call connector tools without asking again, so Anthropic suggests switching write tools off first. The Ryze AI chat has its own Tool approvals setting, which starts on Skip all approvals and can be switched to Approve write & delete or Manual approve.

Search Console and Claude limits in numbers

LimitValue
Search Analytics calls1,200 queries per minute per site and per user. Per Google Cloud project: 40,000 per minute and 30,000,000 per day
Search Analytics loadMeasured in 10-minute and 1-day chunks. Grouping or filtering by page and query costs the most, and longer date ranges cost more. After a quota error, wait 15 minutes
URL Inspection calls2,000 per day and 600 per minute per site. Per project: 10,000,000 per day and 15,000 per minute
Sites and sitemaps calls20 per second and 200 per minute per user. Per project: 100,000,000 per day
Rows in one answer1 to 25,000, and 1,000 when no limit is set. The Ryze AI tool caps a request at 25,000 too
Rows beyond thatRepeat the query with startRow raised by 25,000 until an answer has 0 rows
Rows per dayAt most 50,000 a day per search type, sorted by clicks
FreshnessTypically 2 to 3 days behind. dataState all adds rows that may be incomplete
History and time zone16 months, with dates read in Pacific Time
URL Inspection reachOne URL per call, from Google's index only; a live URL cannot be tested
Claude sideAbout 150,000 characters per tool result and 240 seconds per tool call, on claude.ai and Desktop

Sources: Search Console API usage limits, searchanalytics.query, getting all your data, URL Inspection reference, Google help on Search Console data, Performance report help, Anthropic connector limits. Checked November 14, 2026.

The Search Console calls made in the test

Each row is one call through the Ryze AI connector on November 14, 2026, made from Claude Code with the default Google sign-in. The first five ran in a test workspace against a Domain property; the last ran in a second workspace. No account name, site or number from the answers is shown.

Tool and requestWhat came back
listSitesWorked.
runRawSearchAnalytics: 7 days, grouped by query, rowLimit 25001Refused by Google with HTTP 400, reason invalidParameter.
runRawSearchAnalytics: grouped by a dimension called keywordRefused with HTTP 400, status INVALID_ARGUMENT.
runRawSearchAnalytics: end date earlier than the start dateRefused with HTTP 400, reason invalidParameter.
runRawSearchAnalytics: 7 days, grouped by query, equals filter on a random 20-letter stringWorked with nothing to report. The whole answer was {"responseAggregationType":"byProperty"}, with no rows key.
runRawSearchAnalytics: 90 days, grouped by query, rowLimit 120, dataState all, includingRegex filter on queryWorked. Rows carried keys, clicks, impressions, ctr and position, highest clicks first. Fewer than the 120 asked for came back, so no second page was needed. No metadata object.

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.

Start with these three

  • List my Search Console properties and my permission level on each.
  • For sc-domain:example.com, show the top 25 queries and pages by clicks for the last 28 days with clicks, impressions, CTR and average position.
  • Inspect https://www.example.com/blog/new-post: is it indexed, which canonical did Google choose, and when was it last crawled?

Reporting and opportunities

  • Compare clicks, impressions, CTR and position by page for the last 28 days against the 28 days before and list the 10 biggest drops.
  • Find queries in positions 5 to 15 with more than 500 impressions and CTR under 2% over the last 3 months.
  • Break down clicks by device and country for the last 28 days and flag queries where mobile position is 3 or more places worse than desktop.

Indexing and sitemaps

  • Which sitemaps have errors or warnings, and when did Google last download each one?
  • Give me the indexation summary for the property: sitemaps, submitted URLs, errors, warnings and pending sitemaps.
  • List my sitemaps, then resubmit https://www.example.com/sitemap.xml. Ask me before you submit.

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 with keys, clicks, impressions, ctr and position, sorted by clicks; one call returns up to 25,000 rows. The third returns what inspectUrl covers: coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results. For repeatable SEO checks, see Claude skills for SEO and a nightly striking-distance pages agent with Claude and Search Console.

10 jobs to give Claude

Ten jobs for Claude, each with its tool. Calls of the kind behind the first three ran through the connector on November 14, 2026, with other date ranges; the next six follow the tool definitions and were not run; the last has no tool.

JobAsk ClaudeToolWorks on the default connection
Property checkList my Search Console properties and my level on each.listSitesYes
Top queriesTop 50 queries by clicks for the last 28 days, with impressions, CTR and position.runRawSearchAnalyticsYes
Question queriesLast 90 days with fresh data: only queries matching how|what|why.runRawSearchAnalyticsYes
Pages near page onePages in positions 8 to 20, with the queries each ranks for.runRawSearchAnalyticsYes
Device, country and DiscoverSplit last month's clicks by device and country, then show Discover on its own.runRawSearchAnalyticsYes
New article trackingDaily clicks and impressions for https://www.example.com/blog/new-post since launch.runRawSearchAnalyticsYes
Index statusIs https://www.example.com/pricing indexed, and which canonical did Google pick?inspectUrlYes, one URL per call
Sitemap healthMy sitemaps with errors and warnings, then the property's sitemap summary.listSitemaps, getIndexationSummaryYes
Sitemap changeResubmit https://www.example.com/sitemap.xml and remove the old sitemap I name.submitSitemap, deleteSitemapYes. Google's table gives Submit sitemap to owners and full users; set both to Needs approval to see each call
Indexing requestAsk Google to index my new page.NoneNo. No Ryze AI tool requests indexing

6 ways to connect Claude to Google Search Console

Six ways can put Search Console data in front of Claude. This guide treats the Ryze AI connector as the main way: one Google sign-in inside Ryze AI, one address and a browser sign-in in Claude, and GA4 and ad platform tools on the same connection. The pages of the other five were opened on November 14, 2026, and each is described as its own pages describe it, with the setup that applies in Claude.

WayRuns whereSetup in ClaudeWhat it reaches in Search ConsolePrice
Ryze AI connector (the main way)Hosted. One address for every userCustomize > Connectors > Add custom connector, paste https://connector.get-ryze.ai/mcp, Connect and sign in7 tools: properties, Search Analytics, URL Inspection, sitemap list and summary; submit and remove a sitemapAdding it is free. The tools need SEO Starter at $129 per month with a 3-day trial, Paid Ads at $89 with a 7-day trial, or another plan
Windsor.aiHostedIts page says to search for Windsor under Customize, Connectors in Claude, click Add, then connect Search Console once in Windsor.aiRead-only clicks, impressions, CTR and position, plus fields such as words_in_query. Sitemaps to read; no URL InspectionFree plan with one data source after a 30-day trial. Basic $19 per month billed yearly
ComposioHostedIts toolkit page names Claude, but the setup pages opened cover only ChatGPT and Claude Code. Anthropic lets any remote address, such as https://connect.composio.dev/mcp, be added as a custom connector; that was not tried with Composio14 tools, among them Search Analytics Query, Inspect URL, Submit Sitemap, Add Site and Verify Site OwnershipFree: 10,000 tool calls a month. Standard: $18 per seat per month
Coupler.ioHosted, over data it syncs on a scheduleA Custom MCP destination gives a server URL and a token. Its page names claude_desktop_config.json for Claude Desktop; in claude.ai the token needs Request headers, a beta only some organizations haveRead-only synced data, refreshed as often as every 15 minutes. No sitemap managementFree plan with manual refresh; Starter from $24 per month billed yearly. MCP per plan not shown
AminForou/mcp-gsc, open sourcePython on your computer (uvx mcp-search-console)Claude Desktop only, per its README. A command in claude_desktop_config.json, plus your own Desktop app OAuth client from Google Cloud Console, or a service account key with the account added as a user on the property. Cloning needs Python 3.11+The README speaks of 20 tools and lists 15, batch inspection of up to 10 URLs included. add_site, delete_site and delete_sitemap stay off by defaultFree, MIT. 2,202 GitHub stars on November 14, 2026; 0.4.2 on PyPI, November 6, 2026
Bulk data export plus Google's BigQuery MCP serverGoogle Cloud, at https://bigquery.googleapis.com/mcpAn owner turns on Bulk data export in Search Console with a billed Google Cloud project. Claude then needs an OAuth client ID and secret from Google Cloud, because Google's remote MCP servers do not support Dynamic Client RegistrationPerformance data from the first export on, without anonymized queries. No URL Inspection or sitemaps. 3,000 rows per queryGoogle Cloud storage and query costs, with a free usage level

Options that do not fit this job in Claude

  • Zapier MCP. Zapier names Claude and Claude Code among its MCP clients, but no Google Search Console page was found on Zapier on November 14, 2026: the address patterns that open its Google Analytics 4 and Shopify pages returned 404 for Search Console.
  • Google's Developer Knowledge MCP server. It reads Google's developer documentation and holds no account data. Google names Claude Code and Claude Desktop for it, not Claude on the web.
  • The Search Console API on its own. Google's API pages describe REST calls from your own code with OAuth 2.0, name no assistant and give no MCP address to paste into Claude.
  • AI-powered configuration in Search Console. An experiment inside the Performance report, in the Search Console interface only, with 20 requests per user per day for a small share of users. It names no outside assistant.
  • Google's Google Analytics MCP server. Its README covers the Google Analytics Admin and Data APIs and never mentions Search Console.

Which one to pick

Pick Ryze AI for Search Console in Claude on the web, the desktop app and your phone from one address, with URL Inspection, the sitemap tools and other marketing platforms in one chat. Its limits are the plan or trial it needs, no indexing requests, and sitemap changes that run as your Tool permissions allow. Windsor.ai fits read-only reporting, with extra query fields and a free plan for one data source. Coupler.io fits analysis of synced data and cannot change anything in Search Console. Composio lists 14 Search Console tools, adding sites and verifying ownership among them, but its pages opened give no claude.ai steps. mcp-gsc suits free, local use in Claude Desktop with your own Google OAuth client and can inspect up to 10 URLs in one call; ahonn/mcp-server-gsc is a one-tool open-source option (search_analytics) that needs a service account. The BigQuery route keeps the exported data in your own Google Cloud project, holds nothing from before the export starts, and was not tried here; Google does not present the pair as a Search Console connector. For a one-off look, use the CSV export below.

The Google Search Console MCP page lists every Ryze AI tool with its parameters. Sources: Google remote MCP servers, Google MCP repository, Windsor.ai Search Console MCP, Windsor.ai pricing, Composio Search Console toolkit, Composio pricing, Coupler.io Search Console MCP, Coupler.io pricing, AminForou/mcp-gsc, ahonn/mcp-server-gsc, Search Console bulk data export, BigQuery MCP server, Google MCP client setup, Zapier MCP quickstart, Developer Knowledge MCP, Search Console API, AI-powered configuration, Google Analytics MCP server, Anthropic, add a custom connector. Checked November 14, 2026.

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.

Search Console, Claude and MCP: dates that matter

DateWhat happened
January 31, 2022Google launched the URL Inspection API, with 2,000 calls a day and 600 a minute per property.
February 21, 2023Google announced bulk data export of Search Console performance data to BigQuery.
November 25, 2024Anthropic open-sourced the Model Context Protocol; Claude ran MCP servers locally in the desktop app.
May 1, 2025Anthropic launched Integrations, its first remote MCP support in Claude on the web and desktop, in beta on Max, Team and Enterprise.
July 14, 2025Anthropic opened its directory of tools that connect to Claude.
December 4, 2025Google announced AI-powered configuration for the Performance report as an experimental feature.
December 10, 2025Google put remote MCP servers in Preview for select services, BigQuery among them. Through the newest entry, September 14, 2026, its MCP release notes never mention Search Console.
February 25, 2026Claude Desktop gained a Customize section grouping skills, plugins and connectors.
April 20, 2026Google's BigQuery MCP server became generally available.
November 6, 2026mcp-search-console 0.4.2, the PyPI package of mcp-gsc, came out; still the newest on November 14.
November 14, 2026Google's remote MCP product list (last updated November 12), its MCP repository and the Search Console API pages showed no Search Console server.

Sources: Search Central blog, January 31, 2022, Search Central blog, February 21, 2023, Anthropic, Model Context Protocol, Anthropic, Integrations, Anthropic, connectors directory, Search Central blog, December 4, 2025, Google Cloud MCP release notes, Claude release notes, BigQuery release notes, mcp-search-console release data on PyPI, Google remote MCP servers. Checked November 14, 2026.

How this guide was tested

The connector address was checked on November 13, 2026, and the Search Console calls were run on November 14, 2026. The table lists what was run and what came back.

What was runWhat came back
The connector address without signing in (November 13)A request to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header pointing to the sign-in details. Anthropic's docs say a 401 is what starts Claude's sign-in.
The sign-in details (November 13)Both discovery files on the connector's host loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and two scopes, mcp:read and mcp:write.
The connector's tool list, loaded in Claude Code (November 14)All seven Search Console tool names resolved: five read, one write, one delete.
listSites (November 14)Worked.
Four Search Analytics calls in the test workspace (November 14)Google refused three that were wrong on purpose; one with a filter matching nothing came back empty.
One Search Analytics call in a second workspace (November 14)Worked. It served only to find the questions searchers ask, and its numbers are not shown.

Not run for this page: any step inside Claude. The connector was not added in claude.ai or Claude Desktop and nothing was asked there; those steps follow Anthropic's pages as read on November 14, 2026. The calls came from Claude Code, which reaches the same address and the same seven tools, so they show what the connector and Google return; what claude.ai or Claude Desktop would display was not seen. Also not run: inspectUrl, listSitemaps, getIndexationSummary, and submitSitemap and deleteSitemap, which change Search Console. No call grouped by page, country, device, search appearance or date, used another result type, came from a restricted login or tried to hit a quota.

Errors and fixes

Exact Search Console error messages from the test

Google returned these three messages through the connector in the test on November 14, 2026. The connector passes each one on as Error 400: followed by Google's JSON error body. If Claude shows one of them, this is what it means.

MessageWhat it meansWhat to ask Claude
'25001' is not a valid row limit value. For valid row limit values see https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics/query#rowLimit.The request asked for more than 25,000 rows. Google's code is HTTP 400 with reason invalidParameter.Ask for 25,000 rows or fewer and page on with startRow.
Invalid value at 'dimension[0]' (type.googleapis.com/google.searchconsole.v1.searchanalytics.ApiDimension), "keyword"The grouping named a dimension Google does not have. Search terms are the query dimension.Ask Claude to group by query, page, country, device, searchAppearance or date.
Invalid date range defined by startDate and endDate. End date cannot precede the start date.The end date came before the start date.Ask Claude to swap the two dates and keep the YYYY-MM-DD form.

Documented but not seen in the test: Google's quota exceeded error, the same for every quota event, after which Google says to wait 15 minutes; and request timed out, which the Ryze AI tool definition says to resend once on its own and then narrow with a shorter date range, one dimension and no regex filter. Anthropic also documents Couldn't reach the MCP server, Authorization with the MCP server failed and Unexpected error while invoking tool for any connector. Sources: Search Console API usage limits, Anthropic connector troubleshooting. Checked November 14, 2026.

Setup and data problems

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's permissions table gives Submit sitemap to owners and full users and leaves it empty for restricted users, so ask an owner to 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
The Ryze AI help center says Claude keeps the tool list from the moment 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
Anthropic documents this message for a sign-in that started but did not finish, or for an address that redirects to another host. Remove the Ryze AI connector in Customize, Connectors, add it again with https://connector.get-ryze.ai/mcp exactly as written and start a new chat.

Terms on this page

MCP
The Model Context Protocol, which Anthropic open-sourced in November 2024. Every connector in Claude's directory is an MCP server.
Custom connector
A remote MCP server added to Claude by its address. Anthropic does not review it, and Claude never suggests it.
Domain property
Every subdomain, protocol and path of a domain, written sc-domain:example.com in the API. It needs DNS record verification unless the site runs on a Google product such as Blogger.
URL-prefix property
Only URLs that start with one exact prefix, protocol included; in the API it ends with a slash.
Permission level
listSites' value per property: siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser.
Average position
The average of the topmost spot your site held in Google's results.
Fresh data
Recent rows Google has not finalized, returned with dataState all.

Sources: Anthropic, Model Context Protocol, Anthropic, directory and custom connectors, Search Console property types, Performance report metrics, searchanalytics.query, Sites resource. Checked November 14, 2026.

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.

Frequently asked questions

How do I connect Google Search Console to Claude?

Connect Search Console in a Ryze AI workspace with your Google login, then in Claude open Customize, Connectors, + Add, Add custom connector, paste https://connector.get-ryze.ai/mcp, click Connect and allow access to that workspace. Start a new chat and ask a Search Console question. The whole setup is a Google sign-in, one pasted address and a Ryze AI sign-in, with no code to write.

Is there a Google Search Console MCP for Claude?

Yes. The Ryze AI connector at https://connector.get-ryze.ai/mcp is a hosted Search Console MCP server that Claude adds as a custom connector, with 7 tools after a Google sign-in in Ryze AI. Windsor.ai, Composio and Coupler.io run hosted servers whose pages name Claude, and the open-source mcp-gsc runs in Claude Desktop. Google itself listed none on its MCP pages on November 14, 2026.

Is there an official Google Search Console MCP server?

No Google page listed one when we checked on November 14, 2026. Google's list of products with a remote MCP server has no Search Console row, and its MCP repository has a Google Analytics server but none for Search Console. Google documents two routes to the data instead: the Search Console API, and bulk data export to BigQuery, which Google's BigQuery MCP server can query. Hosted connectors such as Ryze AI and open-source servers such as mcp-gsc fill the gap; mcp-gsc needs your own Google OAuth client or a service account.

Which Search Console permission do I need?

Owner or full user. Google's permissions table gives both levels the Performance report, URL Inspection and Submit sitemap. A restricted user can read Performance data and gets URL Inspection as fetch only, and the table leaves Submit sitemap empty for that level, so plan sitemap changes with an owner or full user login. An owner changes levels under Settings, Users and permissions in Search Console.

Which Search Console tools does Claude get through Ryze AI?

Seven. listSites, runRawSearchAnalytics, inspectUrl, getIndexationSummary and listSitemaps read data, submitSitemap writes and deleteSitemap deletes. Set the last two to Needs approval under Customize, Connectors, Ryze AI, Tool permissions and Claude asks before either one runs. Together they cover properties, Search Analytics queries, URL Inspection and sitemaps.

Can Claude change my site or my Search Console settings?

Through the Search Console tools, only sitemap entries. submitSitemap adds or resubmits a sitemap URL, and deleteSitemap removes the entry from Search Console while the file on your site stays. None of the seven Search Console tools edits pages, robots.txt, users or property settings. The same connector can edit site content through its WordPress, Shopify and GitHub tools when those platforms are connected in the workspace, so keep write tools on Needs approval under Customize, Connectors, Ryze AI and Claude asks before each change.

Does this work in Claude Desktop and Claude Code?

Yes. Connectors are tied to your Claude account, so one added on claude.ai also appears in Claude Desktop. In Claude Code run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope user, then type /mcp inside Claude Code to finish the sign-in in the browser. Claude Code needs a Pro, Max, Ultra, Team, Enterprise or Console account.

Does it work with Domain and URL-prefix properties?

Both. listSites returns each property's exact siteUrl, such as sc-domain:example.com for a Domain property or https://www.example.com/ for a URL-prefix property, and Claude passes that string to the other tools. A URL-prefix property for the www host does not include traffic on the bare domain.

Why do the numbers in Claude differ from the Search Console UI?

Usually the date range. Search Console reports with a 2 to 3 day delay, finalized data is the default in the API, and asking for dataState all adds the fresh, incomplete days. The UI export is truncated to 1,000 rows, while one API call through the connector returns up to 25,000 rows, so totals built from an export can come out lower.

Claude connects, but a Search Console tool says I lack permission. What should I check?

Check your level on the property first: ask Claude to run listSites, which returns siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser for each one. Google's table gives Performance data to owners, full users and restricted users, and Submit sitemap to owners and full users only. Then make sure the siteUrl Claude used matches the property exactly, such as sc-domain:example.com. If the level is right and the error stays, connect Search Console in Ryze AI again and keep every requested Google permission checked.

Can I connect several Search Console properties or client sites?

Yes. listSites lists every property the Google login can reach, and you name the site in the chat. In Ryze AI you can add another Google login with Add one more account on the Search Console card and set the agent's default sites. One Claude connection covers up to 20 Ryze AI workspaces, so agencies usually keep one workspace per client.

Is there one MCP server that connects Google Analytics, Google Ads and Search Console to Claude?

Yes. The Ryze AI connector serves GA4, Google Ads and Search Console tools from the same address once those platforms are connected in the same Ryze AI workspace, so a single custom connector in Claude covers all three. The same address also works in ChatGPT and Cursor.

Why does Claude not see my Search Console data?

Start a new chat first, as the Ryze AI help center asks. Then check that Search Console shows Connected under Integrations in the workspace you allowed. If you connected Search Console after adding the connector, remove the Ryze AI connector in Claude, add it again and open a new chat: the Ryze AI help center says Claude keeps the tool list from the moment the connector was added.

How much does it cost to connect Claude to Google Search Console?

Connecting is free, and the Search Console tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial, and annual billing is 30% off the first year. On the Claude side, custom connectors work on every Claude plan, with one custom connector on Free.

What should I ask Claude first?

Start with three prompts: list your properties and permission levels, pull the top queries and pages for the last 28 days with clicks, impressions, CTR and position, and inspect one important URL for index status and the canonical Google chose. Together they confirm access, show where clicks come from and check indexing.

Connect Search Console and your ad accounts to Claude

One Ryze AI workspace holds Search Console, GA4, Google Ads and Meta Ads. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial, and annual billing takes 30% off the first year.

Next: how to connect Claude to Google Analytics, how to connect multiple Google Ads accounts to Claude and the integrations hub.

Need help? Read the Claude connector FAQ, connecting Search Console in Ryze AI or email Ryze AI support.