1. Home
  2. Free tools
  3. Redirect chain checker

Redirect chain checker

See every redirect between the address you type and the page that loads, with the status code and time of each hop, plus the four versions of your domain.

No sign-up.Try:
Check several addresses at once (up to 10)
0 of 10

How to use it

  1. Enter a URL.
  2. Read the chain top to bottom. Green is a normal response, amber a redirect, red an error.
  3. Look at the four-version table. All four should end on the same address, ideally in one redirect.

What it checks

  • Number of redirects and total time
  • 301 and 308 (permanent) versus 302, 303 and 307 (temporary)
  • Redirect loops and chains longer than ten hops
  • Hops that go from https back to http
  • http, https, www and non-www versions of the address
  • The final status code

Limits

  • Follows redirects sent by the server. Meta refresh and JavaScript redirects are not followed.
  • Browser caching of permanent redirects can make your own browser behave differently from this test.
  • Follows a limited number of hops and reports longer chains as a problem.

Public pages only, one page at one point in time. See the methodology and terms.

Frequently asked questions

How many redirects are too many?

One is normal, for example http to https. Two is acceptable but avoidable. Three or more slows the first load and wastes crawl budget, so point the first URL straight at the final one.

What is the difference between 301 and 302?

301 and 308 say a page moved permanently, so search engines transfer the old address to the new one. 302, 303 and 307 say the move is temporary, so the old address may stay indexed.

Why check four versions of my domain?

Visitors and links arrive as http or https, with or without www. If these end on different pages, search engines can see duplicate sites and link value is split.

Does the tool follow JavaScript or meta refresh redirects?

No. It follows server redirects (HTTP status codes with a Location header), which are what search engines and browsers handle first.

My chain ends in an error. What now?

Fix the last URL in the chain, or change the redirect to point at a page that returns 200. Check for a redirect rule that sends everything to a page that no longer exists.

↑ ↓ to moveEnter to openEsc to closeAll results