Redirect chains happen when one address redirects to a second address, which redirects to a third, and so on until a real page finally loads. Every extra step slows the visit and gives search engines more work. In this guide you will learn how redirect chains form, how to find them and the five costly mistakes that create them.
Table of Contents
What Is a Redirect?
A redirect tells a browser or a search engine that a page has moved. When you visit the old address, the server answers with a status code and the new address. The browser then loads the new address automatically.
The two codes you will meet most often are 301 and 302. A 301 means the move is permanent, so search engines should replace the old address with the new one. A 302 means the move is temporary, so the old address should stay in the index. Newer codes, 307 and 308, work the same way but keep the request method unchanged.
Redirects are useful. They keep old links working after a redesign, a rename or a move to a new domain. One redirect is perfectly healthy. The trouble starts when redirects pile up.
What Are Redirect Chains?
Redirect chains are sequences of two or more redirects between the first address a visitor requests and the final page. A simple example looks like this.
- http://example.com/old-page redirects to https://example.com/old-page
- That address redirects to https://www.example.com/old-page
- That address redirects to https://www.example.com/new-page
The visitor wanted one page and the server made three round trips to deliver it. Nobody planned this. Each rule was added at a different time by a different person, and together they formed a chain.
Why Redirect Chains Hurt Your Website
A chain does not break a site in an obvious way, which is why it often goes unnoticed. The damage is quiet and it adds up.
- Slower pages. Every hop needs a new request and a new response. On a phone with a weak connection this delay is easy to feel.
- Wasted crawl time. Search engines spend part of their visit following hops instead of reading content. Google’s documentation says Googlebot follows a limited number of hops, so very long chains may never reach the final page.
- Diluted signals. The more steps between a link and its target, the more risk that a signal gets lost along the way.
- Harder maintenance. A chain is difficult to understand and easy to break by accident.
Fixing redirect chains is one of the cheapest technical improvements you can make. It needs no new content and no design work, only a clean-up of rules.
5 Costly Mistakes That Create Redirect Chains
Almost every chain comes from one of these five habits.
1. Stacking HTTPS and www rules
One rule forces HTTPS. Another adds or removes www. A third fixes the trailing slash. Each rule fires separately, so an old HTTP address can take three hops to reach the correct version. Combine them so that every variation goes to the final address in one step.
2. Redirecting after every redesign
You redirect page A to page B. Later you rename page B to page C and add a second redirect. Page A now leads through B to C. Whenever you add a redirect, update the older ones to point at the newest destination.
3. Leaving internal links on old addresses
Your menu and your posts may still link to addresses that redirect. Visitors reach the right page, but each click pays the cost of a hop. Update internal links so they point straight to the final address.
4. Mixing plugins and server rules
A redirect plugin, the .htaccess file and a content delivery network can all hold rules. When they overlap, the visitor bounces between them. Keep redirects in one place whenever you can.
5. Forgetting migrations
A move to a new domain often adds a second layer of rules on top of the old ones. Review the old redirects before you launch the new site, and test a sample of old addresses afterwards.
Redirect Status Codes at a Glance
You do not need to memorise every code, but it helps to know what the common ones mean when you read a report.
- 301 Moved Permanently. The page has a new home for good. Use it for most moves.
- 302 Found. The page is somewhere else for now. Use it for short, temporary changes such as a seasonal landing page.
- 307 Temporary Redirect. A stricter temporary redirect that keeps the original request method.
- 308 Permanent Redirect. A stricter permanent redirect that keeps the original request method.
For ordinary web pages, 301 and 302 cover almost every case. What matters most is that each address needs only one of them.
Common Causes on WordPress Sites
WordPress sites collect redirects from many sources. Knowing where to look saves a lot of time.
- Permalink changes. WordPress usually redirects an old post address to the new one on its own. If you change permalinks twice, the second change can add a hop.
- SEO and redirect plugins. Plugins such as Rank Math and Redirection store rules in the database. Old rules often stay behind after a redesign.
- Caching and security plugins. Some of them force HTTPS or add www on their own, on top of rules you already have.
- Host settings. Many hosts add a redirect for HTTPS at server level. Combined with a plugin rule, that makes two hops where one would do.
- The .htaccess file. Older sites often carry years of hand-written rules in this file.
Check all of these places when you clean up. Remove duplicates, and keep one source of truth for each rule.
How to Find Redirect Chains
You cannot spot redirect chains by browsing, because the browser follows them silently. A crawler shows every hop.
- Open TechSEO on the home page of this site and crawl your website.
- In the Overview, look for Redirect chains under Warnings.
- Open the Links group and choose Redirects. Pick the Redirect chains filter.
- For each row read the address, the first redirect target, the final destination and the number of hops.
Anything with more than one hop is a chain. Sort your attention by the pages that matter most, such as your menu items and your best articles.
How to Fix Redirect Chains
The principle is simple. Every old address should redirect straight to the final destination in a single step. Here is how to get there.
Step 1: List the final destination
Take the Final destination column from the report. This is where each old address should end up.
Step 2: Rewrite the redirect rules
Change each rule so that it points to the final address instead of the next hop. In a redirect plugin this means editing the target. In a server file it means replacing the old target in the rule.
Step 3: Merge the global rules
Make sure HTTP, HTTPS, www and trailing-slash variations resolve in one hop. Most hosts and plugins have a single setting for this.
Step 4: Update internal links
Edit menus, widgets and posts so they link to the final address. This removes the need for a redirect on your own pages.
Step 5: Crawl again
Run the crawl once more and use the Compare tab to confirm that the number of redirect chains went down. For more detail on how Google treats moves, read its guide to redirects and Google Search.
Redirect Loops: The Worst Case
A loop is a chain that never ends. Address A redirects to B and B redirects back to A. Browsers give up and show an error such as too many redirects. Search engines abandon the page.
Loops usually come from two conflicting rules, for example one that adds www and another that removes it. If your crawl shows a start URL with no response and a redirect message, check for a loop first. Remove one of the two conflicting rules and test again.
How Long Should a Redirect Stay?
Many site owners wonder when they can delete an old redirect. For site moves, Google recommends keeping redirects in place for at least a year, because it can take a long time for signals to move from the old address to the new one.
After that, look at the facts. If the old address still receives visits or has links pointing to it, keep the rule. If nobody uses it any more, you can remove it. Removing unused rules keeps your list short and your site easier to maintain.
Whatever you decide, write the date and the reason next to each rule in your notes. Future you will be grateful.
Redirect Best Practices
Keep these habits and redirect chains will rarely return.
- Use a 301 for permanent moves and a 302 only for real temporary changes.
- Always redirect to the final page, never to another redirect.
- Redirect to the most relevant page, not blindly to the home page.
- Keep a simple list of your redirects so you know what exists.
- Check redirects after every redesign, migration or plugin change.
- Remove redirects you no longer need once the old address stops receiving visits and links.
Redirects also tie in with broken links. A removed page with no redirect becomes a dead end, so read our guide to the broken link checker as well.
Frequently Asked Questions
How many redirects are too many?
Aim for a single hop. Two hops are tolerable for a short time. Anything longer should be cleaned up.
Do redirect chains lose link value?
Search engines treat redirects as a way to pass signals along, but a long chain adds risk and delay. A direct redirect is always safer.
Should I use 301 or 302 for redirect chains?
Use 301 for permanent moves. The type matters less than removing the extra hops, but mixing types in one chain makes it hard to understand.
Can I fix redirect chains without coding?
Yes. A redirect plugin lets you edit targets in a form. Your host may also offer a redirect manager in its control panel.
Conclusion
Redirect chains are easy to create and easy to ignore, yet they slow visitors down and waste the attention of search engines. Find them with a crawl, point every old address at its final destination, update your internal links and check again. One clean hop per address is all a healthy website needs.
Curious how many chains your site has? Start a free crawl and read the answer in the Redirects report.
Leave a Reply