Trace Every Hop in an HTTP Redirect Chain
A URL that used to work now lands on an error page, or a link you shared bounces through three different domains before arriving. Redirects are the invisible glue of the web, but a misconfigured chain quietly destroys SEO value, slows page loads, and confuses users. This tool follows an HTTP redirect chain hop by hop, showing the status code, location, and final destination at each step. With that trace in front of you, a chain that loops forever or passes through too many hops becomes obvious in seconds.
How to Trace a Redirect Chain
- Paste the full URL you want to check, including the scheme, such as
https://example.com/old-page. - Choose a user agent if the site serves different content to bots than to browsers.
- Press the trace button to follow the chain automatically.
- Review each hop in the results list, from the first response to the final status code.
- Look for the terminal status:
200means success, while repeated301or302entries mean the chain is still moving.
Real Example: Finding a Redirect Loop
A developer reports that example.com never finishes loading. The trace shows 302 from http://example.com to https://example.com, then another 302 back to the insecure URL. The loop is visible in two lines instead of an afternoon of guessing. The same trace also reveals the common www to non-www hop, which many sites add as an extra, unnecessary step.
| Input | Output |
|---|---|
http://example.com | Hop 1: 302 to https://example.com |
https://example.com/old | Hop 1: 301 to /new; Hop 2: 200 OK |
Tips for Clean Redirect Chains
- Prefer 301 for permanent moves — search engines transfer ranking signals only on permanent redirects, not temporary ones.
- Keep chains short — each hop adds latency; aim for a single redirect from the old URL to the final URL.
- Update internal links — linking directly to the destination removes the redirect tax entirely.
- Watch for protocol hops — every
httptohttpsandwwwto non-wwwswitch should happen in one redirect, not several.
When to Use This Tool
- Site migrations — verify that every old URL permanently redirects to its new counterpart after a relaunch.
- SEO audits — find chains longer than two hops and collapse them to preserve link equity.
- Link debugging — confirm that shortened links and affiliate URLs land where they claim to.
- HTTPS cutovers — ensure all traffic is forced to the secure version without loops.
Frequently Asked Questions
What is the difference between a 301 and a 302 redirect?
A 301 signals a permanent move and passes ranking signals to the new URL. A 302 is temporary and tells browsers and search engines to keep the original URL, which is right only for short-lived changes.
Why does my chain show a 308 status code?
A 308 is a permanent redirect that, unlike a 301, preserves the HTTP method and body. It is commonly used when moving a site to HTTPS so POST requests are not rewritten as GET.
How many hops are too many?
Browsers stop following after about 20 redirects, but for performance and SEO you should treat anything beyond two hops as a problem worth fixing.
Why did my redirect chain end at a 404?
The final URL does not exist or the server dropped the path during the redirect. Check whether the destination address is correct and reachable on its own.
Can this tool detect a redirect loop?
Yes. If the trace keeps returning 301 or 302 responses without a terminal 200, the chain is looping and the trace stops to show you exactly where.
Do redirects slow down my website?
Each hop adds at least one extra round trip. A single redirect typically costs 100 to 300 milliseconds of extra latency before the page even starts loading.
Why do I see a redirect to a URL with a trailing slash?
Many servers normalize directory-style URLs by appending a slash, so /about becomes /about/. That is normal behavior, not a configuration error.
How does the user agent affect redirect results?
Some sites redirect bots to different pages than browsers, or serve device-specific versions. Choosing a user agent lets you test the chain the way your target audience experiences it.