---
title: "Google Search Console MCP for AI agents | SEO Skill"
description: "Connect Google Search Console to your AI agent through a local MCP server. Analyze clicks, impressions, CTR, position, queries, pages, and URL inspection evidence."
canonical: "https://seoskill.dev/features/search-console"
language: "en"
---

# Google Search Console MCP for AI agents

Let your agent answer search-performance questions with your clicks, impressions, CTR, position, query, page, and URL inspection data.

“Which pages lost clicks, which queries caused the loss, and what should I check first?”

Ask your own data

## Get answers without another spreadsheet export

The Google Search Console MCP path gives your agent read-only access through the same local report engine as the command line. It can choose a report, request only the rows it needs, and keep the source, date range, units, and limits with the result.

## Find pages losing clicks

Compare final search periods, keep the dates visible, and show the pages and queries behind the change.

Search Console analysis

## Find near-term opportunities

Surface page-two queries, weak CTR, and pages with demand that already exists.

Search Console analysis

## Check indexing evidence

Inspect selected URLs and keep inspection results separate from crawl observations.

Search Console analysis

## Measure a change

Compare a saved release against later Search Console data without inventing a traffic forecast.

Search Console analysis

## Keep Search Console limits visible

Search Console does not expose every query row, and recent data can still change. The reports keep row limits, filters, dates, and skipped sections visible. A missing row does not become a definitive zero.

The CLI uses the final-data calendar for reporting windows and aggregates duplicate rows before ranking them. It does not assign Google Analytics geography to a Search Console query.

## Connect the property you already own

Run `seo start`, sign in to Google, and choose a Search Console property from the discovered list. The connection requests read-only access. Tokens stay in the local managed store.

Then connect the [SEO MCP server](https://seoskill.dev/features/mcp) or run reports directly in the terminal. Google Analytics is optional and stays separate from Search Console evidence.

[

### Connect Search Console and Google Analytics

Follow the local sign-in and property-selection steps.

Google setup guide

](https://seoskill.dev/docs/google)[

### Join search data to crawl evidence

Use the main audit to decide which technical and content checks matter next.

SEO audit tool

](https://seoskill.dev/features/seo-audit)

## Ask Search Console a useful question

Install the command, run seo start, and choose your Search Console property.

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```