I ran a redirect audit on a 300-page WordPress site last month and found 47 redirect chains. Some of them were four hops deep. The site had been accumulating redirects for six years across three redesigns, two domain changes, and dozens of slug updates. Google was burning crawl budget following those chains on every single visit, and PageRank was leaking at every hop.
Redirect chains are one of the most common technical SEO problems I find on WordPress sites, and they are one of the easiest to fix once you know where to look.
What Is a Redirect Chain?
A redirect chain happens when a URL redirects to another URL, which then redirects to yet another URL before reaching the final destination. Instead of a clean A to B redirect, you get A to B to C, or A to B to C to D.
Here is what a typical redirect chain looks like on a WordPress site:
“ https://example.com/old-page/ → 301 → https://example.com/new-page/ → 301 → https://example.com/updated-page/ → 301 → https://example.com/final-page/ “
That is a three-hop redirect chain. The browser and Googlebot have to follow all three redirects before reaching the content. A single 301 redirect is normal and healthy. Chaining multiple redirects together is where the problems start.
Why Redirect Chains Hurt Your SEO
The damage from redirect chains hits three critical areas at once.
Crawl Budget Waste
Google allocates a crawl budget to every site. Googlebot has a finite number of URLs it will crawl per session. Every redirect hop consumes part of that budget. On a site with 500 pages and 50 redirect chains averaging 3 hops each, that is 100 extra requests Googlebot has to make per crawl session. Those are requests that should be spent discovering and indexing your actual content.
For smaller WordPress sites under 1,000 pages, crawl budget is less of a concern. For sites with 5,000+ pages, redirect chains can measurably delay indexing of new content. Google’s Gary Illyes confirmed in 2022 that reducing redirect chains improves crawl efficiency.
PageRank Dilution
Google’s own documentation states that PageRank passes through 301 redirects. But independent testing from Moz and Ahrefs consistently shows a small loss at each hop. A single 301 redirect passes approximately 95-99% of link equity. A three-hop chain passes roughly 85-95%. On your most important pages, that 5-15% loss adds up, especially when those pages are competing in tight keyword races.
Page Speed Impact
Every redirect hop adds 100-500ms of latency depending on server response time and geographic distance. A three-hop chain can add over a second to your page load time before the browser even starts rendering. Google’s research shows that a 1-second delay in mobile page load reduces conversions by 20%. Redirect chains are invisible speed killers that do not show up in standard page speed tests because those tools test the final URL directly.
How Redirect Chains Build Up in WordPress
WordPress sites accumulate redirect chains through predictable patterns. Understanding these patterns helps you prevent new chains from forming.
Slug changes over time. You change a post slug from /seo-tips/ to /seo-tips-2024/, then later to /seo-tips-for-wordpress/. If you created a redirect at each change, you now have a chain.
Plugin-generated redirects. The Redirection plugin, RankMath, and Yoast all create 301 redirects when you change a slug. If the new slug already has a redirect pointing to it, you get a chain automatically.
Domain migrations. Moving from HTTP to HTTPS, from www to non-www, or from an old domain to a new one adds redirect layers. If the old redirects are not updated to point directly to the final HTTPS URL, every legacy link follows a chain.
Category and permalink structure changes. Switching your WordPress permalink structure from /category/post-name/ to /post-name/ generates redirects for every post. If those posts had existing redirects, chains form immediately.
How to Find Redirect Chains
Method 1: Screaming Frog (Best for Full Audits)
Screaming Frog is the most thorough tool for finding redirect chains across an entire site.
- Open Screaming Frog and enter your site URL
- Go to Configuration > Spider > Advanced and check “Always Follow Redirects”
- Run the crawl
- Click the “Response Codes” tab
- Filter by “Redirection (3xx)”
- Look at the “Redirect Chains” report under Reports > Redirects > Redirect Chains
Screaming Frog maps every chain, shows every hop, and identifies the final destination URL. The free version crawls up to 500 URLs, which covers most WordPress sites.
Method 2: Google Search Console
Google Search Console flags redirect issues under Coverage (now called Pages in the updated interface).
- Go to Pages > Not Indexed
- Look for “Page with redirect” entries
- Click into each one to see which URLs Google flagged
- Test each flagged URL manually using the URL Inspection tool
Search Console does not map full chains, but it tells you which URLs Google is struggling with. Cross-reference these with your redirect plugin to trace the full chain.
Method 3: Redirect Path Browser Extension
Install the Redirect Path Chrome extension (free). Browse your site normally. The extension shows a green, orange, or red icon indicating redirects on every page you visit. Click the icon to see the full redirect chain for that URL.
This is my preferred method for spot-checking individual pages. It takes 30 seconds per URL and shows headers, status codes, and every hop in the chain.
Method 4: Check Your Redirection Plugin
If you use the Redirection plugin in WordPress, go to Tools > Redirection > Redirects. Sort by “Last Accessed” to see which redirects are actively being followed. Then manually test the target URL of each redirect. If the target itself redirects, you have a chain.
RankMath users can find redirects under RankMath > Redirections. The same principle applies: check whether your redirect targets are themselves redirecting.
How to Fix Redirect Chains in WordPress
The fix is straightforward. Update every redirect to point directly to the final destination URL. Eliminate the middle hops entirely.
Step 1: Export Your Redirects
In the Redirection plugin, go to Tools > Import/Export and export all redirects as a CSV file. This gives you a backup and a working spreadsheet.
In RankMath, go to Redirections and export. Same process.
Step 2: Map Every Chain
Work through your exported redirects. For each one, follow the target URL. If it redirects again, follow that one too. Document the final destination for every chain.
Example:
| Source | Current Target | Final Destination | |——–|—————|——————-| | /old-page/ | /new-page/ | /final-page/ | | /old-service/ | /services/ | /services/web-design/ |
Step 3: Update Redirects to Final Destinations
In your redirect plugin, edit each redirect in the chain. Change the target URL to the final destination. Delete the intermediate redirects that are no longer needed.
In the Redirection plugin:
- Find the redirect for
/old-page/ - Change the target from
/new-page/to/final-page/ - Delete the redirect from
/new-page/to/final-page/(it is now unnecessary) - Save and test
Step 4: Verify the Fix
After updating, test every changed redirect using the Redirect Path Chrome extension or curl:
“bash curl -I -L https://yoursite.com/old-page/ “
The -I flag shows headers only. The -L flag follows redirects. You should see a single 301 followed by a 200, not multiple 301s.
Step 5: Update Internal Links
This is the step most people skip. Go through your content and update any internal links that point to redirected URLs. Link directly to the final destination. This eliminates the redirect entirely for internal traffic and passes full link equity.
RankMath’s internal link suggestions help with this. You can also use Screaming Frog to export all internal links pointing to 301 URLs, then update them in bulk using a search-and-replace plugin like Better Search Replace.
Cleaning up internal links is a core part of WordPress blog SEO that compounds over time. Every direct link is faster and passes more authority than a redirected one.
Preventing New Redirect Chains
After fixing existing chains, put safeguards in place to prevent new ones.
Set a slug policy. Finalize your URL structure before publishing. Changing slugs after a post has been indexed creates redirects. Changing them again creates chains.
Audit redirects quarterly. Run Screaming Frog or check your redirect plugin every three months. Catch chains before they stack up.
Use the Redirection plugin’s chain detection. The Redirection plugin in WordPress shows a warning icon when it detects a redirect that targets another redirect. Enable notifications for this.
Update old redirects when adding new ones. Every time you create a new redirect, check whether any existing redirects point to your source URL. If they do, update them to point to the new destination directly.
These are the kinds of common SEO mistakes that accumulate silently. A quarterly redirect audit takes 30 minutes and prevents months of wasted crawl budget.
Redirect Chains vs. Redirect Loops
Do not confuse redirect chains with redirect loops. A chain eventually reaches a destination. A loop never does. A loop looks like this:
“ /page-a/ → /page-b/ → /page-c/ → /page-a/ (infinite loop) “
Browsers display an “ERR_TOO_MANY_REDIRECTS” error. Googlebot gives up and drops the page from the index entirely. Loops are less common than chains but far more damaging. If you find one, delete the circular redirect immediately.
How many redirects in a chain does Google follow?
Google follows up to 10 redirect hops before giving up on a URL. But best practice is one redirect maximum. Every hop adds latency and costs a small amount of link equity. John Mueller from Google has recommended keeping redirect chains as short as possible, ideally a single hop from source to destination.
Do redirect chains affect Core Web Vitals?
Yes. Each redirect hop adds server round-trip time before the browser receives any content. A three-hop chain on a server with 200ms response time adds 600ms to your Time to First Byte (TTFB). That delay pushes your LCP (Largest Contentful Paint) further out, directly impacting your Core Web Vitals scores.
Should I fix redirect chains on a small WordPress site?
Fix them. Even on a site with 50 pages, redirect chains slow down page loads for real visitors. A three-hop chain can add a full second of load time. The fix takes minutes per chain, and the ranking improvements are immediate for both speed and crawl efficiency.
Can I use a plugin to automatically fix redirect chains?
The Redirection plugin for WordPress detects chains and flags them. It does not automatically fix them because the plugin cannot know your intent for each redirect. You need to verify the correct final destination for each chain and update it manually. The good news is that most WordPress sites have fewer than 50 redirect chains, and updating them is fast once you have mapped the chains.
Clean Up Your Redirect Chains
If you have not audited your WordPress redirects in the last six months, run Screaming Frog or check your Redirection plugin today. Most sites I audit have between 10 and 50 redirect chains, and fixing them takes less than an hour. The payoff is faster page loads, more efficient crawling, and stronger PageRank flowing to your important pages.
If your WordPress site has years of accumulated redirects and you want a professional audit, get in touch. I run full technical SEO audits that cover redirect chains, crawl errors, schema markup, and everything else affecting your rankings.