Redirect planner
Check a list of redirects before a migration: chains, loops, clashes, one hop each.
- Paste and test
- 2 rules
- Last updated
What it checks
- Chains: /a to /b to /c becomes /a to /c and /b to /c, so a visitor and a crawler make one hop.
- Loops that never end, and the same address redirected to two places.
- An address redirected to itself, a repeated line, and a line that is not a pair.
- Characters that a server’s config cannot take (a space, a quote, a bracket, a semicolon) and sources with a query or a star.
- The list after it is flattened, ready for the redirect generator.
Example
HTTP/1.1 302 Found Location: https://www.example.com/old HTTP/1.1 301 Moved Permanently Location: https://www.example.com/new HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8
HTTP/1.1 301 Moved Permanently Location: https://www.example.com/new HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8
How to fix
Plan the list, then write the config with the redirect generator, then test with the redirect checker on live addresses:
- Redirect each old address straight to its final home: one hop, and the permanent status (301) when the move is permanent.
- Send an address to the page that answers the same need, not to the home page: Google treats a mass redirect to the home page as a soft 404.
- Keep the redirects for as long as the old addresses are linked or ranked, a year at the least.
- Update your internal links and sitemap to the new addresses; do not leave them to the redirects.
/old-page /new-page
/collections/old /collections/newFAQ
Each hop costs a request and some patience: crawlers follow a limited number of hops, and a visitor waits for every one. One hop is faster and safer.
In the redirect generator, which takes the same list and writes Apache, nginx, _redirects and Vercel config.
No. The planner runs in your browser, and nothing you type leaves it.
What this tool runs
- A chain of redirects before the pageminor
redirect-chain - A temporary redirect for a move made for goodminor
redirect-temporary
How we measure
The planner runs in your browser. It reads each line as an old address and a new one separated by a space, a comma, a tab or an arrow, normalises the paths (decoded, no trailing slash), follows each source to its end, and names a path met twice on the way as a loop. The examples are judged by the redirect checks Arablyzer runs on a live address (redirect-chain, redirect-temporary).