GUIDE · PART OF AUTOMATED TECHNICAL SEO
Redirect management:
chains, loops and where they lead.
Redirects pile up. Every migration, renamed page and retired product leaves one behind, and after a few years a single URL can pass through four hops before it lands. This guide covers how to find what you have, which redirects are costing you, and why the fix belongs on the server.
What is redirect management?
Redirect management is the work of keeping a site's redirects short, correct and current. A redirect sends a visitor or a crawler from one URL to another. Over time they stack into chains, where one redirect leads to another, and occasionally into loops, where they lead back to the start. Managing them means finding those, pointing each old URL straight at its final page, and updating the links that still use the old address.
Key facts
- A redirect chain is one redirect leading to another. Each extra hop slows the page and can lose link value
- A redirect loop sends a URL back to itself, so the page never loads
- A 301 says a move is permanent. A 302 says it's temporary. For a retired URL, use a 301
- The fix is to point each old URL directly at its final destination
- A redirect has to be issued by the server to count as one. A script on the page that forwards the visitor is not the same thing
- SEORCE maps every chain and loop and works out the correct target. It leaves the change to your team
Last reviewed 15 October 2026 by the SEORCE team.
Nobody removes a redirect.
Redirects are added in a hurry and never revisited. Each one made sense on the day. Together they turn into a tangle that slows pages and leaks the value of old links.
A chain grows one hop at a time
A redirects to B after a redesign. B redirects to C after a migration. Nobody goes back to point A at C.
The page still loads
A visitor ends up in the right place and never knows it took four hops. Only a crawl shows it.
Server, CDN, platform, plugin
Rules get added wherever is quickest, so no single list shows them all.
Find them, judge them, then fix them properly.
Plenty of redirects are fine as they are. The job is to find the ones that aren't.
Map every redirect on the site.
You can't manage what you can't list. Because redirects are set in several places, the reliable way to find them is to crawl and follow each one.
- Every chain, hop by hopWith the status code at each step.
- LoopsURLs that never resolve.
- Internal links that point at a redirectEach of these costs a hop on every click.
- External links that land on a redirectBacklinks flags links routed through one.
Work out which ones matter.
A single clean redirect from an old URL to a new one is fine. Spend your time on the chains attached to pages that carry links or traffic.
- Chains on linked pagesWhere an old URL with backlinks passes through several hops.
- Chains on busy pagesWhere visitors wait through each hop.
- Temporary redirects left in placeA 302 that should have been a 301 years ago.
One hop, set on the server.
The fix is always the same: send the old URL straight to the final one. Where that rule is set matters, because only a redirect the server issues passes on what the old URL earned.
- Old URL to final URL, directlySkip every hop in between.
- On the server, CDN or platformWherever your redirects are properly configured.
- Update the links tooChange internal links to point at the final URL, so nothing needs redirecting.
- We leave this one to youSEORCE doesn't apply redirects for you. A redirect forwarded by a script doesn't behave like a server redirect.
/product/multi-currency → /features-old/… → /features/… → /features/multi-currency/product/multi-currency → /features/multi-currency (301)Cleaning up redirects, without breaking anything.
Work from a full list, and test each change before and after.
Crawl and list every redirect
Including the chains, the loops and the links that point at them.
Errors and redirects →Write the direct rule
Old URL to final URL, as a 301, for each chain worth fixing.
Apply it on the server
Hand the list to whoever manages your server, CDN or platform.
Update internal links
Point them at the final URLs.
Test, then crawl again
Check a few by hand, then confirm the chains have gone.
Free redirect tracer →Trace any redirect, hop by hop.
Paste a URL into the redirect tracer and it shows every hop to the final page, with the status code at each. It's the fastest way to confirm a chain or a loop.
Redirect problems, and what to do about each.
| What you find | Why it matters | What to do |
|---|---|---|
| A chain of several hops | Each hop adds delay, and link value can thin out along the way. | Point the first URL straight at the last. |
| A loop | The page never loads, for anyone. | Find the rule that sends it back, and remove it. |
| A 302 on a permanent move | It tells search engines the old URL is coming back. | Change it to a 301. |
| Internal links to a redirected URL | Every click takes an extra hop. | Update the link to the final URL. |
| A redirect to an unrelated page | Search engines may treat the old page as gone. | Redirect to the closest matching page instead. |
| One clean redirect | Nothing. This is how it should look. | Leave it alone. |
Every chain mapped, with the fix worked out.
Technical Suite follows each redirect on every crawl and lists the chains, the loops and the links that still point at old URLs. For each chain it gives the correct final target, ready to hand to your team. Backlinks adds which of those old URLs carry external links, so you know where to start.
Frequently asked questions.
A redirect chain is a series of redirects, where one URL forwards to a second, which forwards to a third. Each extra step is called a hop.
Aim for one. A single redirect from an old URL to its final page is fine. Once a chain reaches several hops, it slows the page and is worth shortening.
A 301 tells search engines the move is permanent. A 302 tells them it's temporary and the old URL will return. For a page that has moved for good, use a 301.
No. A redirect has to be issued by the server to behave like one, so SEORCE leaves the change to your team. It maps every chain and works out the correct target for each.
A single well-set redirect passes it on. Long chains and redirects to unrelated pages are where value tends to be lost, which is why both are worth fixing.
Crawl the site and follow every redirect to its end. For a single URL, the free redirect chain tracer shows each hop.
Yes. The SEORCE redirect chain tracer follows any URL through each hop to its destination and shows the status code at every step. It's free and needs no account.
See every redirect on your site.
Crawl your site and you'll get each chain and loop, with the target it should point to.
Not ready for an account? Use the free browser extension or any of the free tools.