Search Console MCP
·Updated ·8 min read·
Grok Bot
Agents
Guide

Connect Google Search Console to Grok and Grok Bot

Connect Google Search Console to Grok Bot with a setup token, then schedule SEO routines on your real ranking data: digest, regression watch, sweep.

To connect Google Search Console to Grok Bot, sign in at mcpsearchconsole.com and generate a setup token. In Grok Bot, open Settings, then Plugins, and add a custom connector with the URL https://mcpsearchconsole.com/mcp and the header Authorization: Bearer plus your token. Then attach it to a task with @ and ask for your properties.

Grok Bot is xAI's take on the always-on agent: named AI teammates that live on a cloud computer with a browser, files and a terminal, keep memory between sessions, and run routines on a schedule after you close your laptop. Connect one to our Google Search Console MCP server and SEO maintenance becomes something your Bot does every Monday morning with your real queries, clicks and positions, not something you remember to check.

What Grok Bot is (and why it fits Search Console)

Launched in beta on August 11, 2026, Grok Bot sits on xAI's top plans (SuperGrok Heavy, Cursor Ultra and eligible team plans). You create named Bots, give them standing instructions, and they work persistently: routines run on schedules, successful processes become reusable skills, up to six Bots can pass work between themselves in group chats, and sensitive actions wait for your approval.

That shape rewards exactly what SEO needs: boring consistency. Rankings drift, pages fall out of the index quietly, Core Web Vitals regress after an unrelated deploy. None of it announces itself; it has to be noticed. An agent that reads your Search Console data every week and only pings you when something moved is the right tool, and because the Search Console MCP is read-only by default, an autonomous Bot can observe your site but not change it.

The two Grok Bot constraints that decide the setup

  • Remote MCP servers only. Grok Bot attaches MCP servers over HTTPS on the public internet. It cannot run local stdio servers and cannot reach localhost, so the classic "clone an open-source GSC server and run it on your machine" route is out (or means running a tunnel forever). A hosted server is the supported path, not just the convenient one.
  • No interactive OAuth yet. In the current beta, custom connectors take a server URL plus a static auth header; Grok Bot cannot drive a sign-in flow the way Claude or ChatGPT do. That is what our manual setup token is for: you do the Google sign-in once in your own browser, then hand the Bot a bearer token.

Connect it, step by step

  1. Get your setup token. Sign in with Google here (approve the read-only Search Console scope), then on your account page click Generate setup token. Copy it now; we store only a hash, so it is shown exactly once.
  2. Add the plugin in Grok Bot. Open Settings → Plugins, add a custom connector, and set the server URL to https://mcpsearchconsole.com/mcp.
  3. Set the auth header. In the connector's auth field, use Authorization: Bearer <your token>.
  4. Attach it. Connectors become available to attach to a task with @, alongside your Bots and routines. Attach Search Console and run the check below.

From then on any Bot on the account can call the server's tools: search performance with filters and period comparisons, ready-made insights, URL inspection, sitemaps, PageSpeed and site-health checks for DNS, redirects, robots.txt and TLS.

Check it works

Attach Search Console to a task and send this first prompt:

First promptList my Search Console properties, then give me clicks, impressions, CTR and average position for the first one over the last 28 days.

What you should see: the Bot calls list_sites, then search_analytics, and answers with your properties exactly as Search Console names them, such as sc-domain:example.com or https://example.com/, followed by four totals for the 28 days ending about two days ago, since Search Console data trails by roughly two days. If your sites come back, your Bots are connected. Listing properties is free; the performance query counts as one data pull. An authentication error at this point almost always means the header is missing the word Bearer or the token was mistyped.

Three routines that maintain your SEO

Give a Bot these as scheduled routines and you cover most of the weekly grind. They are deliberately small; a Bot that messages five bullet points every Monday beats a dashboard nobody opens.

Monday digest routineEvery Monday at 9:00: pull Search Console performance for sc-domain:example.com, last 7 days vs the 7 days before. Summarize clicks, impressions, CTR and average position; name the top 3 winners and losers by clicks; flag any query where average position dropped by 2 or more. Report five bullet points, no fluff.
Regression watch routineEvery other Thursday: list striking-distance queries (average position 8 to 20, over 100 impressions in the last 28 days) and compare with the list you saved last run. Tell me which improved after our changes, which are new, and pick the 3 best opportunities to work on next. Save today's list for the next comparison.
Technical sweep routineMonthly: run inspect_url on our 10 most-clicked pages, check list_sitemaps for errors, and run page_speed on the homepage and top landing page. Also check redirects and TLS on the apex domain. Only report if something regressed: a page dropped out of the index, a sitemap has errors, or Core Web Vitals got worse.

