Google Search Console logo
ConnectorGoogle Search Console

Google Search Console integration for Claude and Codex

Create a Google Search Console connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Google Search Console from Claude

Add the Google Search Console connection to a Space that runs Claude, then use it from every channel in that Space.

Use Google Search Console from Codex

Add the Google Search Console connection to a Space that runs Codex, then use it from every channel in that Space.

Use Google Search Console from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Analytics & Data

What the Google Search Console connector can do

Google Search Console provides tools to monitor, maintain, and troubleshoot your site's presence in Google Search results.

One connection, many Spaces

Connect Google Search Console once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • Add Site

    Adds a site to the set of the user's sites in Google Search Console. This action registers a new property (site) in Google Search Console for the authenticated user. After adding the site, you will need to verify ownership through one of the available verification methods. The site URL must be properly formatted as either a URL-prefix property (with protocol) or a domain property (with sc-domain prefix).

  • Delete Site

    Removes a site from the user's Google Search Console sites. This action permanently removes a site property from the authenticated user's Search Console account. The site URL must be URL-encoded. Use this when you need to unregister a site from tracking in Search Console.

  • Get Site

    Retrieves information about a specific Search Console site. Use when you need to get site details including permission level for a specific property.

  • Get Sitemap

    Retrieves sitemap metadata (submitted/indexed counts, errors, warnings, last-submission timestamps) for a specific sitemap in Search Console. Returns metadata only, not raw XML content. Note: numeric fields like `errors`, `warnings`, `submitted`, and `indexed` may be returned as strings; cast to int before comparisons. Values such as `contents.indexed` can lag several days after submission.

  • Inspect URL

    Inspects a URL for indexing issues and status in Google Search Console. Results may reflect cached data lagging real changes by several days. High-volume use can trigger 429 quota errors; limit to priority URLs.

Connection

API and auth details

Google Search Console APIs expose site ownership and search-performance data. Integrations can list verified sites, query search analytics, inspect URLs, submit or manage sitemaps, and connect SEO reporting or content-monitoring workflows to Google Search Console using OAuth-authorized access.

FAQ

Questions people ask before connecting Google Search Console

Can Claude use Google Search Console?

Yes. Add a Google Search Console connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Google Search Console through Type?

Yes. Add a Google Search Console connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Google Search Console MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More analytics & data connectors