Bulk redirect checker

What it does

Each URL is followed through its full redirect chain on the server (HTTP and meta-refresh redirects; likely JavaScript redirects are detected, not executed), exactly like the single redirect checker — this just runs many at once and lays the results out as a sortable, exportable table. Click any row's ↗ to open it in the single checker for the hop-by-hop view.

Validating a migration (old → new)

Paste two columns straight from your redirect spreadsheet — old URL then a tab or comma then the expected new URL — and each row gets a verdict: Pass (lands on the expected page), Mismatch (redirects somewhere else), or Fail (broken final, or a loop). By default the comparison is lenient — http/https, www, and a trailing slash are treated as equal — so you don't get false mismatches. Tick Strict match for an exact comparison. An expected value can be a full URL or just a path like /new-page.

The flags

loop

The chain redirects back on itself — the page is unreachable.

broken

The final response is a 4xx/5xx (or no response). The redirect lands on a dead page.

chain

More than one redirect hop. Google follows chains but they waste crawl budget and dilute signals — collapse them to a single hop.

temp

A temporary redirect (302/303/307, or meta/JS) in the chain. For a permanent move you almost always want a 301.

http

The final URL is insecure (http://). Usually the redirect should end on https.

Limits

Up to 100 URLs per run, checked a few at a time to stay polite to the shared endpoint; results stream in as they finish and rows that time out are marked rather than dropped. Bot user-agents set the request header only — sites that verify crawlers by IP still see a non-bot address.