Skip to main content
Læs siden på dansk The Google Search Console connector gives your AI read-only access to your properties in Search Console. Ask in natural language about search queries, clicks, impressions, CTR, positions and trends over time, compare periods, and dig into a single page or a single query. You approve Consile via Google’s own consent screen, and your AI never sees the access itself.
100% read-only. All seven tools are read tools, and the connector asks for only one scope: webmasters.readonly. It cannot submit sitemaps, request indexing or change any setting in Search Console.

Access

Read-only (webmasters.readonly)

Authentication

Google OAuth

Hosting

Hosted in the EU · Frankfurt
  • Price: 249 DKK/month excl. VAT (€29/month if you have chosen the EU · EUR market in the portal). The price covers 1 user and 1 agreement (one connected Google account). Each extra user and each extra agreement costs 124.50 DKK/month excl. VAT (€14.50). No lock-in, cancel at any time. Also included in the Consile Studio membership and the free edition. See Pricing.
  • Endpoint: https://mcp.consile.ai/gsc/mcp (your own named connector in Claude).
Multiple Google accounts and websites. The portal calls each connection to the system an agreement. One agreement covers all the properties your Google account has access to. You add one more agreement if you also want to fetch data from another Google account, or if each website should have its own connection, locked to exactly that website (see the section on locking below). An administrator clicks Add agreement on the Connections card on the connector’s page (124.50 DKK/month excl. VAT per extra agreement) and then Connect next to the new agreement. Each agreement gets its own MCP address, for example https://mcp.consile.ai/gsc-2/mcp, which you add in Claude as a separate connector. Only administrators can add and remove agreements. Under the Consile Studio membership there is no button to add an agreement, so write to support@consile.dk instead. See Multiple Google accounts and websites.

​
Prerequisites

1

Subscription

The connector must be bought in the portal. See Buy a connector.
2

Google approved

Approve Consile via Google’s consent screen with an account that has access to at least one verified Search Console property. The connection applies to your whole Consile account. See Connect Google Search Console.
3

Access for your user

If there are several users on the account, an administrator must assign you Google Search Console under Team in the portal. Whoever bought the connector has access from the start. Without assigned access, the connector refuses your calls. If you have created your own Consile account, but belong to a company that already has the connector, ask your administrator for an invitation to the team instead of buying again. If you have the Consile Studio membership, an administrator instead gives one membership licence per person, and it also covers Google Search Console. See Team.
4

Claude connected

Each user adds the connector in their own Claude and logs in with their own Consile login. This can be done before or after Google is connected. See Connect Claude.

​
What can it do? (tools)

You do not need to know the tool names. You just ask in natural language, and your AI picks the right tool itself. Here are the seven read-only tools the connector provides:

Building on top yourself? See the API reference

Full reference with arguments, return values and JSON examples for each of the seven tools.

​
Try asking

“Which search queries got the most clicks in the last month?”
“Which search queries have high impressions but low CTR? Where is the potential?”
“How have clicks developed on my website over the last 90 days?”
“Compare the last 28 days with the period before. What went up and what went down?”
“Which search queries drive traffic to my home page?”
“How has my average position for ‘consulting’ developed over time?”
Mention the specific property (for example your domain) and a period in your question, and the answer gets more precise. Properties are given as a URL prefix (https://www.example.com/) or a domain property (sc-domain:example.com); list_sites shows the valid values.

​
Lock to one company

A Google account can have access to many websites in Search Console. An administrator can lock an agreement to one website (one property), so every call on that agreement keeps to it. The lock is optional. Without a lock, the connection works as before, and your AI chooses the property in each call. On a locked connection:
  • list_sites only shows the locked property.
  • The six other tools still need a property (siteUrl), and it must be the locked one. If your AI names another property, the call is refused, and your AI is told which property the connection is locked to.
  • No tools are hidden. All seven are still there.
  • A property with a URL (https://example.com/) and a domain property (sc-domain:example.com) are two different properties. The connection only answers for the one it is locked to.
If an administrator connects the agreement again with Reconnect or a link from your AI, all calls are refused until an administrator has chosen the property again. If an administrator disconnects, the lock disappears. A property can only be locked on one agreement at a time. How to lock, and what else happens: Lock a connection to one company.

​
Limitations

  • Read-only: the connector cannot submit sitemaps, request indexing or change settings in Search Console. This is enforced both in the tools and at the approval itself: if Google grants scopes other than exactly webmasters.readonly, the connection is refused.
  • Only search performance: the connector reads the list of properties and Search Analytics data (clicks, impressions, CTR and position). URL inspection, indexing status, sitemaps and Core Web Vitals are not included.
  • Only your own properties: your AI can only see the properties your approved Google account already has access to. list_sites shows the access level (permissionLevel) per property, and only properties you are verified for return data. If the agreement is locked, your AI only sees the locked property.
  • Data is not real time: Google finalizes Search Console data with a delay of a couple of days. The fixed tools only use finalized data for regular web search. If you want the newest, preliminary figures or data for images, video, news or Discover, ask your AI to use search_analytics_query.
  • Dates and number of rows: dates must be YYYY-MM-DD, and each call fetches at most 25,000 rows (Google’s own limit). top_queries and top_pages fetch 10 by default.
  • The access can stop: Consile renews the access at Google automatically. If you revoke the access at Google, the connector stops working, and your AI gets a message that Search Console must be connected again. The portal can still show the connector as Connected. Only an administrator can reconnect: if the agreement says Access revoked, click Reconnect. Otherwise the administrator chooses Disconnect in the menu next to the agreement and then clicks Connect. You can also ask your AI for a new connection link in the connector that belongs to the agreement (for example gsc-2). If the agreement was locked, an administrator must choose the property again afterwards. See Connect Google Search Console.
Is something not working as expected? See Troubleshooting.