Redirect Chain Cleanup: Fixing Common Redirect Issues
Redirect chains waste crawl budget, slow page loads, and leak link equity. This troubleshooting guide helps you identify and fix redirect issues that silently harm your SEO.
Key Takeaways
- A redirect chain occurs when URL A redirects to B, which redirects to C (or further).
- A loop occurs when URL A redirects to B, which redirects back to A.
- Screaming Frog or Sitebulb will identify all redirect chains and loops.
- Maintain a redirect map in your repository
Types of Redirects
| Code | Type | SEO Impact |
|---|---|---|
| 301 | Permanent | Passes ~95% link equity |
| 302 | Temporary | May not pass link equity |
| 307 | Temporary (HTTP/1.1) | Preserves request method |
| 308 | Permanent (HTTP/1.1) | Preserves request method |
| Meta refresh | HTML-based | Poor UX, avoid |
| JavaScript redirect | Client-side | Not always followed by crawlers |
Redirect Chains
A redirect chain occurs when URL A redirects to B, which redirects to C (or further). Each hop adds latency (~100-300ms per redirect) and may lose link equity.
Chain: /old-page → /renamed-page → /final-page
Fix: /old-page → /final-page (direct)
/renamed-page → /final-page (direct)
Redirect Loops
A loop occurs when URL A redirects to B, which redirects back to A. The browser gives up after a few iterations (ERR_TOO_MANY_REDIRECTS). Common causes include conflicting server rules and CMS settings fighting each other.
Finding Issues
Using a Crawler
Screaming Frog or Sitebulb will identify all redirect chains and loops. Filter by 'redirect chain' and 'redirect loop' reports.
Search Console
Check the Coverage report for 'redirect error' and 'page with redirect' statuses.
Fixing Common Patterns
| Pattern | Fix |
|---|---|
| HTTP → HTTPS → www → non-www | Single redirect: HTTP www → HTTPS non-www |
| Old slug → new slug → newer slug | All old versions → final URL |
| 302 on permanent URL change | Change to 301 |
| Trailing slash inconsistency | Pick one, redirect the other |
Prevention
- Maintain a redirect map in your repository
- Audit redirects quarterly
- When adding a redirect, check if the source URL already has inbound redirects pointing to it
- Use a redirect testing tool before deploying