---
title: "SEO workflows with Search Console MCP"
description: "Run page-loss reviews, query investigations, and targeted URL inspection with comparable periods and traceable tool evidence."
canonical_url: "https://gscdump.com/learn-google-search-console/ai-agents/seo-workflows"
last_updated: "2026-09-11"
---

A repeatable SEO workflow needs a question, a consistent report, and a decision someone can check. Begin with one question: which pages deserve a closer look this week?

These prompts assume a working [MCP connection](/learn-google-search-console/ai-agents/mcp-server). They are instructions to run against your own data, not examples of measured results.

## Choose periods before comparing pages

Start with `list-sites`, choose a registered site by its public `siteId`, and inspect its recorded sync range. Then choose two equal periods with matching weekdays.

Do not choose a fixed three-day gap and assume that makes the data complete. Recorded oldest and newest dates do not prove uninterrupted coverage either. If the tools cannot establish that the periods are comparable, say so before drawing a conclusion.

```text
Show the selected site's siteId, sync status, and recorded date range.
Propose two equal seven-day periods with matching weekdays.
State what the tools establish about coverage and what remains unknown.
Keep siteId and report settings consistent across both periods.
Ask me to confirm the dates before comparing results.
```

For fresh Google data, [data delay](/learn-google-search-console/limits/data-delay) and [hourly metadata](/learn-google-search-console/api/hourly-search-analytics-api) explain why recent observations can change.

## Review page losses

Use `get-pages` for both approved periods. Its returned list is bounded and sorted by clicks, so it can omit a page from one period's result.

```text
Fetch get-pages for both approved periods with the same limit.
Build the union of returned page URLs.
Show previous clicks, current clicks, and absolute change
only where both observations are available.
Mark an absent row as unknown unless another result proves zero.
Show the row limit and any tool errors beside the comparison.
Shortlist five pages for review. Do not claim a cause yet.
```

If clicks fell but impressions held steady, inspect CTR and the search result context. If impressions also fell, investigate demand, query mix, and visibility. These are next questions, not automatic diagnoses.

For a small baseline, percentage changes can look dramatic. Show absolute clicks as well so the reader can judge whether the change matters.

## Investigate a query opportunity

Use `get-keywords` to find candidate queries, then `get-keyword-details` for a selected query's series and pages. A useful candidate has enough impressions to investigate and a page you can realistically improve.

```text
List candidate queries with impressions, clicks, CTR, and average position.
State the dates and result limit. Let me choose one query.
Use get-keyword-details for that exact query.
Show the pages returned and the observed daily series.
Separate missing observations from zeros.
Suggest what to review on the relevant page, without promising a rank gain.
```

Average position describes impressions over the period. It is not a daily rank tracker or a guarantee that one edit will move the page.

If several pages appear for a query, compare their purpose and results before calling it cannibalization. Different pages may answer different needs. Missing query detail also limits the analysis, as the [export guide](/learn-google-search-console/limits/export-row-limits) explains.

## Inspect a selected URL

Use this when you have a specific indexing question, such as a canonical mismatch:

```text
Inspect the exact URL I provide with inspect-url.
Show the verdict, last crawl time, user canonical, and Google canonical
when those fields are returned. Mark missing fields as unavailable.
Explain which result needs a closer look.
Do not describe this as a live-page test or a site-wide indexing audit.
```

Google's [URL Inspection API](https://developers.google.com/webmaster-tools/v1/urlInspection.index/inspect) returns information about the indexed version. Check the current page separately before deciding whether an old result still describes the issue.

## Save the evidence with the decision

For each run, keep the siteId, dates, tool names, arguments, returned values, and limitations with the recommendation. If a tool fails, record the failure and follow its retry guidance rather than substituting a plausible answer.

A short review record can be enough:

```text
Question:
Registered siteId and periods:
Tool calls and limits:
Observed change:
Missing evidence:
Next check:
Proposed action, awaiting review:
```

Repeat the workflow with the same definitions when you check the result of an edit. Keep the edit date as context, for example with a [Search Console annotation](/learn-google-search-console/performance/custom-annotations). Allow for other changes before attributing a later traffic movement to your work.

## Sitemap

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