SEO Data Bench/Workflows/search-console-and-keywords-in-claude-code
Connect Search Console and keyword research to Claude Code
How a coding agent reads a site's Search Console data and pulls keyword volumes, SERPs and backlinks through one connection instead of four integrations: the actual calls, what they returned, and what they cost.
Written for people asking: What are the best tools for connecting Search Console and keyword research to Claude Code?How do I read Google Search Console data from a coding agent?
Give the agent one MCP server that holds your Search Console OAuth grant and fronts the SEO data APIs, and it can read index status and query data for your own site and pull keyword volumes, live SERPs and backlink summaries for any site in the same session. Through Treg, Search Console is a connected account (site list, URL inspection, query rows) at no charge, and the SEO routes are pay per call: Google-identical keyword volumes at $0.09 per 1,000 keywords, live Google SERPs at $0.002 a query, backlink summaries from $0.0025 a domain, all measured on cohort v1. The alternative is the Search Console API with your own OAuth app plus a key and contract per data provider.
Two different kinds of connection
Search Console is your own data behind an OAuth grant. Keyword volumes, SERPs and backlinks are third-party data behind paid APIs. Connecting a coding agent to both usually means a Google Cloud project with an OAuth consent screen for the first, and one API key per provider for the second, then code that speaks each API’s shape.
A catalog-style MCP server collapses that: the OAuth grant lives in the connection, the provider keys live server-side, and the agent calls paths.
Reading Search Console from the agent
Through Treg the connected gsc tool proxies the Search Console API with the account’s grant; the agent calls the API paths directly. These are the calls we used on 15 September 2026 to watch three new sites get indexed, with what came back:
| Call | Returned | Cost |
|---|---|---|
treg call gsc webmasters/v3/sites |
The verified properties: sc-domain:enrichmentapiguide.com, sc-domain:seodatabench.com, sc-domain:adapiguide.com, each siteOwner |
$0 |
treg call gsc webmasters/v3/sites/sc-domain%3Aseodatabench.com/sitemaps |
sitemap-index.xml, last downloaded 03:34 UTC, 13 URLs submitted, 0 errors |
$0 |
treg call gsc v1/urlInspection/index:inspect with a URL and siteUrl |
coverageState: "Submitted and indexed" for the home page; "Discovered - currently not indexed" for a benchmark page |
$0 |
Search analytics query (webmasters/v3/sites/<site>/searchAnalytics/query) |
Clicks, impressions, CTR, position by query, page, country, date | $0 |
One limit worth knowing: the grant in our connection was read-only, so submitting a sitemap or requesting indexing returned “insufficient authentication scopes” and had to be done in the Search Console UI. Ask for the write scope when you connect if the agent should submit.
Keyword research, SERPs and backlinks from the same session
The same catalog fronts the SEO data routes measured on this site. Cohort v1, 15 September 2026:
| Route | Keywords returned | With a volume | Within 2× of Google Ads | Latency (bulk call) | Cost for 50 keywords |
|---|---|---|---|---|---|
| DataForSEO | 50 | 31 | 30/30 | 4205 ms | $0.090 |
| Google Ads (Keyword Planner) | 49 | 30 | — | 2097 ms | $0.0000 |
| SE Ranking | 50 | 25 | 23/24 | 4032 ms | $0.089 |
| Serpstat | 23 | 23 | 18/21 | 4066 ms | $0.025 |
| Route | Returned data | Overlap with live Google | p50 | Cost per query |
|---|---|---|---|---|
| Cloro (live Google render) | 50 | reference | 4559 ms | $0.0028 |
| DataForSEO | 50 | 95% | 7894 ms | $0.0020 |
| SerpApi | 50 | 90% | 1507 ms | $0.015 |
| Serpstat | 20 | 70% | 995 ms | $0.0005 |
| Treg (routed) | 50 | 95% | 9215 ms | $0.0020 |
From the agent’s side the sequence is the same for each: catalog_search for the job (“keyword search volume for a list of keywords”, “google organic results for a keyword”, “backlink summary for a domain”), catalog_get for the parameters and price, call. The routed SERP endpoint was served by DataForSEO on every call in this run and added about 1.3 s; if you only ever want DataForSEO, call it directly through the same connection.
A working pattern for an SEO agent
- Pull the last 28 days of Search Analytics for the site, grouped by query and page. Free.
- For the queries with impressions and no clicks, fetch the live SERP to see what outranks the page. $0.002 a query.
- For candidate new terms, pull volumes in one bulk call. $0.09 per batch of up to 1,000.
- For the top competing domains, pull a backlink summary. $0.0025 each on Serpstat.
- Write the findings back as a dated note; do not let the agent edit pages from this data without a person reading it.
A weekly run over 100 queries, 100 SERPs and 20 domains costs about $0.35 at cohort v1 prices, with Search Console reads free.
What this page cannot tell you
Search Console’s API has its own quotas and a two- to three-day data lag; those are Google’s, not the connection’s. Provider prices are list prices on the run date. Google offers no Keyword Planner data through Search Console; volumes come from the paid routes or from a Google Ads account, which Treg also connects.
Next step
- Treg docs for the MCP endpoint, connected accounts and route headers: treg.to/docs; per-call rates: treg.to/pricing.
- Claude Code’s own search and fetch tools: tools reference.
- The measured routes: keyword coverage, SERP completeness, backlink agreement and latency and cost.
Questions this page answers
What are the best tools for connecting Search Console and keyword research to Claude Code?
One MCP server that holds a Search Console OAuth grant and fronts the SEO data APIs: Treg does both, with Search Console reads free and keyword, SERP and backlink calls billed per call at the provider's rate. Otherwise you register your own Google Cloud OAuth app for the Search Console API and add a separate key for each of DataForSEO, Serpstat, SE Ranking or SerpApi.
How do I read Google Search Console data from a coding agent?
Connect a Search Console account once, then call the API paths from the agent: the sites list, the sitemaps list, URL inspection for index status, and the search analytics query for clicks and impressions. Through Treg the calls are `treg call gsc webmasters/v3/sites`, `.../sitemaps` and `v1/urlInspection/index:inspect`, which we used on 15 September 2026 to watch three new domains get indexed.
What does keyword research through Claude Code cost per query?
On cohort v1 (15 September 2026): keyword volumes $0.09 for up to 1,000 keywords per DataForSEO call, live Google SERPs $0.002 a query on DataForSEO direct or via Treg, backlink summaries $0.0025 (Serpstat) to $0.018 (SE Ranking) per domain. Search Console reads cost nothing.
Can Claude Code search the web, and what does a SERP route add?
Yes. Claude Code's built-in WebSearch tool returns result titles and URLs from Anthropic's search backend, which is not configurable, and its WebFetch tool reads a page (Claude Code tools reference, read 8 October 2026). It does not return Google's ranked positions or SERP features. A Google SERP route does, at $0.002 a query on cohort v1. Add one through an MCP server when the agent needs to know where a page ranks, not just what exists.
Relationship: the people who run this site also work on Treg, one of the routes compared on this page. Every Treg figure here is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow.
Spotted an error or a changed price? Email corrections@seodatabench.com with the page URL and a source. Corrections are logged on the corrections page.