Compare SEO Crawls

Crawl comparison is the clearest way to validate technical SEO work after a deployment. SEO MCP can compare two known crawl UIDs and help explain the deltas, but the conclusion should still be verified against affected records.

Comparison prompt

Compare the two latest completed crawls for [PROJECT].

Summarize:
- pages added or removed
- status-code changes
- on-page issue changes
- link and image changes
- score or overview movement

Separate improvements, regressions, and neutral changes.
For every major regression, retrieve representative records and explain
whether the pattern appears template-wide or isolated.

Tool sequence

1. list_projects
2. list_crawls
3. compare_crawls
4. get_crawl_summary for each crawl when more context is needed
5. list_pages, list_links, or list_images to verify an important delta

Choose comparable crawls

Comparison quality depends on scope. Confirm:

• The same project and domain.
• Similar crawl settings.
• Completed crawl status.
• Expected differences in URL limits or exclusions.
• Whether a release occurred between the two crawl times.

A large page-count change caused by a crawl limit is not a technical SEO regression.

Release review format

Validate a regression

The comparison shows more non-2xx pages.
Use list_pages on both crawl UIDs with the same status filter.
Identify new affected URL patterns and return up to 20 examples.

Keep the original crawl UIDs in the final report so another reviewer can reproduce the analysis.