Redirect Chain Checker

Paste any URL to trace its full redirect path — every hop, every status code, and whether it loops. Free, instant, no signup.

What this checks & how to fix it

It follows a URL exactly the way a browser or search engine crawler would: request the URL, read the response, and if it's a redirect (a 3xx status with a Location header), follow it and repeat — up to 10 hops. Every hop is recorded with its own status code and redirect type, and the trace stops early if it detects the chain looping back on itself.

How to fix what it finds

  • Multi-hop chains — update the original link or server rule to point straight at the final destination URL, skipping every intermediate hop.
  • Temporary redirects used for permanent moves — switch the response code to a 301 (or 308 if the request method must be preserved) so search engines transfer ranking signal to the new URL.
  • Loops — check your redirect rules (`.htaccess`, `next.config`, CDN/proxy rules, or CMS redirect settings) for two rules that point at each other, directly or through a longer cycle.

Frequently asked questions

What counts as a redirect chain?

A chain is any URL that redirects to a second URL that itself redirects again before finally returning content — two or more hops instead of one. A single hop (like http:// forwarding to https://) is normal and healthy; a chain of three, four, or more hops is what this tool flags.

Why do redirect chains hurt SEO?

Each extra hop adds real latency for every visitor and every crawl, and search engine crawlers allocate a limited crawl budget per site — a long chain burns that budget on redirects instead of on your actual content. Google has also said it may not follow very long chains at all, meaning the final page can simply never get indexed.

What's the difference between a permanent and a temporary redirect?

A 301 or 308 (permanent) tells search engines to transfer ranking signals to the new URL and update their index. A 302, 303, or 307 (temporary) tells them the move is short-lived, so they keep the original URL indexed and typically don't pass ranking signals the same way. Using a temporary redirect for a permanent move is one of the most common causes of pages that mysteriously never re-rank after a URL change.

What is a redirect loop, and why does it fully break a page?

A loop is when a chain eventually redirects back to a URL it already visited, so it never reaches actual content. Browsers detect this and show an error ("too many redirects"), and crawlers give up the same way — the page becomes completely unreachable and un-indexable until the loop is fixed.

How many hops does this tool follow?

Up to 10. In practice a healthy site never needs more than one or two — if this tool stops at 10 without reaching a final page, something is very likely misconfigured (often a loop, which it will flag directly).

Related tools

Command Palette

Search for a command to run...