Bulk Redirect Checker
Paste a list of old URLs and see their status codes, redirect chains and final destinations, for QA after a migration.
What it checks
Paste a list of URLs, one per line. The checker fetches each one, follows any redirects, and reports the number of hops, the full chain, and the final HTTP status. A single 301 or 302 straight to a working page is flagged as clean; a chain of more than one hop, or a URL that doesn't redirect at all, is flagged as a warning; a broken final destination (4xx or 5xx) is flagged as a failure.
Up to 6 URLs are checked per run, so split a long list into batches. Download the results as a CSV for a QA record after a migration or a big permalink change.
When to run it
- Right after you publish a set of redirects, to confirm they actually work.
- Before you retire an old domain, to catch chains, loops or dead ends.
- After a Google Search Console crawl error spike, to check whether specific old URLs are redirecting properly.
Questions people ask
Why only 6 URLs at a time?
Each check makes a live request from the server, and this keeps a single check fast and within the tool's fetch budget. Run it again for the next batch.
What counts as a problem?
No redirect at all (loads directly, whether that's a 200 or an error), more than one redirect hop, or a final page that returns 4xx or 5xx.
Why does it flag a working page with 2 redirect hops?
Each extra hop slows the browser and search engine crawlers down and can leak some SEO value. Point the redirect straight at the final URL instead of chaining through an old one.
Can I check a sitemap's worth of URLs?
Pull the list with the sitemap URL extractor first, then check batches of the ones that actually changed.
Related tools
Last reviewed 30 September 2026.
