Redirect Chain Checker - Trace Every Hop Free

A redirect chain checker follows a URL hop by hop and shows every status code between the address you typed and the page that finally loads. Paste any public URL and you get a numbered table of each request, its status, and whether the step was an HTTP redirect or a meta refresh. SEOs, developers and site owners use it to find slow or broken paths.

What Is a Redirect Chain?

A redirect chain is a sequence of two or more redirects that a browser or crawler must follow before it reaches the final page. Instead of going from the old URL straight to the new one, the request passes through one or more in-between URLs.

Most chains are accidental. A site moves from HTTP to HTTPS, then adds www, then restructures its folders, and each change stacks a new redirect on top of the last one. Nobody removes the old rules, so a visitor now travels through several hops.

Redirect types the tool reports

• 301 and 308: permanent redirects. They tell search engines the content has moved for good.
• 302 and 307: temporary redirects. They signal that the original URL should stay in use.
• 303: a "see other" redirect, often sent after a form submission.
• Meta refresh: a redirect written into the HTML of a page that otherwise loads normally (status 200). The Type column labels these as meta-refresh.

People sometimes search for "reroute vs redirect". On the web, "redirect" is the standard term. A reroute is just an informal way of describing the same idea: sending a request to a different destination.

How to Use the Redirect Chain Checker

You trace a chain by entering one URL and pressing one button. The steps below match the fields on this page.

1. Type or paste the address into the URL to trace field. The placeholder shows a short link such as https://bit.ly/example, but any public page works.
2. You can leave off the protocol. If you enter only a domain, the tool starts with http://, which is useful because it exposes HTTP-to-HTTPS redirects.
3. Press Trace Redirects.
4. Read the summary: observed requests, how many were redirect responses, the final status and the final URL.
5. Scan the table with its #, Status, URL and Type columns to see each hop in order.
6. If the tool shows a warning, fix the redirect rules and run the same URL again to confirm.

Worked Example: Tracing an Old Blog URL

Say you migrated a blog and want to know why an old link loads slowly. You enter example.com/old-post and press Trace Redirects.

The summary reads 4 observed requests, 3 redirect responses and a final status of 200. Because the path has more than three requests, the tool also warns that long chains slow crawling and can dilute SEO signals.

The fix is to point the first URL straight at the destination. One 301 from http://example.com/old-post to https://www.example.com/new-post replaces three hops with one. Run the trace again and you should see 2 requests: the single redirect and the final 200.

How Do You Read the Results?

Each part of the output answers a specific question, and you can act on every one of them.

Observed requests and redirect responses

Observed requests counts every URL the tool fetched, including the final page. Redirect responses counts only the steps that sent you somewhere else. A healthy, well-maintained URL usually has zero or one redirect response. Two is tolerable for an old link. Three or more is worth cleaning up.

Final status and final URL

The final status is the code of the last page reached. A 200 means the chain ended on a working page. If the chain was cut short, the status shows Unverified and the label changes to Last observed URL, so you know the result is not confirmed.

The Type column

A type of http means the server sent a redirect status with a destination. A type of meta-refresh means a page loaded successfully but its HTML told the browser to move on. Meta refreshes are slower and less clear to search engines, so replace them with a server-side 301 where you can.

Why Do Redirect Chains Matter for SEO?

Redirect chains matter because every extra hop adds a network round trip for users and another fetch for crawlers. Google's Search Central documentation says Googlebot follows up to 10 redirect hops, so long chains risk the crawler giving up before it reaches your page.

Chains also make audits harder. Internal links, sitemaps and canonical tags that point at a redirecting URL force every visitor and bot to take the detour. Linking directly to the final address removes the problem at its source.

Security reviews often flag a chain that includes a plain http step. Even if the chain ends on HTTPS, the first hop is unencrypted. Redirecting HTTP straight to the final HTTPS address in one step avoids that.

Who Should Use This Tool?

Anyone who changes URLs or links to pages they do not control can benefit from a quick trace. These are the most common situations.

• Site migrations: confirm that old URLs reach the new ones in a single step after a domain, protocol or folder change.
• Link building and outreach: check that a backlink or short link lands on the page you expect, and see every stop on the way.
• Campaign links: trace tracking or short URLs before you send them, so you know the final landing page and status.
• Developers and server admins: verify new rewrite rules without opening browser developer tools.
• Content teams: find out why an old article link takes noticeably longer to open.

To check many addresses at once, use the bulk HTTP status checker. For a focused check of domain variants, the www redirect checker compares http, https, www and non-www versions.

Best Practices and Troubleshooting

Good redirect hygiene comes down to a few habits you can apply after every trace.

• Aim for one hop. Update old rules so each legacy URL points directly to its current destination, not to another redirect.
• Use permanent codes for permanent moves. A 301 or 308 tells search engines the move is final. Reserve 302 and 307 for genuinely temporary changes.
• Fix the source links. Update navigation, internal links and sitemap entries to the final URL so the redirect is only a safety net.
• Test the exact variant. Trailing slashes, uppercase letters and query strings can change the path. Trace the URL exactly as it appears in your link.
• Re-trace after every change. A new rule can create a loop or an extra hop in a place you did not expect.

If you see a loop message

A loop message means a URL appeared twice in the chain, so two or more rules send visitors in circles. Look for conflicting rules, such as one forcing www while another strips it, or a trailing-slash rule fighting a lowercase rule.

If the chain is incomplete

The tool may report that it could not verify the next destination, that a redirect had no usable Location, or that the redirect limit was reached. Check that the target loads in a browser, that the redirect response includes a valid destination address, and that the chain is not longer than the tool's 10-request budget. For a closer look at what each response sends back, open the HTTP header checker or the HTTP header analyzer.

If the page you typed has no redirect

One request with a 200 status and no redirect responses is a good result. It means that exact URL loads directly.

Limitations to Keep in Mind

This checker observes public HTTP redirects and meta-refresh tags. It does not run JavaScript, so a redirect triggered by a script after the page loads will not appear in the table. Pages behind a login, a private network address or a firewall that blocks automated requests cannot be traced reliably.

The trace is also a snapshot. A server can send different redirects depending on country, device or cookies, so what you see may differ from what a specific visitor sees. If the trace stops early, the status shows as Unverified rather than guessing the rest of the path.

For wider site health checks, browse the Website Audit and Performance tools.

A clean redirect path is one of the easiest technical wins on any site. Enter a URL in the field above, press Trace Redirects, and you will know within seconds whether your links take the shortest route or need a cleanup.