Redirect chain checker
Trace recorded HTTP redirect chains in a crawl export and identify loops or missing targets.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Trace relative or absolute recorded redirect locations through an uploaded URL/status/location graph, detecting loops, missing targets and excessive recorded hops.
Read the source reference ↗A few things to know
Snapshot analysis rather than live crawling. Each URL must appear once. Only standard 301/302/303/307/308 redirects are followed; JavaScript, meta refresh and stateful behavior are outside scope.
When to use this tool
Inspect a redirect chain from recorded crawl data. The tool follows only links present in the snapshot and marks absent targets as unverified.
- Inspect migration redirects.
- Find recorded loops.
- Compare chain lengths.
How to use redirect chain checker
Prepare the inputs
Paste or upload the requested source or crawl-export columns.
Choose the settings
Run the local check; no remote website requests are made.
Review and export
Review flagged rows and confirm them against the actual site.
Try the supplied example
Inputs
data: URL,Status,Location https://example.com/old,301,/new https://example.com/new,302,/final https://example.com/final,200,
Result
The example traces /old through /new to the recorded 200 response at /final in two hops.
What it means
Recheck recorded failures against the live site before making changes.
Common mistakes to avoid
A missing target is unverified
A missing target is unverified.
A snapshot can become stale
A snapshot can become stale.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
Can I enter only a live URL?
No. This version analyzes a CSV snapshot because arbitrary live redirect tracing is restricted by browser security.
Which headers are required?
URL,Status,Location.
Are relative locations supported?
Yes. They resolve against the recorded source URL.
What if a target is absent?
It is reported as unverified, not a successful final response.
Are JavaScript redirects followed?
No. Only recorded standard HTTP redirect statuses are followed.
How are loops detected?
The tool tracks visited URLs in each recorded chain.
Are my inputs uploaded or stored?
Processing happens locally in your browser. This tool does not upload inputs. Downloads stay on your device; sharing or opening them in another service is your choice.
What should I check before using the output?
Snapshot analysis rather than live crawling. Each URL must appear once. Only standard 301/302/303/307/308 redirects are followed; JavaScript, meta refresh and stateful behavior are outside scope.
Explore the topic in the blog
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.