Does it follow JavaScript redirects?

Only what the redirect API surfaces—meta refresh and JS-only hops may be incomplete.

Why three hops as long?

It is a practical warning threshold for crawl and UX; tighten further if Core Web Vitals suffer.

HTTP versus HTTPS duplicates?

Expect at least one hop for scheme changes—verify they are intentional 301s, not chains.

Fetches may fail with errors—test signed-in URLs with curl or browser devtools separately.

Technical SEO

Live

Redirect Loop Detector

Detect infinite-loop redirects and cycles between URLs.

URLs

One per line, max 25. We trace each redirect chain and flag loops + chains over 3 hops.

X / Twitter LinkedIn Facebook

Start here · How redirect tracing works here

Each line hits the /api/redirects endpoint which follows redirects similarly to browsers, recording status codes and destinations until completion or failure.

Loops repeat a destination already in the hop list. Long chains exceed three hops—often a performance and crawl budget issue even without a literal loop.

Clean traces stop within three hops with no loop. Errors display if a URL cannot be fetched.

When to use this tool

Post-migration validation
Batch legacy URLs after DNS cuts to confirm 301 paths terminate without spirals.
Vendor redirect exports
Paste CSV-first-column URLs from staging sign-off lists.
International hreflang maintenance
Ensure country toggles do not bounce users through redundant regional hops.
Affiliate or tracking parameters
See whether marketing query parameters trigger unnecessary intermediary responses.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

Loop badge

Try this

Include a staging URL that ping-pongs between two paths.

What to look for

The card shows a rose loop badge and enumerates repeated hosts in order.

Long chain badge

Try this

A chain with more than three HTTP steps but no cycle.

What to look for

Amber hops badge nudges you to consolidate intermediates into one hop.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

Step 1 — Collect URLs
Up to 25 unique lines; blank lines ignored.
Step 2 — Trace batch
Click Trace and wait for per-URL cards to populate.
Step 3 — Triage by summary tiles
Clean, long chains, and loops counts prioritize engineering tickets.
Step 4 — Read hop rows
Status chips highlight 3xx versus errors so you can screenshot exact steps.
Step 5 — Pair with migration tooling
Map intended targets in redirect map generator and validate site-wide in post migration auditor.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Redirect Loop Detector does one job: detect infinite-loop redirects and cycles between URLs. It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.

FAQ

Does it follow JavaScript redirects?: Only what the redirect API surfaces—meta refresh and JS-only hops may be incomplete.
Why three hops as long?: It is a practical warning threshold for crawl and UX; tighten further if Core Web Vitals suffer.
HTTP versus HTTPS duplicates?: Expect at least one hop for scheme changes—verify they are intentional 301s, not chains.
Auth-walled URLs?: Fetches may fail with errors—test signed-in URLs with curl or browser devtools separately.