Redirect chain checker

Follow every hop and spot loops and slow chains.

FreeNo sign-upNothing to install

Follows up to 10 redirects, checking each hop. Redirects done with JavaScript or a meta refresh aren't followed.

Built with atrby · Open live demo

What it does

One redirect is normal. Several in a row slow every visit down, and each extra hop is one more thing that can break the next time you change your site.

This checker follows a URL one hop at a time, the way a crawler would, and shows the status code, address and response time of each step. It flags chains longer than one hop, temporary redirects, hops over plain HTTP, and loops.

How to use it

  1. 1Paste the address in URL. Include http:// to test the plain HTTP version; without a protocol, the check starts at https.
  2. 2Press Follow the redirects.
  3. 3Read the numbered list top to bottom. Each row is one request with its status and time; the last row is where the URL ends.
  4. 4Check the findings: the destination, the number of redirects, any temporary ones and any hop over HTTP.

Which redirect code to use

For a moved page, a domain change or an http to https upgrade, use 301 or 308. Keep 302 and 307 for short-term cases such as maintenance.

  • 301 Moved Permanently: a new address for good. Search engines move the old URL's signals to it.
  • 308 Permanent Redirect: the same, but the method can't change, so a POST stays a POST.
  • 302 Found: temporary. Search engines usually keep the old URL in results.
  • 307 Temporary Redirect: temporary, keeping the method.

Fixing a chain

Chains build up over the years: http to https, then to www, then an old slug to a new one.

  • Point each old URL straight at the final address in one redirect.
  • Update internal links, the sitemap and canonical tags to the final address.
  • Keep old redirects in place; other sites may still link to them.
  • Watch for loops, where A redirects to B and B back to A.

What this tool sees

It follows up to 10 server redirects, sent as a status code with a Location header. Redirects done in JavaScript or a meta refresh tag aren't followed, so a chain can stop at a 200 that still moves a browser on.

Questions

How many redirects is too many?

Aim for one at most. The checker passes one, asks you to check two, and marks three or more for fixing.

Is a 302 bad for SEO?

Not when the move really is temporary. The problem is a 302 left in place for a permanent move, because search engines may keep showing the old URL.

What's the difference between 301 and 308?

Both are permanent. A 308 requires the same method and body on the next request; a 301 lets browsers turn a POST into a GET. For page moves, either works.

Why does my URL show an error instead of a status?

The server didn't answer in time, the connection failed, the address isn't public, or the redirects looped or passed 10 hops. The last row says which.

More free tools

All 29 tools

Your site is tuned. Is the traffic paying?

atrby shows which sources, pages and AI assistants bring paying customers. Cookieless, from $19 a month.