How to connect Google Search Console to Claude

Why connect Search Console to Claude?

Without an integration, Claude cannot see your private Search Console performance reports. It can suggest an SEO checklist, but it cannot reliably tell you which of your pages lost clicks yesterday or which search terms have the biggest opportunity.

A Search Console connector brings your permitted search data into the conversation. Instead of exporting a CSV for each question, you can ask for a comparison, request the underlying pages and queries, and follow up on anomalies.

This works best for questions such as:

• Which pages lost the most Google Search clicks over the last 28 complete days?
• Which high-impression queries sit outside the top three positions?
• Did traffic drop on mobile only, or across devices?
• Which URLs need an indexing-status check?

Important: Google Search Console measures appearances and clicks in Google Search. It does not, by itself, tell you what visitors did after arriving. For conversions and sessions, use Google Analytics 4 as well.

What you need before starting

1. A Google account with access to at least one verified Search Console property.
2. A Claude account whose connector controls are available to you.
3. An accessible remote MCP endpoint and the credentials required by that service.

Claude’s custom connector documentation lists support across Free, Pro, Max, Team and Enterprise; Free accounts have a limit on the number of custom connectors. On managed workspaces, an administrator may need to add the connector first.

GSC Magic is designed to connect search tools to AI assistants. If the GSC Magic service is still on the waitlist, you can join at GSC Magic and use the setup steps when access opens; don’t expect the endpoint to authenticate before your account has been provisioned.

Connect Claude on the web or desktop

1. Open Claude and navigate to Customize → Connectors. Depending on your version, connector management may also appear under account or organization settings.
2. Choose Add custom connector. For a managed workspace, ask its owner to add the connector to the organization first.
3. Name it GSC Magic and enter the remote MCP URL: https://gscmagic.com/mcp.
4. Follow the authentication options shown by Claude. Approve only the permissions you understand; never paste an API secret into a normal chat message.
5. Open a conversation, enable the connector under the available connector/tool controls, and ask it to list the Search Console properties it can access.

The connection should be tested with a simple read-only request before you ask for a large report. If the list is empty, check the Google account used during authorization and whether that account has access to the selected property.

Connect from Claude Code

Claude Code supports remote HTTP MCP connections. In a terminal, run:

claude mcp add --transport http gsc-magic https://gscmagic.com/mcp

Then use /mcp inside Claude Code to inspect the connection and complete authorization where supported. The MCP server must be reachable and operational, and your access must be enabled.

If you prefer to work entirely in a browser, the web connector route above is simpler. A command-line connection is more useful when your SEO work is part of a development workflow.

Three useful first prompts

Treat thresholds as starting points, not universal SEO rules. A small site may need a lower impression threshold. For a larger site, make it higher. Ask the assistant to show its date range and numbers, not only its recommendations.

For more ideas, read 25 SEO prompts for AI agents or the guide to finding low-CTR queries.

Troubleshooting: common connector problems

An official Claude connector guide is a useful reference if menu labels change.

A complete first audit you can run in Claude

Once the MCP connection is available and authorized, start with one narrowly defined project instead of asking the assistant to “fix my SEO.” The following exercise creates a baseline you can revisit after making changes.

Step 1 — Select the property. Ask Claude to list properties the connector exposes. Choose the exact URL-prefix or domain property you intend to analyze. A domain property may cover subdomains that a URL-prefix property does not, so this choice affects reported totals.

Step 2 — Choose comparable periods. Request the latest 28 complete reporting days versus the 28 days immediately before. Ask Claude to state the start and end dates in the answer.

Step 3 — Identify the size of the change. Request total clicks, impressions and CTR for each period. Have the assistant calculate both the absolute and percentage change, using the previous period as the percentage denominator.

Step 4 — Find the pages that matter. Sort URLs by clicks lost, not merely by the largest percentage decline. A page falling from 3 clicks to 1 lost 67%, but a page falling from 900 to 650 lost 250 clicks.

Step 5 — Investigate one page. For the largest loss, ask for its top changed queries, device split and country split. A mobile-only decline should trigger different checks from a decline in both mobile and desktop search.

Step 6 — Write an action log. Save three items: the observed change, a hypothesis to test and a metric that would indicate improvement. Do not let the model present an unverified cause as a fact.

You can repeat this exercise each month. The resulting table also gives you a baseline for the traffic-drop investigation checklist.

Security and permissions: what to verify before authorizing

An MCP connector acts as a bridge between the assistant and a remote service. Read its requested permissions and confirm which operations the assistant is allowed to perform. For reporting-only tasks, prefer the least access necessary.

• Property access: verify that the Google account can view the intended Search Console property; personal and work Google accounts frequently differ.
• Tool scope: distinguish reading search reports from submitting sitemaps or URLs to external services.
• Sensitive outputs: a query report can include confidential product names or unreleased pages. Decide whether that information is appropriate to share with the AI service you use.
• Organization control: if you are working in a company workspace, follow its security and admin approval process before enabling any custom connector.
• Revocation: know how to disconnect a connector or revoke its granted access if you no longer need it.

These checks apply whether you connect Claude through GSC Magic or a different MCP server. An AI response should remain auditable: you should be able to trace a recommendation back to its property, dimensions and date range.

Claude + Search Console: frequently asked questions

Can I use the connector with Claude Free?

Anthropic’s remote MCP connector guide currently lists Free plan support, with a limit of one custom connector. The MCP service you connect to may have its own account and access requirements.

Will Claude know which Google website is mine?

Only if the authorized connection returns it or you provide the property identifier. Always confirm the selected property before asking for comparative metrics.

Does a Search Console connector show conversions?

Not by itself. Search Console reports search performance; conversion and key-event analysis requires a source such as GA4. See GSC clicks versus GA4 sessions.

Can I ask Claude to index my blog posts?

Claude can help interpret Search Console data if the connector exposes the necessary tools. Google’s general URL Inspection API is not a request-indexing endpoint. Use Search Console’s own supported indexing workflows where applicable.

What to do after connecting

Start with a baseline: the last 28 complete days, compared with the preceding period. Segment by page or query only after identifying where the change occurs. That prevents broad site averages from hiding the actual problem.

Next, use the workflow in finding keyword cannibalization or diagnosing an organic traffic drop.

Want this workflow without building your own API client? Explore GSC Magic and join the early-access list.