Redirect Chain Checker
Follow every redirect hop for a URL, see 301/302 status codes and response times, and catch chains and loops.
When to check your redirects
- After a site migration, domain change or switch to HTTPS.
- When you change URL structures, such as removing dates from blog URLs.
- When old backlinks or ads point to pages that no longer exist.
- When pages load slowly and you suspect hidden hops, like
http→https→www.
The checker requests each hop individually, records the status code and response time, and flags chains, loops, temporary redirects and error pages at the end of the chain.
Frequently asked questions
What's the difference between a 301 and a 302 redirect?
A 301 (or 308) says the page has moved permanently, so search engines move ranking signals to the new URL. A 302 (or 307) says the move is temporary, so the old URL may stay indexed. Use 301 for migrations and URL changes.
How many redirects does Googlebot follow?
Googlebot follows up to 10 hops, but every extra hop slows the page and wastes crawl budget. Aim for a single redirect from any old URL straight to its final destination.
What is a redirect loop?
A loop happens when a URL redirects back to one already in the chain, for example A → B → A. Browsers show an error and search engines can't index the page.