Redirect Checker by URL
Check a URL redirect chain, HTTP status codes, final destination, temporary redirects, permanent redirects, and redirect loops.
Redirect review
Review the redirect count, final destination, and each HTTP response in the chain.
Paste a public URL to check its redirect path and final destination.
This checker follows public HTTP redirects at the time of the request. Results can differ by location, cookies, user agent, authentication, CDN rules, or website configuration.
Check where a URL redirects
Paste a public URL to see every redirect step between the address you entered and the final response.
The checker requests each URL separately so you can see 301, 302, 307, 308, and other HTTP responses instead of only seeing the final destination.
This is useful when reviewing changed page URLs, migrations, affiliate links, campaign links, old backlinks, and redirect rules.
A redirect can behave differently for different visitors when a website uses cookies, location rules, login state, device detection, or CDN logic.
Review a redirect chain in three steps
You only need the URL that you want to test.
Paste the original URL
Use the address that visitors or search engines currently reach.
Follow the chain
The checker requests each redirect destination separately and records the HTTP status.
Review the final destination
Check whether the URL ends where you expect and whether unnecessary redirect hops can be removed.
Example redirect chain
Suppose an old HTTP product URL has been moved and the website also enforces HTTPS.
The checker might show HTTP 301 from the HTTP URL to HTTPS, followed by another HTTP 301 to the new product URL, and then HTTP 200 at the final destination.
How to read the redirect results
Redirect status codes tell browsers and crawlers why they are being sent to another location.
301 and 308 are permanent
These status codes indicate that the resource has been moved permanently to another URL.
302 and 307 are temporary
These indicate that the redirect is temporary. Whether that is correct depends on the reason for the redirect.
Shorter chains are easier to maintain
When possible, redirect an old URL directly to its final destination instead of sending visitors through several intermediate URLs.
Loops need to be fixed
A redirect loop sends a request back to a URL already seen in the chain and prevents the visitor from reaching a final page.
Redirect checker questions
Common questions about URL redirects and redirect chains.
What is a redirect chain?
A redirect chain occurs when one URL redirects to another URL that then redirects again before reaching a final response.
Is a 301 redirect always better than a 302?
No. A 301 is appropriate for a permanent move, while a 302 can be appropriate when the change is temporary. The correct status depends on the intended behavior.
How many redirects are too many?
There is no single universal number, but unnecessary hops add latency and complexity. When you control the redirects, sending the original URL directly to the final destination is usually simpler.
Can redirects differ between users?
Yes. Some sites redirect based on country, cookies, login state, device type, experiments, or CDN rules. This checker shows the path returned to the checker request.
Can this detect redirect loops?
Yes. The checker stops if the chain returns to a URL it already requested and reports the detected loop.