Get started

Google Search Console for AI agents

Google Search Console shows how a website performs in Google Search, including rankings, indexing status, and sitemap health. Analysts and operators pull this data into reports and dashboards instead of collecting it by hand. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Google Search ConsoleSee the 9 actions ↓
AnalyticsOAuth 2.0MCP + RESTsearch.google.com
AUDIT LOG · GOOGLE SEARCH CONSOLEPOLICY: acme-support
09:41:07 · claude · u_8f2read
google_search_console.list_sites
List Sites✓ allowed · 212ms
09:41:08 · claude · u_8f2read
google_search_console.get_site
Get Site✓ allowed · 164ms
09:41:09 · claude · u_8f2write
google_search_console.add_site
Add Site✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
google_search_console.delete_site
Delete Site✕ blocked · policy: deny
EVERY GOOGLE SEARCH CONSOLE CALL, ON THE RECORD
01 · USE CASES

What agents do in Google Search Console.

01

Check search performance

Query search analytics for clicks and impressions on a page to report on SEO performance.

02

Inspect a URL's index status

Inspect a specific URL to see whether Google has indexed it and flag any issues.

03

Submit a sitemap after review

Submit an updated sitemap only after confirming the new URLs are ready to be crawled.

02 · ACTIONS

9 Google Search Console actions, graded by risk.

Every Google Search Console action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

5

Look things up. Allowed by default.

  • google_search_console.get_site
    Get Site
  • google_search_console.list_sites
    List Sites
  • google_search_console.get_sitemap
    Get Sitemap
  • google_search_console.list_sitemaps
    List Sitemaps
  • google_search_console.search_analytics_query
    Search Analytics Query

write

3

Create and change things. Allow, or ask the user first.

  • google_search_console.add_site
    Add Site
  • google_search_console.inspect_url
    Inspect URL
  • google_search_console.submit_sitemap
    Submit Sitemap

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • google_search_console.delete_site
    Delete Site
03 · HOW IT WORKS

Google Search Console in three steps.

  1. 01Your users connect Google Search ConsoleThey sign in to Google Search Console on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “add Site” can wait for the user, and “delete Site” can be denied outright.
  3. 03Any agent can actYour agent calls Google Search Console through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('google_search_console', {
  read: 'allow',
  write: 'ask',        // add_site
  destructive: 'deny',  // delete_site
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Google Search Console connects.

Users sign in to Google Search Console on Arc0 Connect and approve the scopes you request. Build with Arc0’s Google Search Console OAuth app, or bring your own so the Google Search Console consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

The same Google Search Console connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Google Search Console from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More analytics apps.

Gong58 actionsSerpApi59 actionsPeople Data Labs27 actionsPostHog507 actions21risk8 actionsAkta19 actionsAlpha Vantage56 actionsAmplitude54 actions
ALL ANALYTICS APPS →
07 · FAQ

Google Search Console and Arc0, answered.

Q01

Can I use Google Search Console with Claude, ChatGPT or Cursor?

Yes. Connect Google Search Console to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Google Search Console actions you allow.

Q02

How do users connect Google Search Console?

Users sign in to Google Search Console on Arc0 Connect and approve the scopes you request. Build with Arc0’s Google Search Console OAuth app, or bring your own so the Google Search Console consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

Q03

Which Google Search Console actions can my agent take?

9 in total: 5 read, 3 write and 1 destructive, such as “add Site”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Google Search Console?

Yes. Actions like “delete Site” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Google Search Console too?

Yes. The same Google Search Console connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Google Search Console into your agent.

Your users connect Google Search Console once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.

Connect Google Search ConsoleBrowse all apps →

Free to build · MCP + REST · Audit log on every plan