Free tool · no sign-up

Redirect checker: 301 and 302 redirect tracer

Check 301 and 302 redirects for up to 10 URLs at once. See every hop, its HTTP status and how long it took.

0 / 10
Try an example:
Every hopSee each step with its status code and response time.
301 vs 302Know which redirects are permanent and which are temporary.
Loops and chainsSpot circular redirects and chains that slow pages down.
Browsers and botsCheck as a desktop, mobile, Googlebot or Bingbot visitor.

What a redirect checker is for

After moving a page, switching to HTTPS or adding or removing www, the old addresses should send visitors and search engines to the right place in as few steps as possible. This tool follows each address the way a browser would and shows exactly what happens.

301 and 308 are permanent: search engines pass ranking to the new address. 302, 303 and 307 are temporary and should not be used for lasting moves.

How to check a 301 redirect

Paste the old address into the box and press Check redirects. A correct permanent move shows one hop with status 301 (or 308) that lands on the final page with status 200. If you see a 302, more than one hop, a loop or a 404 at the end, fix the redirect rule so the old URL points straight at the final address.

Use it after a site move, an HTTPS switch, a URL change or when you add or remove www. Choose Googlebot or Bingbot in Check as to confirm search engines get the same result as visitors.

Fixing a loop? Read how to fix ERR_TOO_MANY_REDIRECTS, or build clean rules with the .htaccess and nginx redirect generator.

Frequently asked questions

What is the difference between a 301 and a 302 redirect?

A 301 is a permanent move: browsers and search engines treat the new address as the real one and pass its ranking signals on. A 302 is temporary: search engines keep the old address indexed because they expect it to come back.

How many redirects in a chain is too many?

Aim for one hop from the old address to the final page. Every extra hop adds delay for visitors, and long chains can stop search engines from following them to the end. Point old URLs straight at the final address.

What causes a redirect loop?

A loop happens when two rules send visitors back and forth, for example HTTP to HTTPS on the server and HTTPS to HTTP at the CDN, or www to non-www in one place and the reverse in another. The checker shows the exact hop where the loop starts.

Can I check how Googlebot sees my redirects?

Yes. Choose Googlebot or Bingbot under Check as. If search engines get a different redirect from the one visitors get, that can be a sign of cloaking or a misconfigured rule.

Is the redirect checker free?

Yes. You can trace up to 10 URLs at once with no sign-up, and download the results as a CSV.

Read-only: we request each URL the way a visitor would. Private and internal addresses are blocked.