Google Search Console MCP Server — 10 AI Tools

Google Search Console MCP ServerGoogle Search Console MCP server with 10 ready-to-use AI tools. Connect Google Search Console to Claude, ChatGPT, Gemini, or any MCP-compatible AI assistant. Cloud MCP connector — no install, no Docker, works from any browser.Category: Marketing & SEO. 10 tools available. Authentication: OAuth.Your search performance, analyzed by AIWhy Google Search Console + AI?Google Search Console has all the data you need to improve your SEO — but navigating the interface, building custom date comparisons, and identifying optimization opportunities takes time. Let your AI assistant query your search data, find quick wins, and monitor indexing issues through natural conversation.Example prompts you can send your AI about Google Search Console

Ask: "Show my top keywords by impressions this month and find quick wins"
AI does: AI queries your search analytics, ranks keywords by impressions, identifies queries in positions 4-10 with low CTR, and calculates potential additional clicks if you optimize your title tags and meta descriptions.

Ask: "Check if my new blog post is indexed and look at its search performance"
AI does: AI inspects the URL in Google's index, reports crawl status and mobile usability, then queries analytics for the page to show clicks, impressions, and ranking queries.

Ask: "Compare my search traffic this week vs last week by device type"
AI does: AI runs two analytics queries with date and device dimensions, then presents a comparison showing changes in clicks, impressions, CTR, and average position across desktop, mobile, and tablet.

Featured Google Search Console Tools

search_analytics: Query Google Search Console search analytics data. This is THE primary tool for understanding how your site performs in Google Search. Returns clicks, impressions, CTR (click-through rate), and average position for your pages and queries. WHEN TO USE: This is the most important GSC tool. Use it when the user asks about: - Search performance: "how is my site doing in Google?", "show my search traffic" - Top queries: "what keywords bring traffic?", "top search queries last month" - Page performance: "which pages get the most clicks?", "how does /blog perform?" - Country/device breakdown: "traffic by country", "mobile vs desktop clicks" - Trend analysis: "compare this month vs last month", "daily click trend" - Specific page analysis: "how does example.com/pricing rank?", "queries for my blog" - Content gaps: "high impression low CTR queries" (use detect_quick_wins for this) DIMENSIONS EXPLAINED: - query: Search terms users typed (most common dimension) - page: URLs that appeared in search results - country: Three-letter country code (USA, GBR, DEU, etc.) - device: DESKTOP, MOBILE, or TABLET - date: Daily breakdown (use with startDate/endDate for trends) - searchAppearance: Rich result types (AMP, RICH_RESULT, etc.) FILTERS: Use pageFilter/queryFilter/countryFilter/deviceFilter to narrow results. The filterOperator applies to pageFilter and queryFilter (default: "contains"). AGGREGATION: "auto" (default) groups by property, "byPage" groups by page, "byProperty" by entire property. DATA FRESHNESS: dataState="all" includes fresh (incomplete) data; "final" is only fully processed data (2-3 day delay). LIMITS: Max 25,000 rows. Use startRow for pagination. Date range max ~16 months back. STEP-BY-STEP — Analyze top queries: 1. Call search_analytics with dimensions=["query"], startDate="2026-02-01", endDate="2026-02-28". 2. Review clicks, impressions, CTR, and position for each query. EXAMPLES: "Top queries this month" → dimensions=["query"], startDate/endDate for current month "Traffic by page" → dimensions=["page"] "Daily click trend" → dimensions=["date"] "Mobile traffic for /blog" → dimensions=["device"], pageFilter="/blog" "Queries for my pricing page" → dimensions=["query"], pageFilter="/pricing"

detect_quick_wins: Find SEO "quick win" opportunities — pages ranking on page 1-2 of Google (positions 4-10) with high impressions but low CTR. These are pages that Google already considers relevant but aren't getting clicked, meaning small improvements to titles, meta descriptions, or content could dramatically increase traffic. WHEN TO USE: User asks about: - "Find SEO opportunities", "quick wins for my site" - "Low-hanging fruit keywords", "easy traffic gains" - "Pages with high impressions but low clicks" - "What should I optimize first?" - "Content optimization priorities" HOW IT WORKS: Queries search_analytics with dimensions=["query", "page"], then filters for rows matching: 1. Impressions >= minImpressions (default: 50) — enough visibility to matter 2. CTR <= maxCtr% (default: 2.0%) — underperforming click-through rate 3. Position between positionRangeMin and positionRangeMax (default: 4-10) — already ranking well Results are sorted by impressions descending (highest impact first). ACTIONABLE OUTPUT: For each opportunity, consider improving the page title, meta description, or adding structured data to make the search result more compelling. EXAMPLES: "Find quick wins for my site" → use defaults "Find high-impression low-CTR queries" → adjust maxCtr if needed "Opportunities in positions 5-15" → positionRangeMin=5, positionRangeMax=15