Grok Bot's memory is what makes the second routine work: "compare with last run" is only computable because the Bot persists files between runs. If you want the full self-improving loop, with hypotheses and verified predictions, the design in our autonomous SEO agent guide transfers unchanged.

Prompts to try

For one-off questions, or as the starting point for a new routine, each prompt below works as written; the heading links to a page explaining the method and how to read the result.

Striking-distance keywordsFind my striking-distance keywords: queries where I rank in positions 6 to 20 over the last 28 days. Group them by page and tell me which three pages to improve first.
Keyword cannibalizationCheck my site for keyword cannibalization: queries where two or more of my pages rank. For each one, say which page should own the query and what to do with the others.
Low-CTR pagesList my pages with the most impressions and a CTR well below what their position suggests. Draft a better title tag and meta description for the top five.
Content decayCompare the last 28 days with the same 28 days three months ago and list the pages that lost the most clicks. For each, say whether the drop comes from position, CTR or demand.
Index coverage auditInspect my ten most-clicked pages and check my sitemaps. Tell me which pages are not indexed or have a different Google-selected canonical, and why.
Weekly SEO reportWrite my weekly SEO report: the last 7 days against the 7 before, with clicks, impressions, CTR and average position, the top three winners and losers, and one thing to do next week.
Site migration checksWe moved from old.example.com to example.com on [date]. Check the redirects on my 20 most-clicked old URLs, inspect where they land, and compare clicks before and after the move.
Technical SEO auditRun a quick technical check on my homepage: robots.txt, redirects, TLS certificate, DNS and Core Web Vitals. Report only what needs fixing.

Using grok.com chat instead?

Regular Grok on grok.com also takes custom MCP connectors, and there you can sign in interactively: xAI's docs say to go to grok.com/connectors, click New Connector, choose Custom, enter the server URL and complete any required authentication. Paste https://mcpsearchconsole.com/mcp and sign in with Google when prompted. On Grok Business and Enterprise, xAI says a team admin must provision a connector first. That route is interactive chat rather than scheduled teammates.

Also available for Claude, ChatGPT, Cursor, Claude Code, Codex and Mistral.

Troubleshooting

Why won't the Grok Bot connector accept an OAuth sign-in?

Expected in the current beta: Grok Bot has no interactive OAuth for custom MCP servers. Use the setup-token route above; the token stands in for the sign-in you completed in your own browser.

I lost my Search Console setup token

Generate a new one from your account page. Generating a new token replaces the old one, so update the plugin's auth header after regenerating.

Why does Grok Bot reject the MCP server URL?

It only accepts servers reachable on the public internet. https://mcpsearchconsole.com/mcp is public, so a rejection usually means a typo (the path is /mcp, not /).

Do several Grok Bots share one Search Console quota?

Yes. Connectors are shared account-wide, not per Bot, and every Bot's data pulls draw on the same quota. Free-plan caps that fit one weekly digest can bind when three Bots each run their own routine; space the schedules or upgrade.

Why does Grok Bot return no data for my site?

Have the Bot list your properties first. sc-domain:example.com and https://example.com/ are different Search Console properties; put the exact one in the routine's standing instructions.

Why is yesterday's Search Console data empty?

Search Console data trails by about two days. Write routines against trailing windows (last 7 or 28 days), never "yesterday".

Quota and pricing

Connecting is free: discovery and site-health tools are unlimited, and data pulls (performance queries, insights, URL inspection, sitemaps, PageSpeed) are capped at 15 a day and 40 a month on the free plan. A weekly digest plus a monthly sweep fits the free plan; an account full of Bots running daily routines is exactly the case Solo's unlimited pulls are for, at €4.99 a month next to Grok Bot's own price tag.

FAQ

Can I connect Google Search Console to Grok?

Yes, both ways. Grok Bot takes a custom connector with https://mcpsearchconsole.com/mcp and a setup token in the auth header; grok.com chat takes the same URL as a custom connector with Google sign-in.

Does Google Search Console have an MCP?

Google itself does not publish a Search Console MCP server that we could find on 2 October 2026. Third-party servers fill the gap using Google's public Search Console API: hosted ones like Search Console MCP, and open-source ones you run yourself. Grok Bot needs a hosted one, because it cannot reach a server on your own machine; our best hosted Google Search Console MCP servers page lists the options.

Go further

The always-on pattern is bigger than one product: our OpenClaw and Hermes guide runs the same three routines on self-hosted agents, and the autonomous SEO agent guide adds the full hypothesis-and-verify loop. For interactive analysis in chat, the Claude guide and ChatGPT guide are the one-minute versions. And for what to stack next to Search Console (backlinks, crawling, conversions), see the best SEO MCP servers comparison.

Ready to put your search data in your AI?

Set up the Search Console MCP, free

Free plan included. See pricing