# Google Search Console MCP

Canonical: https://typenode.ai/templates/google-search-console-mcp

Connect Google Search Console to ChatGPT, Claude and other AI assistants over MCP, and ask about clicks, queries, pages and indexing. Read-only.

- No Google Cloud project needed
- Read-only access to your Google account
- No Google Search Console API fees

* [Try this template free](https://app.typenode.ai/sign-up?returnTo=%2Ftemplates%3Ftemplate%3Dgoogle-search-console-mcp)

7-day trial (no credit card) · 1,000 credits included

[How to Connect Google Search Console to Claude with MCP (Step-by-Step)](https://youtu.be/v6s0uusAxsg)

Published by Typenode · Reviewed by [Bartosz Mróz](https://typenode.ai/authors/bartosz-mroz) · Updated November 1, 2026

## About

People who connect AI assistants to their own data use this toolkit to ask questions about their Google Search Console properties in plain language, without opening a browser tab or writing API requests. It connects to Search Console through the Model Context Protocol (MCP), so any assistant that supports MCP — ChatGPT, Claude, Cursor and others — can call the tools you install.

The 18 tools cover property discovery, page and query performance, URL inspection and sitemaps. You can ask which queries drive traffic to a specific page, compare click trends across two date ranges, or check whether a batch of URLs is indexed — up to 20 per inspection call. Data comes directly from Google's API and reflects what Search Console reports, including the standard 3-day lag for web search performance.

The toolkit is read-only. It does not submit sitemaps, request indexing, change property settings or modify user access. Every call requires your own Google account, connected with the webmasters.readonly OAuth scope.

Connect your Google account with Typenode's managed OAuth app, or use your own Google Cloud OAuth app.

## Examples

What this template can return.

### Asked in Claude: How do I find which queries bring clicks to a page?

example.com · /guides/what-is-ssl · Last 28 days

Queries that brought clicks to this page:

Query Clicks Impressions CTR Position what is ssl 312 4,210 7.4% 8.2 ssl certificate 89 2,540 3.5% 11.4 ssl vs tls 74 1,820 4.1% 9.8 https explained 31 780 4.0% 12.1 how does ssl work 18 620 2.9% 14.3

"what is ssl" drives the most clicks at average position 8.2. Moving it above position 5 would raise CTR significantly. "ssl vs tls" ranks at 9.8 with the title not containing that phrase. "how does ssl work" sits at 14 and could benefit from a dedicated section.

## How it works

How your agent uses these tools.

### What Search Console properties can I see?

Calls the Search Console API to list every property your connected Google account can read, preserving exact property identifiers and permission levels. A follow-up lookup returns the details of one property. Most subsequent performance and inspection queries need the exact property identifier returned here.

### How do I find which queries bring clicks to a page?

Runs a performance query filtered to a single page, returning the search queries that drove clicks to it along with impressions, CTR and average position. A matching tool works the other way: given a query, it returns the pages that ranked. A combined tool returns rows grouped by both page and query.

### Can I check if a URL is indexed?

Calls Google's URL Inspection API for one URL and returns the full indexed-version result: crawl date, canonical URL, coverage state and any issues. A batch tool inspects up to 20 URLs in one call, each with its own outcome. This is not a live crawl test and does not request indexing.

### How do I track clicks and impressions over time?

Retrieves daily or recent hourly performance: clicks, impressions, position and CTR, as Google reports them. An overview tool combines totals with a daily time series in one call. Period comparison tools retrieve the same report for different named date ranges, returning each period's result separately without calculating differences.

### What does it do with sitemaps?

Lists the sitemaps submitted to a Search Console property and returns one sitemap's metadata, including Google's reported warnings and errors. The toolkit reads sitemap records; it does not submit, delete or update them.

## Tools · 18

Tools your agent can use to work with your data.

### List Google Search Console Properties

List Google Search Console properties accessible to the connected Google identity, preserving exact property identifiers and permission levels.

### Get Google Search Console Property

Get one exact Google Search Console property record. Returns the same fields as property discovery, with a direct lookup outcome.

### Query Google Search Console Performance

Retrieve Google Search Console performance using supported dimensions, filters and aggregation. Returns one bounded page of source rows; pagination does not guarantee exhaustive data.

### Get Google Search Console Performance Totals

Retrieve Google's aggregate performance for a property and filter scope. Totals come from a separate source query, never from summing displayed detail rows.

### Get Google Search Console Performance Time Series

Retrieve daily or recent hourly Google Search Console performance. Preserve reported timestamps, missing intervals and available incomplete-data metadata.

### Get Google Search Console Page Queries

Retrieve observed search queries for an exact page or explicit page filter. Returns a bounded page; omitted query identities are not reconstructed.

### Get Google Search Console Query Pages

Retrieve observed pages for an exact query or explicit query filter. Returns source performance rows without judging overlap between pages.

### Get Google Search Console Page Query Rows

Retrieve performance grouped by page and query, with optional country/device detail. Returns source rows for client-side analysis, subject to Google's detail limits.

### Get Google Search Console Search Appearances

Retrieve observed search appearance categories and source metrics for a scope. Use returned categories as filters in a subsequent performance query.

### Get Google Search Console Available Dates

Retrieve dates with reported performance in an explicit window and search surface. Missing dates do not establish zero traffic or a universal freshness boundary.

### Get Google Search Console Performance Overview

Retrieve separate source totals and daily performance, optionally with one detail dataset. At most three source requests; each dataset retains its own scope and continuation.

### Get Google Search Console Period Datasets

Retrieve the same performance report for supplied named periods. At most six independent source requests; returns datasets without matching rows or calculating changes.

### Get Google Search Console Surface Datasets

Retrieve the same performance report for selected search surfaces. At most six independent source requests; preserve per-surface results and failures without combining metrics.

### Get Google Search Console Property Datasets

Retrieve the same performance report for supplied Google Search Console properties. At most six independent source requests; each property retains its own result and continuation.

### List Google Search Console Sitemaps

List submitted sitemap records for a property, optionally within a sitemap index. Returns Google's metadata, not the sitemap XML URL inventory.

### Get Google Search Console Sitemap

Get one submitted sitemap's Google Search Console metadata, warnings and errors. Deprecated indexed counts do not establish indexed coverage.

### Inspect Google Search Console URL

Retrieve Google's full indexed-version inspection result for one property-member URL. This is not a live test or an indexing request.

### Inspect Google Search Console URLs

Retrieve indexed-version inspection results for up to 20 supplied URLs, with independent outcomes. Each attempted URL consumes one inspection request; this is not a sitewide index census.

## Use it in ChatGPT, Claude or Cursor

Clone the template in Typenode to start setup. Your agent prepares the template, then helps you connect your custom MCP connector.

### ChatGPT

[Connect Typenode MCP to ChatGPT](https://docs.typenode.ai/connect/chatgpt), then give your agent the template’s setup prompt.

### Claude

[Connect Typenode MCP to Claude](https://docs.typenode.ai/connect/claude), then give your agent the template’s setup prompt.

### Cursor

[Connect Typenode MCP to Cursor](https://docs.typenode.ai/connect/other-apps), then give your agent the template’s setup prompt.

## Apps and setup

Accounts, access, and setup for the apps this template uses.

### Google Search Console

#### Authentication

- Managed OAuth app
- Custom OAuth app

#### Required scopes

- <https://www.googleapis.com/auth/webmasters.readonly>

#### Costs

The Search Console API is free for the usage levels typical of conversational queries. Google applies per-project quotas.

#### Documentation

- [API documentation](https://developers.google.com/webmaster-tools): Search Console API methods, authorization and property identifiers.
- [Help center](https://support.google.com/webmasters): Learn how to manage Search Console properties and user access.
- [OAuth setup](https://developers.google.com/identity/protocols/oauth2/web-server): How to configure a Google OAuth web application for offline access.

## FAQ

Answers to common questions about using this template.

### Can it see all my Search Console properties?

Yes, every property your connected Google account has at least restricted access to. Property identifiers are returned exactly as Search Console uses them: URL-prefix (<https://example.com/>) or Domain (sc-domain:example.com). Properties your account cannot access are not returned.

### Does it change anything in my account?

No. Every tool is read-only. The toolkit connects with the webmasters.readonly OAuth scope, which Google does not permit to submit sitemaps, request indexing or change property settings. Nothing in your Search Console account or website configuration is modified.

### How fresh is the data?

Google Search Console web search data has a standard 3-day reporting lag. Hourly performance data is available only for the most recent 48 hours. The toolkit reports exactly what Google's API returns and does not estimate or fill gaps for missing days.

### What can't it do?

It cannot submit URLs for indexing, request sitemap processing, change property settings, add or remove users, or modify any data in Search Console. It cannot access properties your Google account cannot read, and URL inspection is limited to 20 URLs per call.

### What does it cost to use a template?

Templates are included with Typenode. Start with a 7-day trial (no credit card) and 1,000 credits included. Continued use requires a paid plan. Third-party services may charge separately; see Apps and setup.

### Who controls access to my data?

You choose which accounts to connect. The template’s workflows and tools use the access you configure. Review the required scopes and setup details before connecting an account.

## Related templates

- [Google Analytics MCP](https://typenode.ai/templates/google-analytics-mcp): Connect Google Analytics to ChatGPT, Claude and other AI assistants over MCP, and ask about sessions, channels, events and landing pages. Read-only.
- [LinkedIn MCP](https://typenode.ai/templates/linkedin-mcp): Explore LinkedIn people, companies, jobs and posts in Claude or ChatGPT through MCP and Apify. Paid collection with owner-set budgets.

## Disclaimer

This toolkit is published by Typenode and is not affiliated with or endorsed by Google LLC. Google Search Console is a service of Google LLC. Use requires a Google account with access to the properties you query, subject to Google's Terms of Service and API usage policies.
