Redirect Chain Checker

Paste your redirect rules and see which ones chain, loop or conflict, and where each one finally lands.

How to use

What it checks and how it works

The checker follows each rule through the others: if rule A sends /a to /b and rule B sends /b to /c, then /a is a chain of two hops and should go straight to /c. A rule that returns to a URL it already visited is a loop. Google's documentation says its crawlers follow up to 10 redirect hops, so a longer chain is flagged as too long. It compares URLs in their decoded form with trailing slashes ignored, so an Arabic slug and its percent-encoded form match. It checks the rules you paste. It does not request your live URLs, so it cannot see redirects added by plugins, CDNs or the server outside your list.

Why avoid redirect chains?

Each hop adds a request and a delay, and a long chain can stop a crawler before it reaches the page. Google's documentation says its crawlers follow up to 10 hops. Pointing the old URL straight at the final one avoids both problems.

What counts as a loop?

A set of rules where following them returns to a URL already visited, such as /a to /b and /b to /a. Browsers and crawlers give up on loops.

Does it test my live site?

No. It checks the rules you paste, in your browser. To see what your server really does, request the URL with a crawler or your browser's network panel.

Sources

Related tools

Privacy

Runs in your browser; nothing is uploaded. The interactive tool needs JavaScript.