To fix redirect chains, map every old URL directly to its final destination with a single 301 redirect — not A→B→C. Remove intermediate hops, update internal links to point at the final URL, and test with a redirect checker. Re-scan to confirm.
A redirect chain happens when URL A redirects to B, which redirects to C. Each hop wastes crawl budget, slows users, and dilutes SEO signals. The fix is always one direct 301 from the old URL to the final canonical URL.
Check your website
See how your site handles how to fix redirect chains — free, no account needed.
Business impact
Chains make pages feel slow and can cause Google to stop following redirects before reaching the destination. After migrations or HTTPS changes, cleaning chains protects both rankings and user experience.
Why this happens
Chains accumulate during site migrations (HTTP→HTTPS→www), plugin stacking (CDN + server + WordPress all redirecting), and layered fixes where a new redirect was added without removing the old one. Loops (A→B→A) break pages entirely. Audit with curl -I -L or a redirect checker.
How to confirm the issue
Manually: run curl -I -L http://yoursite.com/old-page and count hops; ideal is one 301 to the final HTTPS URL.
With Plexa Trust: broken or slow redirect behaviour may appear alongside link and HTTPS findings; re-scan after flattening chains.
Step-by-step fix
List every URL that should redirect and its final destination.
Use a redirect checker to find chains and loops.
Replace multi-hop rules with one direct 301 per old URL.
Update internal links to the final URL — do not link through redirects.
Remove redundant rules from CDN, server and CMS layers.
Re-test and re-scan.
Platform-specific fixes
WordPress
Check Redirection plugin rules, Really Simple SSL, and server rules for overlap.
Consolidate to one rule per old URL pointing to the final path.
Update permalinks and internal links to HTTPS canonical URLs.
Cloudflare
Review Bulk Redirects and Page Rules — avoid duplicating server redirects.
Prefer fixing at origin and using Cloudflare only for edge cases.
Apache / Nginx
Combine HTTP→HTTPS and www canonicalisation into one rule where possible.
Apache: single RewriteRule from old path to final https://canonical/path.
Nginx: return 301 directly to final URL in one return statement.
How to verify the fix
Aim for one hop maximum from any old URL to its destination.
Fix internal links so crawlers never need to follow redirects.
Document redirect maps during migrations.
Common mistakes
Adding a new redirect without removing the old intermediate one.
Redirecting everything to the homepage instead of the relevant page.
Using 302 for permanent moves, losing ranking signals.
Frequently asked questions
How many redirects are too many?
More than one hop is a chain worth fixing. Google may stop following after several hops.
What is a redirect loop?
When URLs redirect in a circle (A→B→A). Browsers show an error. Fix by mapping each URL to one final destination.
Do chains hurt SEO?
They waste crawl budget, slow loading, and can prevent signals consolidating on the final URL.
301 or 302 for permanent moves?
Always 301 (or 308) for permanent consolidation so ranking signals transfer.
Who should fix chains — CDN or server?
Ideally one layer owns redirects. Fix at origin and avoid duplicating at CDN unless necessary.
How do I test redirects?
curl -I -L, browser DevTools, or online redirect checker tools.
Should internal links use redirect URLs?
No. Link directly to the final canonical URL to avoid unnecessary hops.
How do I confirm it worked?
Each old URL should show one 301 to the final URL; re-scan with Plexa Trust.
Think you've fixed it?
Run a free scan to verify the issue is resolved. Upgrade to Pro on Plexa Trust for the full audit, monitoring alerts, and score history.
Verify with a free scan