Category: Developer tools
redirect chain planner
Plan redirects, and catch chains, loops and duplicate sources
Enter old-url -> new-url rows locally to detect redirect chains, loops and duplicate sources, then plan single-hop targets.
/old-page→/newer-page— collapse 2-hop chain to a single redirect/new-page→/newer-page— already a single hop/legacy→/current— already a single hop/duplicate→/target-one— already a single hop
- /loop-a → /loop-b → /loop-a
/duplicate→ /target-one, /target-two
Everything on this page is processed in your browser. Nothing is uploaded.
What this tool does
Clean up redirect mappings before publishing. Enter one old-url -> new-url row per line and the tool builds a redirect graph, follows each source to its final target, and flags chains longer than one hop, redirect loops and duplicate sources that point to different targets. It recommends direct final targets, but does not fetch URLs, check live HTTP status codes, write server rules or validate server config. The entered redirect rows, graph analysis and recommended plan stay in the browser and are not uploaded to LocalTools.
How to use it
- Enter one redirect per line as old-url -> new-url.
- Review flagged chains, loops and duplicate sources.
- Use the plan to collapse multi-hop chains to the final target.
Privacy
This tool runs entirely in your browser. Your input is never uploaded, stored or shared — closing the tab removes it.
Frequently asked questions
- How do I find multi-hop 301 redirect chains?
- Enter one redirect per line as old-url -> new-url. Review flagged chains, loops and duplicate sources.
- Why collapse redirect chains to the final target?
- Clean up redirect mappings before publishing.
- Does this redirect chain planner upload my URL list?
- The entered redirect rows, graph analysis and recommended plan stay in the browser and are not uploaded to LocalTools.
- What checks does this redirect chain planner not replace?
- No live URL fetching, HTTP status-code checks, crawling, DNS redirect checks, short-link tracking, canonical tag checking, .htaccess or Nginx validation, automatic server-rule writing, file uploads, batch imports, accounts, server processing or third-party APIs.
- Does it check live 301 or 302 status codes?
- No. It plans the mappings you paste and does not fetch URLs or read real status codes.