Redirect Checker Tool Online

Last updated:

Trace the full redirect path of any URL. See every hop, status code, response time, and whether you're losing SEO value through redirect chains or loops.

Enter a URL to trace its redirects:

How the Redirect Checker Works

This tool follows every redirect step from your input URL to the final destination. Here's the process:

  1. Enter a URL, type or paste any web address. If you leave out the protocol, the tool adds https:// automatically.
  2. Follow each hop, the checker makes an HTTP request to the URL. If the server returns a 3xx redirect, it reads the Location header and follows it to the next URL.
  3. Record everything, for each step, the tool records the status code, redirect type, response time, server header, and whether the connection uses HTTPS.
  4. Detect issues, it identifies redirect chains (more than one hop), redirect loops, mixed HTTP/HTTPS transitions, and slow response times.

Why URL Redirects Matter for SEO

Redirects are one of the most common technical SEO elements, and one of the easiest to get wrong. Here's why they matter:

  • Link equity transfer, when you move a page, backlinks pointing to the old URL still carry ranking value. A 301 redirect passes that equity to the new URL. Without it, you lose those signals entirely.
  • Crawl budget, every redirect hop costs Googlebot time. Redirect chains (A→B→C→D) waste crawl budget that could be spent indexing your actual content. Google has indicated it may stop following after a few hops.
  • User experience, each redirect adds 50–300ms of load time. Visitors hitting a chain of redirects experience slower page loads, which directly impacts bounce rates and conversions.
  • HTTPS migration, moving from HTTP to HTTPS requires proper 301 redirects. A 302 (temporary) instead of 301 (permanent) means search engines may not fully transfer your rankings to the HTTPS version.
  • Site migrations, domain changes, URL restructuring, and CMS migrations all require redirect mapping. Broken or circular redirects during migration can tank your traffic overnight.

Use this tool alongside the SSL Certificate Checker to verify that your HTTPS redirects and certificates are working together, or the Meta Tag Checker to confirm the final destination has correct meta tags.

When to Run a Redirect Check

Running a redirect check takes seconds and can prevent serious SEO and usability issues. Here are the most common scenarios:

  • After a site migration, moved to a new domain or restructured URLs? Verify that every old URL correctly reaches the new destination with a single 301 hop.
  • HTTPS setup, after installing an SSL certificate, confirm that HTTP requests redirect to HTTPS with a 301 (not 302) and that no mixed-content loops exist.
  • Shortened or affiliate links, trace shortened URLs (bit.ly, t.co) or affiliate links to see where they actually lead before clicking or sharing them.
  • Debugging 404s, if users report broken pages, check whether the old URL has a redirect in place or if it's returning a 404 directly.
  • Cleaning up redirect chains, over time, URL changes stack up. Check existing redirects periodically to collapse chains (A→B→C) into direct redirects (A→C).

For a broader SEO audit, combine redirect checks with the Robots.txt Tester and Sitemap Checker to ensure your crawling, indexing, and redirects are all aligned. For bulk URL checking across an entire page's links, the HTTP Status Code Checker handles up to 50 URLs at once. To find all broken links on a given page, use the Broken Link Checker.

Redirect Status Codes Explained (301 vs 302 vs 307 vs 308)

Every redirect returns a 3xx HTTP status code that tells browsers and search engines how to treat the move. Here's a quick reference for the codes this tool detects, including when to use each and what it means for SEO.

Code Meaning When to use SEO note
301 Moved Permanently Permanent URL changes: site migrations, HTTP→HTTPS, www to non-www, removed pages mapped to a replacement. Preferred for permanent moves. Passes nearly all link equity to the target and lets the old URL drop from the index.
302 Found (Temporary) Short-term redirects: A/B tests, maintenance pages, geolocation, when the original URL will return. Keeps the original URL indexed. Avoid for permanent moves, ranking signals may not transfer fully.
303 See Other After a form POST, to send the browser to a confirmation page using GET (Post/Redirect/Get pattern). Rare in SEO contexts. Forces the follow-up request to use GET regardless of the original method.
307 Temporary Redirect (method-preserving) Temporary redirects where the HTTP method and body must be preserved (e.g. a POST stays a POST). Treated like a 302 for indexing. The stricter, modern alternative when method preservation matters.
308 Permanent Redirect (method-preserving) Permanent redirects where the method must be preserved, e.g. APIs and POST endpoints that moved. Treated like a 301 for SEO. Passes link equity while keeping POST requests intact.

Next steps

Redirect Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Redirect Checker: FAQ

What does each redirect-hop row show?
Each row shows the requested URL, HTTP or HTTPS, status code, status text, response time, and any server header returned. For a redirect response, it also shows the Location value that points to the next hop.
How should I interpret 301, 302, 307, and 308 results?
301 and 308 indicate a permanent move, while 302 and 307 indicate a temporary one. The 307 and 308 codes preserve the original HTTP method by definition. Choose the code that matches the real duration and application behavior rather than changing it only for the checker.
When does the tool label a result as a redirect chain or loop?
A chain is reported when more than one 3xx response is followed before the final URL. A loop is reported when the same absolute URL appears again in the traced path. Replace chains with a direct redirect and correct the conflicting rules that create a loop.
What should I do if the final status is 4xx or 5xx?
A 4xx final response usually means the destination is unavailable, forbidden, or missing. A 5xx response points to a server or upstream failure. Update the redirect to a working canonical destination, then rerun the trace and confirm the final response is appropriate.
What does status 0, Timeout, or Connection Failed mean?
The checker could not obtain an HTTP response for that hop. Each request has an eight-second limit and the full trace stops after about 30 seconds. DNS trouble, TLS errors, a firewall, bot blocking, or a slow origin can produce this result, so verify from another network or with server logs.
Why does an HTTPS to HTTP downgrade get flagged?
A hop from HTTPS back to HTTP removes transport protection for that request and can introduce another redirect before the secure destination. Point the earlier rule directly to the final HTTPS URL and check CDN, application, and web-server rules for conflicts.
Can this trace differ from what a visitor sees?
Yes. The server sends a GET request with the WebAlohaBot user agent, does not carry a visitor's cookies, and stops after 20 redirects or the 30-second overall limit. Geo rules, authentication, device detection, consent cookies, JavaScript navigation, and POST-specific behavior can produce a different path.
Are checked URLs or responses stored?
The URL is sent to the Web Aloha server so it can make the external requests and return the hop data. This redirect endpoint has no database or result cache and does not persist the URL or response chain after the request completes.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Dealing with Redirect Issues?

We help businesses fix redirect chains, plan site migrations, and set up SEO-friendly URL structures.