Seotoolsdesk.com
Bulk up to 100 • Full hop-by-hop chain • Copy + TXT

Redirect Chain Checker

Paste URLs — we’ll follow redirects and show every hop (status + Location), detect loops, hop limits, and risky changes like https→http.

Paste up to 100 URLs (one per line)
Tip: Short chains are best. A long chain can waste crawl budget and slow users.

Results

Input Final URL Final HTTP Hops Time Issues
Run a check to see results here.
Click a row to show the full redirect chain below.

Quick interpretation

Redirect chains can waste crawl budget and add latency.

  • OK no redirects or a clean 1-step redirect
  • Warning multiple hops, host/scheme changes, missing Location, hop limit
  • Error redirect loops, fetch errors, final HTTP 4xx/5xx

Redirect chain details

Run a check and click a result row to populate this table.
Hop URL HTTP Location
No details yet.
TXT format: hop TAB url TAB http TAB location
Redirects

Redirect chain checker: find slow or risky redirect paths

Redirects are normal, but chains and loops are not. This tool follows redirects hop-by-hop and flags common SEO and performance problems.

What we flag

  • Redirect loops: repeating URLs.
  • Hop limits: chains that are too long.
  • HTTPS downgrade: https → http.
  • Host / www changes: can be fine, but should be intentional.

FAQ

What is a redirect chain?

A redirect chain happens when a URL redirects to another URL, which redirects again, and so on (A → B → C…). Each hop adds latency for users and can waste crawl budget for search engines.

How many redirects are OK?

Best is 0. If a redirect is needed, keep it to one hop (A → B). Anything longer is usually a technical debt problem: old rules stacking up, duplicate canonical versions, or conflicting HTTPS/www/trailing-slash policies.

What is a redirect loop?

A redirect loop is when the chain repeats the same URL(s) again (A → B → A …). Browsers will eventually stop, and bots may drop the URL as unreachable. This tool detects loops by tracking visited URLs in the chain.

Why do you flag “missing Location”?

HTTP 3xx redirects must include a Location header. If a server returns 301/302/307/308 without Location, the client has nowhere to go — this is typically a misconfiguration.

Why is HTTPS → HTTP downgrade dangerous?

Downgrading from https to http can break security assumptions, expose users to interception, and confuse canonicalization. For SEO, the preferred version is almost always HTTPS.

What do “host changed” and “www/non-www switch” mean?

“Host changed” means the redirect ended on a different hostname (example.com → m.example.com or example.com → example.net). “www/non-www switch” is a common canonical consolidation step (www.example.com → example.com or the reverse). Both can be fine — but should be intentional and consistent across the site.

Why can results differ from what I see in a browser?

Some redirects depend on cookies, geo, language, headers, or user-agent. This tool follows HTTP redirect headers using a consistent bot-like request. If a site does JS redirects, consent flows, or device detection, chains can differ.

Does this tool detect JavaScript or meta refresh redirects?

No. This checker focuses on HTTP redirects (3xx + Location). JavaScript redirects and <meta http-equiv="refresh"> require rendering and are not covered here.