Google Search Console MCP Server: Connect GSC to Claude AI

Google Search Console shows you how Google sees your site. Rankings. Impressions. Click-through rates. Which queries bring traffic. Which pages perform well.

But GSC's interface makes analysis tedious. Want to find queries where you rank on page 2? That's manual filtering. Want to compare CTR across page types? Export to spreadsheet. Want to identify quick SEO wins? Start clicking.

The Google Search Console MCP server connects your GSC data directly to Claude AI. Ask SEO questions in plain English. Get answers from your actual search performance data.

"What queries have high impressions but low CTR?" Just ask.

What Is the Google Search Console MCP Server

The Google Search Console MCP server uses Model Context Protocol to give Claude direct access to your GSC property.

MCP is an open standard from Anthropic that connects AI to external data sources. Instead of navigating GSC's interface and exporting reports, you ask Claude questions. Claude queries your data and provides analysis.

For SEO professionals and content teams, this means faster insights without the manual work.

What Data You Can Access

The Google Search Console MCP server pulls comprehensive search performance data.

Query Performance:

Search queries triggering impressions
Clicks and click-through rate by query
Average position by query
Impressions by query

Page Performance:

URLs receiving search traffic
Clicks, impressions, CTR by page
Average position by page
Top queries for each page

Dimensional Breakdown:

Performance by country
Performance by device (mobile, desktop, tablet)
Performance by search appearance (rich results, etc.)

Position Data:

Ranking distribution
Position changes over time
Queries close to page 1

Technical Insights:

Coverage issues (what GSC reports)
Indexing status references

Use Cases

Find Quick-Win Keywords

The fastest SEO wins come from queries where you almost rank on page 1. A small improvement yields big traffic gains.

Ask Claude: "What queries have average position between 8 and 15 with at least 100 monthly impressions? These are my quick-win opportunities."

Let Claude identify keywords where a ranking boost would drive real traffic.

Diagnose CTR Problems

High impressions but low clicks means your title tags and meta descriptions aren't compelling.

"Which pages have above-average impressions but below-average CTR? Show me the queries they rank for."

Find pages where better titles could capture more clicks.

Track Position Changes

SEO is a long game. Understanding what's improving or declining helps prioritize effort.

"How have my rankings changed over the last 90 days? Which pages gained the most positions? Which lost ground?"

Claude can surface trends that manual analysis would miss.

Content Gap Analysis

GSC shows what queries already bring traffic. But the data also reveals content opportunities.

"What queries am I ranking for where I don't have dedicated content? These might be topics worth expanding."

Identify content gaps based on actual search demand.

How to Set Up

Setting up the Google Search Console MCP server takes about 10 minutes.

Step 1: Set Up Google Cloud Access

Create a Google Cloud project (or use existing). Enable the Search Console API.

Step 2: Create Service Account

Create a service account and download the JSON credentials file.

Step 3: Grant GSC Access

In Search Console, go to Settings > Users and permissions. Add the service account email as a user with Full access.

Step 4: Note Your Property

Copy your Search Console property URL exactly as it appears (including http/https and trailing slashes if present).

Step 5: Install and Configure

Install the Google Search Console MCP server. Configure with your service account credentials and property URL.

Step 6: Connect to Claude

Add the server to your Claude configuration and test with a query about your top keywords.

Example Queries

Once connected, you can ask Claude:

"What are my top 10 queries by clicks this month?"
"Which pages have the best CTR? What makes them different from low-CTR pages?"
"Show me queries where I rank positions 4-10. These are candidates for optimization."
"How does my mobile performance compare to desktop? Am I losing clicks on mobile?"
"What queries have declining impressions over the last 30 days? Could indicate dropping rankings."
"Which new pages started ranking in the last 90 days? Are they gaining traction?"

SEO-specific questions get SEO-specific answers.

Common Questions

How far back does the data go?

Google Search Console stores 16 months of data. The MCP server can query anything within that window.

Is the data real-time?

GSC data has a 2-3 day delay. This is a Google limitation, not the MCP server. For position tracking, this delay is normal.

Can I see which pages aren't indexed?

The MCP server focuses on search performance data (queries, clicks, impressions, positions). Coverage and indexing data may have limited availability through the API.

Can I compare multiple properties?

If you configure access to multiple GSC properties, you can ask Claude to compare search performance across different sites.

Does this work with domain properties?

Yes. The MCP server works with both URL-prefix properties and domain properties in Search Console.