Run the bounded queue directly:
seo crawl-queue --project <project> --json
seo crawl-queue https://example.com --json
Through MCP, use seo_run_report with report id crawl-site and
saveReport: true. Pass its reportId to report ids top-fixes and
affected-urls. Reuse that report instead of crawling again. Call
seo_describe_report before a report when its parameters are not already
known.
Check the evidence before ranking work
- Read
dataStatus, source joins, selection counts, warnings, and caveats. - Check
summary.pageLimitReached. A capped crawl cannot support an inventory-wide zero or all-clear. - Preserve the returned priority order unless stronger evidence supports a change.
- Use GSC or GA4 evidence only when the source join is available. Do not call a page search-visible or valuable from crawl evidence alone.
- Keep failed fetches, missing provider data, and filtered rows separate from observed zeros.
Each queue item should retain its rule id, priority, evidence, affected count, bounded URL sample, fix, and verification step. Explain unfamiliar rules with structured output:
seo explain --rule <rule-id> --json
Use report id explain-issue through seo_run_report.
Write Markdown implementation tickets only when the user wants a handoff file:
seo crawl --project <project> --format markdown --output seo-fixes.md
Keep the final answer short. Show the top material fixes and end with the next verification command. Do not dump every rule the crawler checked.