inspect_url: Inspect a URL's indexing status in Google Search. Returns detailed information about how Google sees a specific page: whether it's indexed, crawl status, mobile usability, rich results eligibility, and the canonical URL Google selected. WHEN TO USE: User asks about: - "Is my page indexed?", "why isn't my page showing in Google?" - "Check indexing status for this URL" - "Is Google crawling my page?", "when was this page last crawled?" - "Does my page pass mobile-friendly test?" - "What canonical URL did Google pick?" - "Why isn't my rich snippet showing?" RETURNS: Index status (INDEXED, NOT_INDEXED, etc.), coverage state, crawl details (last crawl time, crawl allowed, page fetch status), mobile usability verdict, rich results status, and referring sitemaps. CRITICAL: The inspectionUrl must be a full URL (including https://) that belongs to the specified GSC property. RATE LIMIT: This API has stricter rate limits than search_analytics. Avoid calling in rapid loops. STEP-BY-STEP — Debug why a page isn't ranking: 1. Call inspect_url to check if the page is indexed at all. 2. If not indexed, check the coverage state and crawl details for the reason. 3. If indexed, use search_analytics to see its current performance. EXAMPLES: "Is my pricing page indexed?" → inspectionUrl="https://example.com/pricing" "Check mobile usability for homepage" → inspectionUrl="https://example.com/"

list_sitemaps: List all sitemaps submitted to Google Search Console for a property. Returns each sitemap's URL, type (sitemap, sitemapIndex, atomFeed, rssFeed), submission date, last download date, status (pending, success, errors), and content counts (web pages, images, videos). WHEN TO USE: User asks "what sitemaps are submitted?", "show my sitemaps", "check sitemap status", "are there any sitemap errors?", or "when was my sitemap last processed?". STEP-BY-STEP: 1. Call list_sitemaps to see all submitted sitemaps. 2. Call get_sitemap for detailed info on a specific one. EXAMPLE: "Show my sitemaps" → no required params (uses default site)

Frequently Asked Questions about Google Search ConsoleHow do I connect Google Search Console to Claude or ChatGPT?Create a free LearnToSpeak.ai account, add your Google Search Console credentials in the dashboard, and paste the generated OAuth URL into Claude.ai's custom connectors or ChatGPT's developer apps. The integration runs fully in the cloud — no desktop app, no CLI, no local install.Does it cost anything to connect Google Search Console?The Google Search Console integration is free during the LearnToSpeak.ai public beta. You only need a paid plan from Anthropic or OpenAI (Claude Pro/Max/Team or ChatGPT Plus/Pro/Team) since custom connectors require it on the AI provider side.Which AI assistants support the Google Search Console connector?Claude.ai (Pro, Max, Team, Enterprise) and ChatGPT (Plus, Pro, Team) both support the Google Search Console integration via the MCP (Model Context Protocol) standard. The same credentials work across both platforms — add the connector once, use it everywhere.How many Google Search Console tools does my AI get access to?Your AI gets 10 ready-to-use tools for Google Search Console, covering the most common read and write operations. Each tool is a discrete action the AI can call on demand — no multi-step prompting, no screen scraping, no workarounds.Is it safe to give an AI access to my Google Search Console account?Yes. Your Google Search Console credentials are encrypted at rest with AES-256-GCM and only decrypted in memory when the AI makes a request. LearnToSpeak.ai uses OAuth 2.1 with mandatory PKCE for the AI-to-platform connection, and you can revoke access instantly from the dashboard. We never store or log the actual tool responses returned to the AI.Why use LearnToSpeak.ai instead of running an MCP server locally?Cloud MCP servers work from any browser on any device — no Node.js install, no Docker, no local ports, no maintenance. Configure Google Search Console once in the dashboard and your AI connects from claude.ai or chat.openai.com directly. That's the entire value proposition: web AI assistants don't read your filesystem, they read our servers.What is the Google Search Console MCP server?The Google Search Console MCP server is a cloud-hosted integration that gives AI assistants direct access to Google Search Console through 10 tools via the Model Context Protocol (MCP) standard. It works with Claude, ChatGPT, Gemini, and any MCP-compatible AI — no local installation or Docker required.How do I connect Google Search Console to Claude via MCP?Sign up at LearnToSpeak.ai, add your Google Search Console credentials, and copy the generated MCP URL into Claude.ai's custom connectors (Settings → Developer → Custom Connectors). The cloud MCP server handles the connection — no CLI, no local server, no Docker.How do I connect Google Search Console to ChatGPT via MCP?Sign up at LearnToSpeak.ai, add your Google Search Console credentials, and copy the generated MCP URL into ChatGPT's developer apps (Settings → Apps → Advanced → Developer mode). Works with any ChatGPT Plus, Pro, or Team account.What can AI do with Google Search Console through MCP?Google Search Console offers 10 MCP tools covering Monitor search performance, keywords, impressions, and site indexing. Ask your AI to perform any of these actions in natural language — it calls the right tool automatically.What is MCP (Model Context Protocol)?MCP is an open standard that lets AI assistants like Claude, ChatGPT, and Gemini connect directly to external apps and services. LearnToSpeak.ai hosts cloud MCP servers so you don't need to install anything locally — your AI connects from any browser.Browse all 34 MCP servers