Connect Google Search Console to Claude Code

Query search traffic, inspect how Google indexed a URL, and manage sitemaps. Add Toolspoke to Claude Code once and it can use 8 Google Search Console actions. Your Google Search Console credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Google Search Console and connect it

    Add Google Search Console to a project in your Toolspoke workspace.

    Press connect and sign in to Google Search Console. Toolspoke keeps the token encrypted and refreshes it when it expires, so there is nothing to copy and nothing to rotate by hand.

  3. Choose what Claude Code may do

    All 8 actions start on. Switch off any of the 2 actions that change something in Google Search Console, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Google Search Console actions that only read, so they are safe to try first.

  • Read one property and the permission level this account holds on it

What Claude Code can do in Google Search Console

6 actions read and 2 delete or permanently change something.

Reads

  • List sites

    List every Search Console property the signed-in account can reach, with the permission level it holds on each, siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser. Call this first: every other operation takes a site_url, and this is where the exact string comes from. Properties come in two shapes and the difference matters, a URL-prefix property reads "https://example.com/" with the trailing slash, a domain property reads "sc-domain:example.com". Costs nothing and touches no report, so it is also this connector's health check.

  • Get site

    Read one property and the permission level this account holds on it. Use it to confirm a site_url string is exactly right, and that the account can do more than look, before spending a call on query_search_analytics or submit_sitemap. Get the site_url from list_sites rather than typing it. Search Console matches it exactly, and "https://example.com" without the trailing slash is a different string from "https://example.com/".

  • Query search analytics

    The Performance report, as data: clicks, impressions, CTR and average position for a property over a date range, grouped by whichever dimensions you ask for. This is the main reason to install this connector. Group by "query" to see what people searched for, "page" for which URLs earned the traffic, "date" for a trend line, "country" and "device" for a split, and combine up to four, asking for ["query", "page"] returns one row per query-and-page pair. Google withholds some queries for privacy, so the rows never sum exactly to the totals an ungrouped query returns. Fresh data lags by roughly two days, so end the range there rather than today. Get the site_url from list_sites first. Row limits: 25000 per call, paged with start_row.

  • Inspect url

    Ask Google what it knows about one URL on a property you own: whether it is in the index, when it was last crawled, which sitemaps referenced it, what Google picked as the canonical, whether robots.txt or a noindex blocked it, and the mobile-usability and rich-result verdicts. This is the operation for "why is this page not showing up". The URL must belong to the property named in site_url, and the property must be verified for this account. Quota is 2000 inspections a day and 600 an hour per property, so inspect the pages a question is actually about rather than sweeping a site.

  • List sitemaps

    List the sitemaps Search Console holds for a property: each one's path, when it was submitted, when Google last downloaded it, how many warnings and errors it produced, and how many URLs of each content type it declares. Call it before submit_sitemap to see whether a sitemap is already registered, and after to confirm Google picked it up. The `path` values it returns are the full sitemap URLs that get_sitemap and delete_sitemap take.

  • Get sitemap

    Read one sitemap's record: when it was submitted and last downloaded, whether Google flagged it as pending, how many warnings and errors it holds, and the URL counts it declares by content type. Prefer it over list_sitemaps when you already know the sitemap's URL and want only that one. The feedpath is the sitemap's full URL, taken from list_sitemaps.

Deletes or permanently changes

  • Submit sitemap

    Register a sitemap with Search Console and ask Google to fetch it. Classified destructive because it reaches outside the workspace: it tells Google to go and crawl whatever that file lists, it changes what Search Console reports about the property from then on, and resubmitting an existing path replaces the record already there. The sitemap has to be live at that URL and inside the property before this is called. Google fetches it, it is not uploaded here. Answers with an empty body on success; call list_sitemaps or get_sitemap afterwards to see whether Google actually read it and what it made of it.

  • Delete sitemap

    Remove a sitemap from a property's Search Console record, along with its submission history and error counts. The file itself is untouched, this only tells Google to stop tracking it, but the record and its history are gone and cannot be restored by resubmitting. Get the feedpath from list_sitemaps, and confirm with list_sitemaps afterwards.

Google Search Console in Claude Code: questions

Does Claude Code see my Google Search Console credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Google Search Console?

Yes. Each of the 8 actions can be switched off for a project. Turn off the 2 that change something and Claude Code can only read.

Will 8 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Google Search Console action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Google Search Console call does not run in a sandbox, so it bills nothing.

Try Google Search Console in Claude Code

Free to start, and tool calls cost nothing on any plan.