Trace one redirect path

Use redirect-trace when a specific URL behaves unexpectedly after a move, canonical change, or routing release. It follows HTTP redirects manually, records each response, and audits the final destination for basic indexability and canonical evidence. The trace is one observation from the machine and time that ran it; CDNs, geography, cookies, user agents, and later deploys can differ.

Run the report

With MCP, call seo_list_reports with {"category":"monitoring"}. Call seo_describe_report with {"id":"redirect-trace"}, then call seo_run_report, for example {"id":"redirect-trace","params":{"url":"https://example.com/old-page","maxHops":8,"js":false,"refresh":true}}.

The CLI uses the same registry: