Technical SEO / redirects
Redirect checker
Trace every hop from request to destination
One hop is fine. Chains of 302s, HTTP→HTTPS→www→trailing-slash stacks, and loops burn crawl budget and dilute link equity. This checker follows Location headers hop by hop, including servers that block HEAD.
What this checks
- Each hop’s URL, status code, and time
- Final destination
- Redirect loops and hop limits
- HEAD with GET fallback when HEAD is blocked
Why it matters
Migrations, domain changes, and CMS canonical plugins create chains you never see in the browser. Trace the status codes and timing before you assume a 301 did what you think.
Use this page directly, or call check_redirects through WebMCP with the same URL.