Technical SEO Audit Workflow

A technical SEO audit with SEO MCP should move from site-wide patterns to page-level proof. Start with a completed crawl, inspect the overview, then query the records behind each finding. This produces a prioritized action plan instead of a generic checklist.

What this workflow covers

Recommended prompt

Run a read-only technical SEO audit on the latest completed crawl for [PROJECT].

Start with the on-page overview. Then investigate:
- non-2xx HTML pages
- missing or weak titles and descriptions
- H1 problems
- missing or mismatched canonicals
- deep pages
- slow responses
- pages with missing image alt text
- pages without expected social metadata

For every issue, show the filter used, affected count, representative URLs,
likely impact, recommended owner, and validation step.
Group template-wide patterns separately from one-off pages.

Tool sequence

1. list_projects
2. list_crawls
3. get_crawl_summary
4. get_on_page_overview
5. list_quick_wins
6. list_pages with one or more structured filters
7. get_page_details for representative or high-value URLs

Prioritization model

Prioritize with four questions:

1. Reach: How many indexable or business-critical pages are affected?
2. Severity: Does the issue block access or send a conflicting signal?
3. Pattern: Can one template fix resolve many URLs?
4. Confidence: Is the conclusion supported by page-level evidence?

A 404 in the global navigation may deserve attention before hundreds of harmless redirects in an old archive. Counts need context.

Validate the result

Ask the agent to provide:

• The exact crawl UID and crawl completion time.
• Every filter field, operator, and value.
• A bounded sample of affected URLs.
• Any limitations in the available crawl data.
• The metric that should change after the fix.

After implementation, run a new crawl and use the crawl comparison workflow.