SSEO MCP
Getting Started

Run Your First SEO Audit with SEO MCP

Follow a practical SEO MCP workflow that finds high-impact technical SEO issues and verifies every recommendation against crawl records.

The best first audit is narrow enough to verify and broad enough to be useful. Start with the latest completed crawl, retrieve its overview, identify one high-impact issue class, and inspect the affected records before recommending fixes.

Audit prompt

Use SEO MCP to audit my latest completed crawl.

1. List my projects and ask me to choose if more than one is relevant.
2. List crawls for the selected project and use the latest completed crawl.
3. Summarize the on-page overview and quick wins.
4. Choose the three issue groups with the highest likely impact.
5. Verify each group with filtered page, link, or image records.
6. Return evidence, impact, recommended fix, and validation step.

Do not change settings or start a crawl.

Expected tool sequence

StageToolWhy it is used
Discoverlist_projectsPrevent guessed project identifiers
Select evidencelist_crawlsUse a real crawl UID and completed dataset
Orientget_on_page_overviewUnderstand site-wide distributions
Prioritizelist_quick_winsIdentify bounded improvement opportunities
Verifylist_pages, list_links, or list_imagesRetrieve the records behind the claim

What a strong answer includes

A useful result separates:

  • Finding: the exact condition observed.
  • Evidence: counts, URLs, fields, and filters used.
  • Impact: why the condition matters for crawling, indexing, relevance, or experience.
  • Action: the smallest practical fix.
  • Validation: how to confirm the fix in a later crawl.

Weak answers jump directly from a summary score to generic advice. Ask the agent to show the records when a claim influences engineering or content priorities.

Example verification request

Verify the missing-title finding.
Use list_pages with the appropriate title filter.
Return at most 25 examples, grouped by URL pattern.
Tell me whether the issue looks template-wide or page-specific.

After the audit

Turn one finding into a focused workflow:

Related documentation

On this page