---
title: "Use AI agents with Search Console data"
description: "Choose a useful Search Console task for an agent, check registered sites and data coverage, then connect through MCP."
canonical_url: "https://gscdump.com/learn-google-search-console/ai-agents"
last_updated: "2026-09-11"
---

An agent can help turn a Search Console report into a question you can act on. For example: which pages lost clicks, and which of those pages should you review first?

The useful part is the connection to evidence. Ask the agent to name the registered site, dates, tool calls, and limits behind its answer. A confident explanation without those details is hard to check.

## Start with one reporting task

A good first task is a comparison between two equal periods. Ask for the largest page-level changes, then choose one page to investigate.

Keep the first run read-only. You want to see whether the agent uses the right site and dates before it proposes content edits.

```text
Call list-sites to show the registered sites I can access through gscdump.
Ask me to choose a site and use its returned siteId.
Show its sync status and recorded date range.
Do not assume that the range proves every day is complete.
Then propose two equal periods for a page-click comparison.
Wait for me to confirm those dates before analyzing them.
```

This is a prompt to run with your own connection, not a sample of observed account results.

## Connect the data

MCP lets a client call tools exposed by a server. With gscdump, the hosted endpoint is `https://gscdump.com/mcp`.

There are two separate connections. Your Google connection makes Search Console properties available to gscdump. MCP authorization lets an agent client access your gscdump account. Signing in to one does not complete the other.

Add the desired site through [Add a site](/app/sites/add). The `list-sites` tool lists registered sites accessible through gscdump.

The hosted server supports MCP OAuth and a user API key fallback. Your client must support the method you choose. Use the [MCP setup guide](/learn-google-search-console/ai-agents/mcp-server) to check the connection, or follow the specific [Claude Code setup](/learn-google-search-console/ai-agents/claude-code-seo).

## Check what the result can support

A site appearing in `list-sites` confirms that the tool can list it for your account. Its scope can differ from its source Search Console property. Its recorded sync range helps you choose dates. Those endpoints alone do not prove gap-free history.

For a page comparison, gscdump's `get-pages` tool reads stored analytics and returns a bounded list. If a page appears in only one period, ask whether the other result omitted it before treating its clicks as zero.

Search Console also withholds some query detail. An agent cannot recover that text by changing its prompt. Read [export limits](/learn-google-search-console/limits/export-row-limits) when you need to understand what is missing.

## Move from a report to a decision

A drop in clicks can justify a closer look. It does not identify the cause by itself. Check whether impressions changed, whether the periods are comparable, and whether the page or search results changed.

The [SEO workflows guide](/learn-google-search-console/ai-agents/seo-workflows) gives prompts for these next steps. If you're working beside the site's source files, the Claude Code guide shows how to connect a report to a proposed content review without letting the report dictate the edit.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.