Free Online URL Redirect Checker
Trace the full redirect chain for any URL — see every 301, 302, 307 hop, the final destination, and detect redirect loops. Free online tool.
100% Client-Side · Your data never leaves your browserHow to Use URL Redirect Checker
Enter any URL (with or without https://) in the input field and click Check Redirects or press Ctrl/Cmd+Enter. If you omit the protocol, https:// is added automatically.
The tool follows every redirect hop server-side and returns the full chain to your browser. Each hop shows:
- A color-coded status badge — green for 2xx, blue for 3xx, red for 4xx/5xx.
- The URL at that hop, truncated if long (hover for the full URL), with a copy button.
The final destination is highlighted in green. If a redirect loop is detected, an amber warning banner is shown. The summary line shows the total number of hops.
Frequently Asked Questions
What is the difference between 301, 302, and 307 redirects?
A 301 is a permanent redirect — search engines transfer link equity (PageRank) to the destination and update their index. A 302 is temporary — search engines keep the original URL indexed. A 307 is also temporary but preserves the original HTTP method (important for POST requests), whereas a 302 may change POST to GET.
How many redirects can a URL chain have?
Most browsers and HTTP clients stop following redirects after 20–30 hops and return an error. Search engine crawlers typically follow up to 5 redirects. Each hop adds latency, so long redirect chains hurt page load speed and SEO.
What is a redirect loop?
A redirect loop occurs when a URL in the chain redirects back to a URL already visited, creating an infinite cycle. Browsers detect this and show an error like "Too many redirects". This tool highlights loop detection in amber.
Do redirects affect SEO?
Yes. 301 permanent redirects pass most link equity to the destination, but each hop loses a small amount. 302 temporary redirects do not transfer equity. Redirect chains longer than 3 hops can dilute link equity significantly and slow down crawling.
How do HTTPS redirects work?
When a site enforces HTTPS, visiting the HTTP URL (port 80) triggers a redirect — usually a 301 — to the HTTPS version. Some sites also redirect the non-www version to www (or vice versa), resulting in two hops before the final destination.
Is my URL data stored or logged?
No. The redirect check is performed by a Cloudflare Pages Function that follows the URL server-side and returns the chain to your browser. No URLs or results are stored or logged after the request completes.