Redirect Checker
Short answer
Follow a URL's redirects hop by hop to its final address, with the status code and target of each hop, and spot redirect chains and loops.
What it does not do: It follows server-side HTTP redirects only; meta refresh and JavaScript redirects are not followed because the page is not rendered.
What It Does
Follows every redirect from a starting URL to its final destination, returning the status code and target URL at each hop. Flags redirect chains longer than a single hop and redirect loops.
Why It Matters
Every extra redirect adds a round trip before the page starts to load, and every hop is one more rule that can break. Site moves and CMS plugins often leave chains behind that nobody notices until a link from another site stops landing where it should. Tracing a URL shows the whole path at once.
How It Works
-
Enter your starting URL and click Trace
-
We follow each redirect with a fresh request, capturing status + Location
-
Detect chains longer than a single hop, and redirect loops
-
Return a hop-by-hop table with each status code and destination, plus the total time for the chain
Sample input + output
url: https://rankproof.eu/pricing/
Single redirect — One clean redirect with a 301 status. redirect hops: 1 final status: 200 total time (ms): 18 Redirect chain: 1. 301 https://rankproof.eu/pricing/ 2. 200 https://rankproof.eu/tools
How to read the result
- Redirect hops (1) and headline
- How many redirects stand between the address you entered and the page that finally answers. 0 or 1 is fine; 2 or more is flagged as a chain to shorten, and a loop is a critical error. The sample has one clean 301.
- Final status (200)
- The status of the last address in the chain. 200 means the redirect ends on a working page. A 404 or 410 at the end means the redirect points to something that does not exist, and a 5xx means the target is failing.
- Total time (18 ms)
- The time our server took to follow the whole chain. It is measured from our server, not from your visitors' devices, so treat it as a comparison between your own redirects rather than a page-speed figure.
- Redirect chain
- Each step with its status and address. In the sample the retired /pricing/ page answers 301 and the next step, /tools, answers 200. We follow up to 10 steps, wait up to 5 seconds for each, and flag a first step that uses 302.
- What is not followed
- Only HTTP redirects sent by the server count. A meta refresh or a redirect done by JavaScript happens in the browser after the page loads, so it is not seen here, and search engines treat it as a weaker signal.
Who Uses This
-
Migration Lead
Post-migration sweep — trace every old URL to confirm it lands at the new equivalent in exactly one hop.
-
Technical SEO
Trace the URLs that other sites link to and replace any chain with a single direct redirect.
-
DevOps Engineer
Trace key URLs after every deploy that touches routing and catch new multi-hop chains.
Common problems and how to fix them
-
A chain of two or more hops
Typical chains are http → https → www → new path. Change the rules so the first redirect points straight at the final address, and update links to use that address.
# nginx server { listen 80; server_name example.com www.example.com; return 301 https://example.com$request_uri; } -
A permanent move uses 302
Use 301 or 308 for a page that has moved for good; keep 302 and 307 for genuinely temporary moves such as maintenance.
# nginx location = /old-page { return 301 /new-page; } # Apache (.htaccess) Redirect 301 /old-page /new-page -
A redirect loop
Two rules send visitors back and forth, often a CMS setting and a server or CDN rule that disagree about https, www or a trailing slash. Keep the rule in one place and remove the other.
-
The redirect ends on a 404 or on the home page
Point the old address at the closest equivalent page. If there is none, let it answer 404 or 410: search engines treat a redirect to an unrelated page as a soft 404.
-
Internal links still point at old addresses
Each internal link to a redirect costs an extra request. Update menus, body links, canonical tags and the sitemap so they use the final address.
Frequently Asked Questions
- 301 or 302 — which should I use?
- Use 301 (or 308) when a page has moved for good; Google treats it as a strong signal that the new URL is the one to show. Use 302 (or 307) for temporary moves, such as a short campaign.
- How many hops does Google follow?
- Google's crawler follows up to 10 redirect hops and reports an error after that. Each hop still adds delay, so point every old URL straight to its final address.
- Does meta-refresh count as a redirect?
- Google treats an instant meta refresh as a permanent redirect and a delayed one as a temporary redirect. A server-side redirect is still the most reliable option, and it is the only kind this tool follows.
- Why is my redirect chain so long?
- Usually separate rules run one after another: www to non-www, HTTP to HTTPS, then a trailing-slash rule. Combine them into one rule in your CDN, proxy or web server.
- Can it detect JavaScript-based redirects?
- No — we follow HTTP-level redirects only. JavaScript-driven navigation isn't triggered because the page is never rendered.
Sources
The documentation this tool and the explanations on this page are based on.
- Redirects and Google Search — Google Search Central
- How HTTP Status Codes Affect Google's Crawlers — Google Search Central
- Redirections in HTTP — MDN Web Docs
- RFC 9110: HTTP Semantics — RFC Editor