Skip to content

Bulk redirect checker: status, final URL and hops for 1,000 URLs

A bulk redirect checker and HTTP status checker. Paste up to 1,000 URLs and get the status, final address, redirect hops, response time, noindex and canonical of each, in one table.

Up to 1,000 URLs · one per line, commas also work · results in minutes · fill in a sample list

  • Free, no account
  • Up to 1,000 addresses per run
  • Any public http or https address

Example result8 URLs checkedexample-shop.hr

Run it on your site
OK
5
Redirects
0
Chains
1
4xx
1
5xx
0
noindex
1
One row per URL: status after redirects, final URL, hops, time to first byte and the indexability signals
URLStatusResultFinal URLHopsTTFBTypeTitle / canonical
example-shop.hr/old-collection/404Not foundsame07 mstext/htmlNot found

What the bulk redirect checker reports

One row per URL, requested the way a search engine would. Filter by label or download every column as CSV.

  • Status and final URL

    The final status code and the address each URL ends up at after following up to 10 redirects.

  • Every redirect hop

    The full redirect chain with the type of each hop (301, 302, 307 and so on), so temporary redirects that should be permanent stand out.

  • Speed, type and size

    The time to first byte, the content type and the size of every answer.

  • Indexing signals

    For HTML pages: the title, the canonical target and whether a meta robots tag or X-Robots-Tag header says noindex.

  • Labels at a glance

    Every row is labelled OK, redirect, redirect chain, not found, server error, noindex or unreachable, with counts above the table.

  • Filters and CSV

    Filter the table to what needs a look, or download a CSV with every column for a spreadsheet.

  • Gentle on servers

    At most four parallel requests per host, through the same SSRF guard as our reports, so your server is not hammered.

Show 3 more checks
  • Labels at a glance

    Every row is labelled OK, redirect, redirect chain, not found, server error, noindex or unreachable, with counts above the table.

  • Filters and CSV

    Filter the table to what needs a look, or download a CSV with every column for a spreadsheet.

  • Gentle on servers

    At most four parallel requests per host, through the same SSRF guard as our reports, so your server is not hammered.

How the bulk redirect checker works

  1. Paste your list

    Paste up to 1,000 public http or https addresses. The list can mix hosts.

  2. We request every URL

    Each URL is requested with GET, following up to 10 redirects. A run of 1,000 usually finishes in two to four minutes.

  3. Filter and download

    Results appear as they finish, and the run link keeps working if you close the tab. Download the CSV to keep the results past 30 days.

It reads at most the first 256 KB of each answer and does not fetch images, scripts or styles, so it checks addresses and page heads, not full pages.

Bulk redirect checker questions

What do the HTTP status codes mean?

200 means the page answered normally. 301 and 308 are permanent redirects, 302 and 307 temporary ones. 404 means not found and 410 gone for good. 5xx codes such as 500 and 503 are server errors. The table labels every row as OK, redirect, redirect chain, not found, server error, noindex or unreachable, so you can filter to the ones that need a look.

What should I do with the 404s the list finds?

Sort them by value. A 404 on a URL that has backlinks, rankings or internal links loses visitors and signals, so redirect it to its closest equivalent with a 301. A 404 on a URL nobody links to can stay a 404, or a 410 if it is gone for good. Filter the table to Not found and export the CSV to plan the redirects.

Can the bulk checker find soft 404s?

Not directly, because a soft 404 answers 200. Look for rows whose final URL is your home page or a category after a redirect, and for 200 pages whose title says "Not found" or "Page not found"; Google reports both as soft 404s. The final URL and title columns make them easy to spot, and the CSV lets you sort and filter them in a spreadsheet.

Should a removed page answer 404 or 410 Gone?

Either works when there is no replacement. 410 Gone says the removal is deliberate, and Google tends to drop the URL a little faster; 404 is fine too and simpler to set up. If a similar page exists, a 301 redirect to it beats both, because it keeps the visitors and the links the old page had.

How many URLs can I check, and how fast?

Up to 1,000 URLs per run, where the free tier of most crawlers stops at 500. A run of 1,000 usually finishes in two to four minutes, depending on how fast the sites answer. Results appear as they finish, the run link keeps working if you close the tab, and at most four requests run in parallel per host.

Which URLs can I check?

Any public http or https address, and the list can mix hosts. Private and internal addresses, such as localhost, 10.x, 192.168.x or cloud metadata, are skipped by the safety guard and marked as not checked. Each URL is requested with GET, following up to 10 redirects, and the first 256 KB of each answer is read.

How long do you keep the results?

Runs are working data and are deleted after 30 days. Until then the run keeps its own link, so you can come back to it or share it with your developer. Download the CSV with every column if you want to keep the results longer or compare runs in a spreadsheet.

All 59 tools →

Free, funded by the people who use it

No account, no paid plan. Donations keep it running.

Chip in