Does every team member need their own Google Search Console account?

No. One Google sign-in in Loopthink covers the whole team, and it is the only Google account involved. Your people sign in to Loopthink with their own identity, every call is logged under their name, and the seats in Google Search Console stay exactly where they are today.

Who has to add the connector in Claude?

One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.

Where does the Search Console key live?

There is none, and that is the point. A Google sign-in grants Loopthink read access, which is stored encrypted in the EU, is never returned by the API and never reaches Claude or the people using the connector. You revoke it any time at myaccount.google.com/permissions, and nobody has to rotate or paste anything.

Can somebody submit or delete a sitemap from the chat?

No, and not because a switch is off. The sign-in asks for the read-only Search Console scope, so Google itself refuses the write methods, and the connection publishes no write tools either. Both limits would have to fail at once.

Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.

We already run our own MCP server for Google Search Console. Does it still work?

Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

Google Search Console · Claude

Google Search Console in Claude. In five minutes.

Start free See the steps

Free for 2 connectors, no card · Pro €19 · EU-hosted

ClaudeGoogle Search Console

“Which pages lost the most clicks in the last 28 days?”

Used site_acme_com_search_analytics from Google Search Console

Three pages are down against the 28 days before:

Page	Clicks	Change	Position
/pricing	412	−118	8.8
/blog/rollout-guide	268	−74	11.3
/integrations	197	−53	7.4

read-only
logged

“And which queries drove /pricing?”

Top five queries for /pricing, with clicks and position:

Query	Clicks	Position
acme pricing	138	1.2
acme cost	74	2.8
acme vs northwind	51	4.1
acme free plan	39	3.6
acme enterprise price	22	6.9

QUERY dimension enabled by admin

How to connect

Three steps. The third one is asking.

1
Sign in with Google
Pick the properties your team may see. Read-only scope, nothing else.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which pages lost the most clicks in the last 28 days compared with the 28 before?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
Start with a workspace in Loopthink. Its servers, its members and its key are separate from every other one.
2
Add a server and pick Google Search Console as its connection.
3
Press Connect Google account.
4
Sign in with Google. The consent screen asks for the Google Search Console scope and nothing else.
5
Tick the accounts or properties your team may report on. Each one publishes its own read-only tools.
6
Copy the workspace connector URL.
7
In Claude, open Settings, then Connectors, then Add custom connector.
8
Give it a name your colleagues will recognise, Acme Group rather than Loopthink, and paste the URL. Those two fields are the whole form.
9
Continue opens a page of options. Scroll down past it and change nothing: Claude has already read the server, so the sign-in and the OAuth client are detected and chosen for you, and there is no client id, no secret and no request header to type. Press Add at the bottom.
10
Each colleague connects once with their own account, toggles it on in a chat, and asks. Every call runs as them, with their role, and lands in the audit log.

Steps checked against the vendor documentation on 17 September 2026: Search Console API reference · Search Analytics query · Users and permissions · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Use cases

What people actually ask Claude about Google Search Console.

SEO
“Which pages lost the most clicks in the last 28 days compared with the 28 before?”
Content
“How did the blog perform last month, by page and country?”
Management
“Clicks and impressions this month versus last month, by country?”

Why Loopthink

Search Console has no Google MCP server. Why Loopthink?

Google has no MCP server for Search Console. The community ones put one login or a key file into every colleague's config file, and they carry the sitemap writes along with the reports.

Loopthink runs hosted and gives Claude a URL. Every colleague signs in with their own account and sees only what you ticked.

FAQ

Before you connect.

Does every team member need their own Google Search Console account?: No. One Google sign-in in Loopthink covers the whole team, and it is the only Google account involved. Your people sign in to Loopthink with their own identity, every call is logged under their name, and the seats in Google Search Console stay exactly where they are today.
Who has to add the connector in Claude?: One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
Where does the Search Console key live?: There is none, and that is the point. A Google sign-in grants Loopthink read access, which is stored encrypted in the EU, is never returned by the API and never reaches Claude or the people using the connector. You revoke it any time at myaccount.google.com/permissions, and nobody has to rotate or paste anything.
Can somebody submit or delete a sitemap from the chat?: No, and not because a switch is off. The sign-in asks for the read-only Search Console scope, so Google itself refuses the write methods, and the connection publishes no write tools either. Both limits would have to fail at once.
What does it cost?: Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.
We already run our own MCP server for Google Search Console. Does it still work?: Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

When colleagues join

One matrix for Google Search Console. Roles across, tools down.

Tool	SEO	Content	Management
List properties	SEO may use List properties	Content may use List properties	Management may use List properties
Performance per property	SEO may use Performance per property	Content may use Performance per property	Management may use Performance per property
Sitemaps per property	SEO may use Sitemaps per property	Content may not use Sitemaps per property	Management may not use Sitemaps per property
Search terms (QUERY)	SEO may use Search terms (QUERY)	Content may not use Search terms (QUERY)	Management may not use Search terms (QUERY)
Write actions off by default	SEO may not use Write actions	Content may not use Write actions	Management may not use Write actions

Masked for every role: search queries, the text real people typed, until an admin enables the QUERY dimension on the connection.

You set this once. Every Claude user in your team gets exactly this.

Google Search Console runs on the free tier: two connectors for one person, no card. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans