Google Search Console logo search.google.com

Live

Google Search Console API and MCP server

Google Search Console has no API for requesting indexing, the Links report, removals or user access. Sign in to Google Search Console once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Google Search Console.

Google Search Console has no API for this. So we run one for you.

Google Search Console's own API, a GitHub MCP server and Cotlet compared
What you need Google Search Console's APIGitHub MCP serverCotlet
Request indexing, Links report, Removals, Users No Partly Yes, 15 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Google Search Console changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 16, 2026. Sources: Search Console API: resources and methods · Search Central blog: Search Analytics API now supports hourly data · Indexing API: using the API · Search Console Help: URL Inspection tool

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Google Search Console in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Google Search Console to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 15 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Google Search Console and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/google-search-console with its own method and path, such as POST /api/v1/google-search-console/indexing/request, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Google Search Console API and MCP server do?

15 tools on your own Google Search Console account. Agents call them as operations of the MCP tools google_search_console_read and google_search_console_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Google Search Console tools in Cotlet's MCP server and REST API
Tool What it does Access
get_performance_stats Clicks, impressions, CTR and average position by query, page, country, device, search appearance, date or hour. read
inspect_url Index status of a URL: the most recently indexed version, last crawl and canonical. read
test_live_url Fetch a page in real time and see whether Google could index it. read
list_pages_by_index_status URLs from the Page indexing report: the indexed ones, or the ones for a not-indexed reason. read
list_page_issues Indexing and page experience issues of a property with their URL count and validation state. read
list_sitemaps Sitemaps of a property with last read date, status and discovered pages. read
get_links_report Top linking sites, top linked pages, internal links and top linking text of a property. read
list_users Users of a property with their permission: owner, full or restricted. read
list_removals Removal requests of a property from the last 6 months with type and status. read
request_indexing Press Request indexing for one URL, which puts it in Google's indexing queue. write
validate_fix Start Google's validation of a fixed indexing or page experience issue. write
submit_sitemap Tell Google where a sitemap is, or resubmit it. Owner or Full user. write
request_url_removal Temporarily remove a URL or prefix from Google results, or clear its snippet. Owner or Full user. writeasks first
add_user Give a Google account access to a property as owner, full or restricted user. Owners only. writeasks first
remove_user Remove a user from a property. Owners only. writeasks first

Scroll the table for all 15 tools.

Ask in plain words. Your agent does the rest.

All Google Search Console use cases

Is it safe to connect Google Search Console?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Google Search Console API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Google Search Console is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Google Search Console have an API?

Google Search Console has an API, but it covers only part of the web interface (checked 16 Oct 2026). It offers Search Analytics queries (with an hourly breakdown for up to 10 days), sitemap list, get, submit and delete, property list, get, add and delete, and read-only URL Inspection of the indexed version. It cannot request indexing, run a live test, list not-indexed URLs, read the Links report, file removals or manage users.

How do I get access?

Sign up free, open Google Search Console under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 15 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Google Search Console yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Google Search Console sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: request_url_removal, add_user, remove_user wait for your OK by default. You can switch that off per tool for scheduled runs.

Can I use the Indexing API to get normal pages indexed?

No. Google says the Indexing API can only be used for pages with JobPosting, or BroadcastEvent embedded in a VideoObject, applies its spam policies to what you submit and tells you not to circumvent limits with multiple accounts. request_indexing presses Request indexing in the URL Inspection tool instead, which is the documented way to ask for an ordinary page.

How many URLs can I request per day?

About 10 a day per Google account, shared across every property the account can open; adding more properties does not raise it. Each request_indexing call spends one. When Google refuses, the call returns quota_exceeded, nothing is submitted, and your agent picks up the rest on the next run.

Which Search Console role do I need?

Owner or Full user permission covers every tool: performance, inspection, Request indexing, Validate fix, sitemaps, Links and Removals. Adding or removing users needs Owner, as Google allows only owners to grant permissions.

Should I use a Google Search Console MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Google Search Console changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Google Search Console?

No. Cotlet is independent and not affiliated with Google Search Console.

Give your agent access to Google Search Console.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free