Redirect chain: http → https → www (multiple hops slow the page)
A single URL goes through several redirects before the final page loads.
Redirect chainAvoid multiple page redirectsredirect chain http https wwwPage with redirect SEO redirect chain too longtoo many redirect hops Meaning
Each hop adds latency, and long chains hurt SEO and sometimes break crawlers/APIs. Redirect straight to the canonical https://www... URL in one step, and update links, sitemaps and canonical tags to the final URL.
Common causes
- Separate redirect rules for http→https and non-www→www
- Rules in server, CDN and app all active
- Old URL → new URL → newer URL
- Trailing-slash redirect added on top
- Links not updated
⚡ Quick fix
- Redirect to the final URL in a single 301
- Update internal links and sitemap
- Test with
curl -sIL
Detailed fix by platform
cURL
- bash
curl -sIL -o /dev/null -w "%{num_redirects} redirects -> %{url_effective} " http://example.com/
How to diagnose
- Hops — More than one?
- Final URL — Canonical?
- Rules — Duplicated?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026