Information checked: 21 July 2026.
A redirect chain occurs when one URL redirects through several intermediate URLs. A loop occurs when redirects eventually point back to an earlier URL. Both waste time and can prevent users, search engines and integrations from reaching the destination.
In brief: Update rules and internal links so requests reach the final canonical URL directly.
Diagnose the complete route
- Test with an HTTP header tool rather than relying only on the browser.
- Record every status and Location header.
- Check protocol, hostname, slash, case and legacy path rules.
- Test query strings and representative deep URLs.
- Review CDN, hosting, CMS and application redirects together.
Common causes
Chain or loop causes
- Layered migrations
- Old HTTP URL → old HTTPS URL → new domain → new path
- Conflicting canonicalisation
- www rule and non-www rule both active
- Slash rules
- Application adds a slash while server removes it
- Language or device logic
- Two systems disagree about preferred route
- Wildcard rule
- A broad pattern also matches its own destination
Repair safely
- Export current rules and take a configuration backup.
- Choose the single final canonical URL.
- Change old sources and internal links to point directly there.
- Replace layered rules with a tested direct mapping.
- Clear relevant caches and monitor errors after release.
Test the outcome
Crawl the old and current URL sets and confirm there are no loops, no unexpected multi-hop chains and no internal links to redirected URLs.
The most common weak point
A chain can be reintroduced even after a clean migration when canonicalisation, language, trailing-slash and application rules are owned by different systems. Each team sees its own redirect as correct, but together they create delay or a loop.
Evidence and records to preserve
- Full-hop test output
- Canonical URL rules
- Configuration backups
- Layer ownership map
- Regression test URLs
Start with this
Create a small permanent regression set covering protocol, hostname, slash, uppercase, old paths and query strings. Run it after every hosting, CMS or CDN change.
Sources and date checked
This practical guidance was checked against the following primary sources. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.