12 min read
How to Check URL Redirects (and Read a Redirect Chain)
Check URL redirects step by step with TrueURL, curl and DevTools, read every hop of a redirect chain, and fix loops, long chains and mixed 301/302 redirects.
Read articleFree redirect tool
Paste a list of URLs to check all their redirects in one run. Each URL is traced to its final destination, and you can export the results as CSV or JSON.
Cloudflare's edge always validates certificates, so this cannot skip the check. Certificate problems are reported in the result.
Sent with the first request, up to 16 KB. JSON bodies are sent as application/json, others as a form, unless you set a Content-Type header.
1 to 50. Browsers stop after 20.
Sites can redirect phones, crawlers and link preview bots differently.
Sent with every request in the chain.
No custom headers.
Enter a value to send this header. Header values are never saved.
Follow <meta http-equiv="refresh"> tags and Refresh headers found in HTML pages.
Follow simple, unconditional redirects such as location.href = "…" in page scripts.
Settings are remembered in this browser. Cookies, header values and the POST body are never saved.
Paste up to 100 URLs, one per line. URLs without http:// or https:// are checked as https. Each URL is checked separately on Cloudflare's edge, a few at a time, with the same engine and Advanced Settings as the single Redirect Chain Checker.
Because every URL is its own check, a slow or failing URL doesn't hold up the rest of the list, and a problem with one site doesn't affect the results for another.
Each row summarises one URL: where it ended up, the final status code, how many redirects it took and any warnings. Look out for:
Export to CSV to work in a spreadsheet, where you can compare each final URL with the target in your redirect map, or to JSON for scripts and further processing.
12 min read
Check URL redirects step by step with TrueURL, curl and DevTools, read every hop of a redirect chain, and fix loops, long chains and mixed 301/302 redirects.
Read articleUp to 100 per run. For more, split your list into batches, or enter your sitemap in the Sitemap Redirect Checker, which checks up to 500 URLs.
Yes. The HTTP method, Max Hops, User-Agent, custom headers and cookies you set are used for every URL in the list. You can, for example, check a whole redirect map with the Googlebot User-Agent.
Paste the old URLs from your map, run the check and export the results to CSV. In your spreadsheet, compare each final URL with the planned target and filter for rows where they differ, where the final status isn't 200 or where it took more than one redirect. Fix those rules, then re-check only the URLs that failed.
CSV opens directly in Excel, Google Sheets or Numbers and is the quickest way to sort, filter and share results. JSON keeps the structure of the data and is better for scripts, monitoring jobs or importing into other tools.
Common reasons are a typo in the URL, a domain that no longer resolves, a server that times out, or a site that blocks requests from data centers. Each row shows the specific error or warning. Try failed URLs again later, or check one in the Redirect Chain Checker to see every hop in detail.
Yes, with no account or sign-up. Fair-use rate limits apply per IP address so the service stays fast for everyone, and the URLs you check aren't stored.