Redirect Checker
Trace URL redirect chains. See every hop, HTTP status code, and final destination — free online redirect test tool.
What Is a Redirect Checker?
A redirect checker (also called a redirect test tool) traces the full path a URL takes before reaching its final destination. When you enter a URL, the tool follows every HTTP redirect — showing you each hop, its status code, and the next location header — so you can see exactly how a browser or search engine crawler would navigate the chain.
Redirects are a normal part of the web — they handle URL changes, enforce HTTPS, consolidate www/non-www versions, and route traffic after site migrations. But poorly configured redirects (long chains, redirect loops, or the wrong status code) cause slower page loads, wasted crawl budget, and potential loss of SEO link equity. This free online redirect checker helps you diagnose all of those issues in seconds.
HTTP Redirect Status Codes
| Code | Name | Permanent? | Use case |
|---|---|---|---|
| 301 | Moved Permanently | Yes | Site migrations, www→non-www, HTTP→HTTPS |
| 302 | Found (Temporary) | No | Temporary moves, A/B testing |
| 303 | See Other | No | POST→GET redirect after form submit |
| 307 | Temporary Redirect | No | Temporary redirect preserving HTTP method |
| 308 | Permanent Redirect | Yes | Like 301 but preserves HTTP method |
Frequently Asked Questions
What is the difference between a 301 and 302 redirect?
A 301 redirect is permanent — it tells search engines that the original URL has moved permanently to the new URL, and signals them to transfer link equity (PageRank) from the old URL to the new one. A 302 redirect is temporary — search engines keep the original URL indexed. Use 301 for permanent URL changes, site migrations, and HTTP to HTTPS redirects. Use 302 only when the original URL will return in the future.
What is a redirect chain and why is it bad?
A redirect chain occurs when URL A redirects to URL B, which then redirects to URL C. Each hop adds latency for users and dilutes link equity. Search engines follow redirect chains but typically cap the number of hops they will follow. Best practice is to redirect URL A directly to the final destination URL, bypassing any intermediate hops. Use this tool to identify and collapse redirect chains.
How many redirects are too many?
More than one redirect between the original URL and the final destination is generally a chain worth fixing. While Googlebot will follow chains of up to 5 hops in a single crawl session, each additional hop reduces crawl efficiency and adds latency. For best performance and SEO, all URLs should redirect to the final canonical URL in a single hop.
Do redirects pass link equity (PageRank)?
Yes — 301 permanent redirects pass nearly all link equity to the destination URL. Google has confirmed that 301 and 302 redirects both pass PageRank equivalently in modern crawlers. However, each redirect hop has a small cost. To maximise equity transfer, ensure important inbound links point directly to the final URL where possible, and collapse any redirect chains so equity flows in one hop.
How do I test if my redirect is working correctly?
Enter the source URL in the field above and click "Check Redirects". The tool shows every hop in the chain, the HTTP status code at each step, and the final destination URL. A correct redirect should show a single hop with a 301 status code pointing to your intended final URL. If you see multiple hops, the wrong status code, or an unexpected final destination, you have a redirect configuration issue to fix.
What causes a redirect loop?
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a longer cycle). This causes browsers to display "Too many redirects" and search engines to stop crawling the URL entirely. Common causes include misconfigured .htaccess rules, incorrect HTTPS redirect settings, conflicting CDN and server rules, or CMS permalink settings clashing with server-level redirects.