Search Console MCP: Connect GSC to Claude
TL;DR: ARLO is an MCP server that gives Claude live, read-only access to Google Search Console through the Search Analytics API. Connect once with Google OAuth, assign a property to a client, and Claude can answer questions about clicks, impressions, CTR, and average position by query or page — nothing is exported, warehoused, or scheduled.
Why connect Search Console to Claude instead of digging through the GSC UI
Search Console's Performance report is powerful but slow to work with: you pick a date range, filter by query or page, then export to compare periods by hand. Most agencies re-run the same checks every week — which queries gained or lost clicks, whether a page's average position moved, which URLs dropped out of the index. An MCP connector skips the UI: Claude calls the Search Analytics API directly, so "which queries lost the most clicks this month" becomes a sentence instead of a manual comparison across two exported CSVs.
Connect Search Console in 3 steps
Connect Google
Sign in to ARLO and grant Google OAuth once. The same grant also unlocks GA4, Google Ads, YouTube, and Business Profile — no separate Search Console-only integration to configure.
Assign the Search Console property
Pick the verified property from a searchable dropdown for each client or business you track. Multi-client agencies assign as many properties as they have Search Console access to.
Paste your MCP URL into Claude Desktop
ARLO generates a personal MCP URL. Add it under Claude Desktop → Settings → Connectors and Search Console shows up as a tool Claude can call.
Things to ask Claude once Search Console is connected
- “How did clicks and impressions trend for [Client] over the last 28 days?”
- “Which queries lost the most clicks compared to last month?”
- “What's the average position for [Client]'s top 10 landing pages?”
- “Break down this month's Search Console clicks by device.”
- “Which pages have high impressions but a low click-through rate?”
What Claude can query from Search Console
Metrics
- ✓Clicks — Times a user clicked through from search results
- ✓Impressions — Times a URL appeared in search results
- ✓CTR — Click-through rate — clicks divided by impressions
- ✓Position — Average ranking position for a query or page
Dimensions
- ✓Query — The search term that triggered the impression
- ✓Page — The specific URL that appeared in results
- ✓Country — Where the search took place
- ✓Device — Desktop, mobile, or tablet
- ✓Date — Trend and period comparisons
- ✓Search appearance — Rich result type (e.g. FAQ, video, AMP)
Frequently Asked Questions
Is this Google's official Search Console MCP server?+
No. ARLO is a third-party MCP connector built on the public Search Console Search Analytics API. It requires you to grant OAuth access to your own verified properties — it isn't an official Google product.
Do I need to know the Search Console API to use this?+
No. You ask Claude in plain English; ARLO translates the request into the correct Search Analytics API call and returns the numbers Claude uses to answer you.
Is my Search Console data stored anywhere?+
No. ARLO is pass-through — each query fetches live data from Search Console and returns it to Claude for that one response. Nothing is warehoused or cached long-term.
Can I connect Search Console for more than one client?+
Yes. One Google OAuth grant per team member covers every verified property you assign. Add a client, pick their property from the dropdown, and Claude can query it immediately.
Does this cover URL Inspection or indexing status?+
Not yet. Today's connector covers Search Analytics data — clicks, impressions, CTR, and position by query, page, country, device, and date. URL Inspection is not currently supported.