See every hop
Trace 301, 302, 303, 307 and 308 responses, HTTP Refresh and HTML meta refresh. Find loops, missing destinations and chains that end in errors.
FREE TECHNICAL SEO TOOL No signup
Free bulk redirect checker.
Follow the chain, inspect the headers, and find what needs fixing.
Check one link or a thousand — with evidence at every step.
↳ Full redirect trace◷ Last-Modified & ETag↓ CSV & JSON export
Check your URLs
01 / INPUT02 / RESULTS
Your redirect report
Preparing your checks…
Checked0
With redirects0
Need attention0
Profile differences0
| URL & destination | Status chain | Redirects | Time | Findings | Details |
|---|
Your first results will appear here. Large batches continue in the background.
Timings measure server-side HTTP requests, not browser page load. User-agent profiles do not reproduce a verified Googlebot visit. Exports include all results, including pending or cancelled checks.
LESS GUESSWORK. MORE EVIDENCE.
A redirect checker that explains the journey.
Inspect the response
Open each step for its HTTP headers and timing. Review Location, Cache-Control, X-Robots-Tag, canonical hints and security headers together.
Test cache validators
Check Last-Modified dates and send separate If-Modified-Since and If-None-Match requests. See whether your server returns 304 or resends the content.
BUILT FOR REAL CHECKS
Before a migration.
After a release.
Whenever a link looks wrong.
Paste your old URLs, compare desktop and mobile responses, then hand the CSV report to your developer. Every result keeps its device profile attached.
Need a deeper page audit? →- Paste up to 1,000 URLs
Use one URL per line. Addresses without a scheme default to HTTPS; fragments are removed and duplicates are merged.
- Choose what to investigate
Compare device profiles, expand domain variants or validate caching. A profile comparison runs two checks for each URL.
- Inspect, filter and export
Filter the entire completed set, expand a trace and download CSV for spreadsheets or JSON for the full evidence.
Redirect checker questions, answered.
Is this bulk redirect checker free?
Yes. You can check up to 1,000 URLs per batch without an account and export CSV or JSON. Duplicate URLs are checked once. Domain variants count toward the URL limit. Abuse prevention limits batches per IP and controls concurrent requests.
What is the difference between 301 and 302 redirects?
301 and 308 indicate a permanent move. 302 and 307 indicate a temporary redirect; 303 directs the client to another resource, commonly after a form submission. A temporary redirect is not automatically an SEO error: choose the status that matches the intended behavior.
Does a 200 response mean the redirect is correct?
A final 200 confirms an HTTP success response. It does not prove the destination contains the right content, is indexable or matches your migration plan. Inspect the destination, canonical hints and indexing directives as well.
How are Last-Modified and ETag checked?
For a final 200 response, the checker can send separate conditional GET requests using the returned Last-Modified and ETag values. A 304 confirms the cached representation is still valid. A 200 may mean the content changed or that the server did not use the validator. Missing validators alone are not an error.
Does it execute JavaScript redirects?
No. The checker follows HTTP and meta refresh redirects and flags common JavaScript navigation patterns in the HTML sample. Those patterns are clues, not confirmed browser navigation. HTML inspection is limited to the first 128 KiB.
Why can desktop and mobile results differ?
Websites may use User-Agent headers to choose different routes or content. Compare mode sends desktop and mobile profiles from the same probe location and highlights differences in the final URL or status. It does not emulate a full browser or a verified search engine crawler.
Can anyone else access my report?
Report endpoints are tied to the browser session that created the batch. Reports expire after 24 hours and are excluded from search indexing. Avoid submitting URLs containing passwords, access tokens or other sensitive information.
Why was a URL blocked or a trace stopped?
Only public HTTP and HTTPS addresses on their default ports are supported. Private networks, loopback addresses and unsafe redirect targets are blocked. A trace stops after 10 redirects or its time budget; the collected evidence remains available.