How to connect multiple Google Search Console accounts to Claude
Quick answer: Connect each Google login that can open your Search Console sites to Ryze AI with Add one more account, then name the site in your Claude prompt. Ryze AI is the best way to connect multiple Google Search Console accounts to Claude in 2026, with one caveat: it reaches only the sites those logins can open.
Below: properties, roles, logins, naming, prompts, fixes.
Ryze AI · SEO Starter
All your Search Console sites in Claude
- 3-day free trial, $129 a month
Used by 2,000+ marketers
Connect multiple Google Search Console accounts to Claude in 5 steps
Order matters: settle who can open each property first, then connect each login, then add Claude.
1. Check which Google login can open which property
In Search Console, open Settings, then Users and permissions, for each property. A login needs a verified property and a permission level on it. Add the right Google account as a user where it is missing.
2. Connect the first login in a Ryze AI workspace
In the Ryze AI app, open Integrations, find Google Search Console and click Connect. Sign in to Google, keep every requested permission checked, then check the Site and click Save. Until a Site is saved the card shows Require setup.
3. Add every other login to the same workspace
On the Google Search Console card use Add one more account for each further Google login that belongs to the same business, and pick a Site for each. Mark one as the primary with the star.
4. Add the Ryze AI connector to Claude
In Ryze AI, open Integrations, Claude MCP and click Open Claude MCP, which copies the connector URL and opens Claude. Add it as a custom connector named Ryze AI, click Connect, choose your workspaces and click Allow connection. The single-login guide shows each screen.
5. Name the site in every prompt
Start a new chat and name the property exactly as Search Console lists it. Ask Claude to list your sites first if you are unsure.
Multi-account setups at a glance
Pick the row that matches how your Search Console properties are owned.
- 1One Google login that owns or can view every propertyYou or your team already use a single login for all sites
How Claude picks the site: Ask for the site list, then name the property in the prompt
- 2Several Google logins in one Ryze AI workspaceSites of one business sit under different logins
How Claude picks the site: Add one more account in Ryze AI; the starred login is the default
- 3One Ryze AI workspace per clientSeparate clients whose data must never mix
How Claude picks the site: Name the workspace; one Claude connection covers up to 20
- 4Agent default accountsA login reaches many sites but a few matter most
How Claude picks the site: The agent looks at the defaults first; other sites stay reachable
- 5A community MCP server you run yourselfA developer wants local control of the Search Console API
How Claude picks the site: Depends on the server; check its README
| # | Setup | Fits when | How Claude picks the site |
|---|---|---|---|
| 1 | One Google login that owns or can view every property | You or your team already use a single login for all sites | Ask for the site list, then name the property in the prompt |
| 2 | Several Google logins in one Ryze AI workspace | Sites of one business sit under different logins | Add one more account in Ryze AI; the starred login is the default |
| 3 | One Ryze AI workspace per client | Separate clients whose data must never mix | Name the workspace; one Claude connection covers up to 20 |
| 4 | Agent default accounts | A login reaches many sites but a few matter most | The agent looks at the defaults first; other sites stay reachable |
| 5 | A community MCP server you run yourself | A developer wants local control of the Search Console API | Depends on the server; check its README |
Rows 1 to 4 are Ryze AI settings that combine. Row 5 is the do-it-yourself route, and Google publishes no Search Console MCP server of its own.
How Search Console properties and permissions decide what Claude can see
Claude reaches only the properties your Google login can open, so Search Console access is the real setup step.
Search Console has no manager account like Google Ads. Access belongs to a property, and a login sees a property only if someone added it as a user or verified it. Google lets one account hold up to 1,000 properties.
Domain and URL-prefix properties
Domain property
- What it covers
- All subdomains and protocols of a domain; verified by DNS record only
- How it appears in the API
- sc-domain:example.com
URL-prefix property
- What it covers
- Only URLs that start with the exact prefix, including http or https
- How it appears in the API
- https://www.example.com/ with a trailing slash
| Property type | What it covers | How it appears in the API |
|---|---|---|
| Domain property | All subdomains and protocols of a domain; verified by DNS record only | sc-domain:example.com |
| URL-prefix property | Only URLs that start with the exact prefix, including http or https | https://www.example.com/ with a trailing slash |
The property type definitions and the Sites API format are Google's. One site can appear twice in your list, as a Domain property and as one or more URL-prefix properties, with different numbers. Name the exact one you want.
Permission levels and what Claude can do with each
Verified owner
- In Search Console
- Proved ownership with a token; no maximum per property; manages users and settings
- Through Claude and Ryze AI
- Reads, plus sitemap submit and delete
Delegated owner
- In Search Console
- Granted ownership by a verified owner without a token; capped at 500 together with verified owners
- Through Claude and Ryze AI
- Reads, plus sitemap submit and delete
Full user
- In Search Console
- Views most data and takes some actions
- Through Claude and Ryze AI
- Reads; sitemap changes depend on what Google allows this role to do
Restricted user
- In Search Console
- Simple view rights on most data
- Through Claude and Ryze AI
- Reads only; Google may reject sitemap changes
Associate
- In Search Console
- Acts for the site through a linked service; no direct Search Console access
- Through Claude and Ryze AI
- Not a login Claude can use
| Search Console role | In Search Console | Through Claude and Ryze AI |
|---|---|---|
| Verified owner | Proved ownership with a token; no maximum per property; manages users and settings | Reads, plus sitemap submit and delete |
| Delegated owner | Granted ownership by a verified owner without a token; capped at 500 together with verified owners | Reads, plus sitemap submit and delete |
| Full user | Views most data and takes some actions | Reads; sitemap changes depend on what Google allows this role to do |
| Restricted user | Simple view rights on most data | Reads only; Google may reject sitemap changes |
| Associate | Acts for the site through a linked service; no direct Search Console access | Not a login Claude can use |
Roles follow Google's user roles page, which also sets the cap at 100 non-owner users per property and says an email group cannot be added as a user. The last column is a reading of those roles, not a Ryze AI guarantee: Google decides what each role may do.
Why Claude lists a site you cannot read
The Search Console API returns a permission level for each site it lists, and the values include siteUnverifiedUser. A site can therefore show up in a list while data requests for it fail. Ask Claude to show the permission level beside each site before you rely on one.
How Ryze AI handles several Google Search Console accounts
Ryze AI supports several Google logins per workspace, each with its own Site, and keeps clients apart in separate workspaces.
Google login
- What it is
- One Google sign-in. Add more with Add one more account; each has its own Site, and a star marks the primary
- How you switch in Claude
- The primary login is used when you name no other
Site
- What it is
- The Search Console property saved for that login after you connect it
- How you switch in Claude
- Name the property in the prompt
Agent default accounts
- What it is
- The sites the agent looks at first; the help center says it can still reach every site on that login
- How you switch in Claude
- Unnamed requests go to the defaults; name another site to move
Workspace
- What it is
- One business, with its own connections and data
- How you switch in Claude
- Name the workspace in the prompt
| Layer | What it is | How you switch in Claude |
|---|---|---|
| Google login | One Google sign-in. Add more with Add one more account; each has its own Site, and a star marks the primary | The primary login is used when you name no other |
| Site | The Search Console property saved for that login after you connect it | Name the property in the prompt |
| Agent default accounts | The sites the agent looks at first; the help center says it can still reach every site on that login | Unnamed requests go to the defaults; name another site to move |
| Workspace | One business, with its own connections and data | Name the workspace in the prompt |
The help center's rule is one workspace per business: several logins of one brand share a workspace, and separate clients belong in separate workspaces. The Search Console help page lists the Site step that every login goes through.
On the Claude side, one Ryze AI connection can cover up to 20 workspaces. To change which workspaces Claude may use, remove the Ryze AI connector in Claude, add it again and start a new chat.
Which Ryze AI plan fits
Search Console feeds the Ryze AI SEO agent, so the SEO Starter plan at $129 a month with a 3-day free trial is the natural fit. The 7 Search Console tools also work on any other active Ryze AI plan or trial, including Paid Ads at $89 a month with a 7-day free trial. Connecting the connector is free; the tools need an active plan or trial. Annual billing takes 30% off the first year.
The 7 Search Console tools Claude calls across your sites
Five tools only read, one writes and one deletes. The Ryze AI tools accept an optional connection_id.
google_search_console__listSites
- Access
- Read
- What it does with several sites
- Lists every property the connected login can access, with permission levels
google_search_console__runRawSearchAnalytics
- Access
- Read
- What it does with several sites
- Queries clicks, impressions, CTR and position for one property, by query, page, country, device, search appearance or date, up to 25,000 rows per request
google_search_console__inspectUrl
- Access
- Read
- What it does with several sites
- Checks one URL's index status in one property
google_search_console__listSitemaps
- Access
- Read
- What it does with several sites
- Lists a property's sitemaps with dates, errors, warnings and counts
google_search_console__getIndexationSummary
- Access
- Read
- What it does with several sites
- Returns a sitemap summary for a property
google_search_console__submitSitemap
- Access
- Write
- What it does with several sites
- Submits or resubmits a sitemap to one property
google_search_console__deleteSitemap
- Access
- Delete
- What it does with several sites
- Removes a sitemap from Search Console for one property; the file on the site stays
| Tool | Access | What it does with several sites |
|---|---|---|
| google_search_console__listSites | Read | Lists every property the connected login can access, with permission levels |
| google_search_console__runRawSearchAnalytics | Read | Queries clicks, impressions, CTR and position for one property, by query, page, country, device, search appearance or date, up to 25,000 rows per request |
| google_search_console__inspectUrl | Read | Checks one URL's index status in one property |
| google_search_console__listSitemaps | Read | Lists a property's sitemaps with dates, errors, warnings and counts |
| google_search_console__getIndexationSummary | Read | Returns a sitemap summary for a property |
| google_search_console__submitSitemap | Write | Submits or resubmits a sitemap to one property |
| google_search_console__deleteSitemap | Delete | Removes a sitemap from Search Console for one property; the file on the site stays |
connection_id picks a specific Google login when a workspace holds more than one. Without it, the primary login answers.
There is no tool to request indexing, remove URLs from Google or verify a property, so those steps stay in Search Console.
Name sites so Claude picks the right property
Most wrong-site answers come from two properties that look alike. Give Claude a fixed map once.
- Write the property exactly as Search Console lists it. A Domain property is sc-domain:example.com and a URL-prefix property is the full URL with a trailing slash.
- Say which login to use when two logins reach one site. Name the login's email, or say second login, so Claude can choose the matching connection.
- Name the workspace for client work. A workspace named after the client keeps its sites out of every other client's chat.
- Say the date range. Search Console reports lag by 2 to 3 days and keep up to 16 months of history, so ask for explicit dates when you compare sites.
- Ask for the property type. A URL-prefix property excludes traffic outside its prefix, so its totals differ from the Domain property for the same site.
Put the map in a Claude project
Claude projects carry instructions into every chat inside them. Paste this block once per agency or client:
6 prompts that switch or compare Search Console sites
Replace the brackets. Each prompt names its site, so it works the same in a fresh chat.
1. Map every site
- What comes back
- The properties each login can open, with permission levels. A site missing here is not reachable by your logins.
2. Switch to one site
- What comes back
- A query table for one property and one date range.
3. Compare two sites
- What comes back
- Totals from two separate property queries, side by side.
4. Check sitemaps across properties
- What comes back
- Sitemap dates, errors, warnings and counts, grouped by property.
5. Inspect one URL
- What comes back
- The URL Inspection fields for that single URL in that property.
6. Change one property only
- What comes back
- A change summary to confirm; with write tools on Needs approval, nothing runs before you approve.
| Prompt | What comes back |
|---|---|
| 1. Map every site | The properties each login can open, with permission levels. A site missing here is not reachable by your logins. |
| 2. Switch to one site | A query table for one property and one date range. |
| 3. Compare two sites | Totals from two separate property queries, side by side. |
| 4. Check sitemaps across properties | Sitemap dates, errors, warnings and counts, grouped by property. |
| 5. Inspect one URL | The URL Inspection fields for that single URL in that property. |
| 6. Change one property only | A change summary to confirm; with write tools on Needs approval, nothing runs before you approve. |
Every answer comes from your own properties, so no example numbers are shown. More Search Console workflows are in pulling Search Console data with Claude MCP.
If you run a community Search Console MCP server instead
Google offers the Search Console API, and as of November 14, 2026 we found no Search Console MCP server published by Google.
- Community servers call the same API. The open-source mcp-gsc README describes OAuth with your own Google account or a service account, a list_properties tool, and a reauthenticate tool that reruns the browser login to switch accounts. It is MIT licensed.
- With a service account, the README says to add the service account email to each Search Console property with full access. That is how one credential reaches many sites.
- You host it and manage the credentials yourself. The Ryze AI hosted connector signs in with Google OAuth and needs no key in Claude.
- Server features and star counts change often. Check the repository before you pick one.
Several third-party servers exist and we did not test them. If you work only in Claude and want one hosted connector across your logins, the Ryze AI route above needs no local setup.
Search Console API limits that matter when you query many sites
Google sets Search Console quotas per site, per user and per project, so one busy login can slow several sites.
Search Analytics, per site
- Google's limit
- 1,200
- Unit
- queries per minute
Search Analytics, per user
- Google's limit
- 1,200
- Unit
- queries per minute
URL Inspection, per site
- Google's limit
- 2,000 per day and 600 per minute
- Unit
- queries
Other resources, per user
- Google's limit
- 20 per second and 200 per minute
- Unit
- queries
| Quota | Google's limit | Unit |
|---|---|---|
| Search Analytics, per site | 1,200 | queries per minute |
| Search Analytics, per user | 1,200 | queries per minute |
| URL Inspection, per site | 2,000 per day and 600 per minute | queries |
| Other resources, per user | 20 per second and 200 per minute | queries |
Numbers come from Google's usage limits page, which also notes that Search Analytics cost grows with date range and with grouping or filtering. The Ryze AI tool returns up to 25,000 rows per request; more rows need pagination.
Keep changes inside the right property
Only 2 of the 7 tools change anything, but with many properties in one chat a sitemap change can land on the wrong site.
- In Claude, open Customize, Connectors, Ryze AI, Tool permissions and set write and delete tools to Needs approval (Ryze AI help). Read tools keep running on their own.
- In the Ryze AI chat, Tool approvals starts on Skip all approvals and can be switched to Approve write & delete or Manual approve. Scheduled tasks run without an approval step.
- Give analysts the Restricted user role in Search Console, so Google limits what their login can do.
- Ask Claude to repeat the property and the sitemap URL before each change, as in prompt 6. Removing a sitemap only removes it from Search Console.
Troubleshooting: missing sites, wrong login, stale tool list
Match what you see to the row.
A site is missing from the list
- Cause
- The connected logins cannot open that property
- Fix
- Add the right Google account as a user in Search Console, or connect that login with Add one more account
The Google Search Console card shows Require setup
- Cause
- No Site has been saved for that login yet
- Fix
- Open the card, check the Site and click Save
Data for a listed site fails
- Cause
- The login only has an unverified or restricted level on that property
- Fix
- Ask for the permission level in Search Console, or use a login with a higher role
Numbers differ from Search Console for the same site
- Cause
- A URL-prefix property was queried instead of the Domain property, or the date range differs
- Fix
- Name the exact property and the dates
Recent days look empty
- Cause
- Google reports Search Console data with a 2 to 3 day delay
- Fix
- End the date range 3 days back
Claude does not offer Search Console tools
- Cause
- The connector was added before Search Console was connected
- Fix
- Remove the Ryze AI connector in Claude, add it again and start a new chat
Claude cannot see a workspace
- Cause
- The workspace was not ticked on the Allow connection page
- Fix
- Remove and re-add the connector and tick it
| What you see | Cause | Fix |
|---|---|---|
| A site is missing from the list | The connected logins cannot open that property | Add the right Google account as a user in Search Console, or connect that login with Add one more account |
| The Google Search Console card shows Require setup | No Site has been saved for that login yet | Open the card, check the Site and click Save |
| Data for a listed site fails | The login only has an unverified or restricted level on that property | Ask for the permission level in Search Console, or use a login with a higher role |
| Numbers differ from Search Console for the same site | A URL-prefix property was queried instead of the Domain property, or the date range differs | Name the exact property and the dates |
| Recent days look empty | Google reports Search Console data with a 2 to 3 day delay | End the date range 3 days back |
| Claude does not offer Search Console tools | The connector was added before Search Console was connected | Remove the Ryze AI connector in Claude, add it again and start a new chat |
| Claude cannot see a workspace | The workspace was not ticked on the Allow connection page | Remove and re-add the connector and tick it |
Ryze AI causes come from the Search Console help page. Other multi-account guides: Google Analytics and Google Ads. The Search Console tool page is Google Search Console MCP, and all setups are in Ryze AI integrations.
Sources
Checked November 14, 2026
- Search Console Help: Manage users, owners and permissions
- Search Console Help: Add a website property
- Search Console Help: Verify your site ownership
- Search Console API: Sites resource (permission levels, siteUrl formats)
- Search Console API: Usage limits
- GitHub: AminForou/mcp-gsc README (community server)
- Claude Help Center: Custom connectors using remote MCP
- Claude Help Center: What are projects
- Ryze AI Help: Connect Google Search Console
- Ryze AI Help: Connect multiple accounts
- Ryze AI Help: Permissions and approvals in Claude
- Ryze AI Help: Claude connector FAQ
- Ryze AI Help: Plans and pricing
The verdict
Settle access in Search Console first: every property you want Claude to read needs a Google login with a role on it. Then connect each login to one Ryze AI workspace, set a primary login and default accounts, and name the exact property in every prompt.
Frequently asked questions
How do I connect multiple Google Search Console accounts to Claude?
Does Search Console have a manager account like Google Ads?
Can I connect several Google logins to one Ryze AI workspace?
How does Claude know which Search Console site to use?
Show 8 more questionsShow fewer questions
Should I use a Domain property or a URL-prefix property?
Can Claude compare two Search Console sites in one chat?
Can one Claude connection cover several clients?
Why is a site missing from the list Claude shows?
Can Claude request indexing or verify a property?
How do I stop Claude changing the wrong property?
Which Ryze AI plan do I need for Search Console in Claude?
Does this work on the free Claude plan?
Related guides
How to connect Claude to Google Search Console
The single-login setup for claude.ai, Desktop and Code, screen by screen.
Google Search Console MCP server
The 7 Ryze AI Search Console tools, with setup per client.
Connect multiple Google Analytics accounts to Claude
The same multi-account setup for GA4 properties.
Connect multiple Google Ads accounts to Claude
Manager accounts, access levels and account naming for Google Ads.




