A Claude Search Console connector helps investigate an organic traffic change without relying on a screenshot of a single chart. It can retrieve page and query data, narrow a question and retain the property and date context. This guide focuses on explaining a click decline with evidence rather than assigning a cause too early.
What do you need before connecting?
Use Claude on the web or Claude Desktop with connector access allowed for your account. Organization controls may require an owner to add the connector before members connect individually. This guide covers Claude's connector interface; Claude Code's terminal configuration is a separate route.
- A Google login with access to the Search Console property you intend to query.
- A LoomaScale account with Google Search Console connected; a GA4 connection does not grant Search Console access.
- The exact property returned by discovery: a domain property such as sc-domain:example.com or a URL-prefix property such as https://www.example.com/.
How do you connect Claude to GSC?
1. Connect GSC in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Search Console, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Connect the LoomaScale directory connector
Open LoomaScale in Claude's connector directory and choose Connect to Claude. Use the existing full connector for access to this Google service alongside your other connected sources. LoomaScale is listed in the directory; that listing should not be read as a claim that Anthropic verified its analysis.
3. Authorize LoomaScale and enable its tools
Sign in to the LoomaScale account that holds your Google connection and complete authorization. In Claude, open Customize → Connectors and confirm LoomaScale is connected. Enable it for your conversation through + → Connectors, then request an account lookup by name. For a service-specific custom connection, use + Add → Add custom connector, enter the endpoint below and complete the detected OAuth flow. Team and Enterprise owners manage organization-level connector availability.
4. Verify access with an actual account lookup
Use LoomaScale to call gsc_list_sites. List my Search Console properties with their exact site URLs and permission levels. Ask me which property to use. Do not guess a domain or submit anything to Google.
Match the returned property to the site you manage. A domain property and a URL-prefix property can cover different URL sets, so keep the exact returned identifier. After selection, request a small performance report with explicit dates and search type. Check the actual tool result before interpreting a table: an explanation of Search Console without a tool call is not a connection test.
How do you investigate a search click decline in Claude?
Compare equivalent periods using the same search type and property. Find the pages with the largest absolute click losses, then ask which queries and devices account for those losses. Keep changes in impressions, CTR and position separate: each points toward different follow-up questions and none alone proves a search algorithm penalty.
Use LoomaScale for the selected Search Console property. Compare the latest 28 complete days with data against the previous equivalent period for web search. Show the five pages with the largest absolute click losses, their impressions, CTR and average position in both periods. For each, inspect contributing queries and devices. State dates and filters, flag incomplete data and distinguish observations from explanations. Do not change or submit anything.
A page losing clicks because impressions fell needs a different investigation from a page with stable impressions and lower CTR. Ask Claude to show the source rows for each explanation. Check seasonality, site changes and the actual search results before acting. This workflow measures Google's search performance data and does not measure citations from AI assistants.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/gscThe service-specific endpoint exposes GSC tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Claude read or change in GSC?
LoomaScale's Search Console tools retrieve organic clicks, impressions, CTR, average position, query and page opportunities, sitemap status and Google's indexed URL-inspection result. When you ask in chat, they can also submit, resubmit or delete a sitemap and add or remove a property in your Search Console list; removing a property needs explicit confirmation, and an added property stays unverified until you verify it in Search Console. They cannot request indexing or change a website's content. Connections made before November 16, 2026 need a reconnect to grant the write permission. Performance rows describe Google Search visibility, while GA4 sessions describe measured visits. Google's Search Analytics API returns leading rows within its limits and does not guarantee every data row; a missing query is not proof that it received no searches.
Why is the connection or data missing?
If Claude does not call a tool, enable the connector for the conversation and name LoomaScale explicitly. If new tools are missing, open its connector page and use Refresh tools list; the Claude refresh guide shows the menu. A refreshed list cannot grant access to a missing Google property or bypass an organization restriction.
For a missing site, check the connected Google email and Search Console access. For unexpected totals, keep the same property, dates, filters and search type as the interface you compare with. Recent data may be incomplete; name the period you used. URL Inspection reports Google's stored index view, rather than a new browser crawl of the current page. A successful connection does not improve rankings or cause a page to be indexed.
Related connection guides and official references
Use GSC in another assistant
- How to Connect ChatGPT to GSC
- How to Connect Codex to GSC
- How to Connect Claude Code to GSC
- How to Connect Grok Build to GSC
Connect another Google source to Claude
Official setup references
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
