Bulk URL Status & Redirect Chain Checker
Pricing
Pay per usage
Bulk URL Status & Redirect Chain Checker
Paste a list of URLs and get one row per URL: final status code, final URL, every redirect hop with its code and Location, loops, timing, canonical and error reason.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Sampon
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Features
Share
Paste a list of URLs and get back one row per URL: where it finally lands, the status code it ends on, and every redirect it passes through on the way, with the code and the Location header of each step.
It is meant for the jobs where a browser is too slow and a single-URL checker is too small: checking a site move before and after launch, cleaning up old links in a sitemap or a spreadsheet, finding redirect chains and loops, or confirming that every http:// address now ends on https://.
What you put in
A list of URLs, one per line. Up to 10,000 per run.
{"urls": ["http://python.org","https://www.example.com/","https://www.python.org/this-page-does-not-exist-404","http://docs.python.org/3/ https://docs.python.org/3/"]}
Addresses without http:// or https:// are checked as https://.
Checking a site move. Put the URL you expect a page to end on after the old URL, separated by a space, a tab or ->. Each row then tells you whether the final URL matches (matchesExpected). This is the quickest way to test a redirect map: paste the two columns of your old-to-new spreadsheet straight in.
http://old.example/about https://new.example/companyhttp://old.example/blog/post-1 -> https://new.example/articles/post-1
Optional settings:
| Setting | What it does |
|---|---|
onlyProblems | Save only the URLs that need attention: errors, 4xx and 5xx, loops, too many redirects, HTTPS to HTTP steps, and expected URLs that don't match. Everything is still checked. |
oneRowPerHop | Save one row for each step of each chain instead of one row per URL. Handy for filtering long chains in a spreadsheet. |
method | HEAD_THEN_GET (default) sends a HEAD request and repeats the step with GET only if the server refuses HEAD. GET always uses GET. |
inspectHtml | On by default. When a step ends on an HTML page, the first 512 KB are read to follow a meta refresh and report the canonical URL. |
maxRedirects | Stop after this many redirects and flag the chain as too long. Default 10. |
timeoutSecs | Time to wait for each answer. Default 15 seconds. |
respectRobotsTxt | Off by default. See below. |
maxConcurrency | Parallel requests across all sites, at most 4. Default 4. |
requestDelayMs | Minimum gap between two requests to the same host. Default 500 ms. |
userAgent | Replace the default User-Agent if a site answers differently to it. |
What you get
One row per URL:
{"position": 1,"inputUrl": "http://python.org","finalUrl": "https://www.python.org/","finalStatus": 200,"finalStatusText": "OK","redirectCount": 1,"redirectTypes": ["301"],"chainText": "http://python.org [301] -> https://www.python.org/ [200]","redirectChain": [{ "step": 1, "url": "http://python.org", "method": "HEAD", "status": 301, "location": "https://www.python.org/", "redirectType": "301", "timeMs": 616 },{ "step": 2, "url": "https://www.python.org/", "method": "GET", "status": 200, "location": null, "redirectType": null, "timeMs": 182 }],"redirectLoop": false,"redirectsToHttps": true,"expectedUrl": "https://www.python.org/","matchesExpected": true,"responseTimeMs": 1308,"contentType": "text/html; charset=utf-8","contentLength": 11345,"canonicalUrl": null,"errorType": null,"errorMessage": null,"issues": [],"problem": false,"requests": 3,"checkedAt": "2026-10-10T07:51:59+00:00"}
A few fields need a word of explanation:
redirectTypeslists each redirect as301,302,303,307,308,meta-refresh(an HTML meta refresh tag) orrefresh-header(aRefreshHTTP header).chainTextis the whole chain on one line, ready to paste into a report.responseTimeMsis the total time of all requests made for that URL.timeMsinside each step is the time of that step alone.contentType,contentLengthandcanonicalUrldescribe the final page.canonicalUrlcomes from the page's<link rel="canonical">tag or from aLinkheader.errorTypeis set when no usable answer came back:DNS(the host name does not resolve),TIMEOUT,TLS(certificate or encryption problem),CONNECTION_REFUSED,CONNECTION_RESET,CONNECTION_CLOSED,INVALID_URL,REDIRECT_LOOP,TOO_MANY_REDIRECTSorROBOTS_BLOCKED.errorMessagegives the detail.issueslabels what is worth a look. These mark the row as aproblem:ERROR,CLIENT_ERROR(4xx),SERVER_ERROR(5xx),REDIRECT_LOOP,TOO_MANY_REDIRECTS,REDIRECT_WITHOUT_LOCATION,HTTPS_TO_HTTP,EXPECTED_MISMATCH,ROBOTS_BLOCKED,INVALID_URL. These are for information only:MULTIPLE_REDIRECTS(two or more hops),TEMPORARY_REDIRECT(a 302, 303, 307 or refresh in the chain),META_REFRESH,CANONICAL_ELSEWHERE(the canonical URL differs from the final URL).positionis the line number in your input. Rows are saved as checks finish, so sort bypositionto get your original order back.
The dataset has three table views: URLs (the overview), Expected vs final (for site moves) and Steps (for runs with oneRowPerHop).
How it checks
- Redirects are followed one step at a time by the Actor itself, so every hop is recorded rather than only the end result.
- Each step starts with a HEAD request. If the server refuses HEAD, the same step is repeated with GET. When a step ends on an HTML page and
inspectHtmlis on, one GET reads the top of the page for a meta refresh and the canonical tag. Non-HTML files such as PDFs and images are never downloaded. - Cookies set during a chain are kept for the rest of that chain, the way a browser would. A page that redirects to itself once to set a cookie is therefore not reported as a loop.
- A loop is reported when the chain comes back to an address it has already visited with nothing changed.
robots.txt
By default robots.txt is not consulted. This Actor is a point check of addresses you supply: it makes one request per redirect step for each URL, much like opening the link yourself, and it does not discover or crawl any other pages.
If you prefer, turn on respectRobotsTxt. Each site's robots.txt is then read once before the first request, URLs it disallows are skipped and reported with the error ROBOTS_BLOCKED, and any crawl delay it sets is applied.
Price
Free for now. You only pay Apify's usual platform usage for the run. In our test, 30 URLs (20 of them on the same site) took about 32 seconds, which at the default 256 MB memory is well under one cent of usage. A per-URL price may be added later. If that happens, it will be shown on this page before it applies to you.
Speed and limits
- At most 4 requests run at once, and each host gets at least 500 ms between requests by default. URLs from different hosts are mixed so that this gap costs little time. Many URLs on one single site are the slow case: 1,000 URLs on one site take roughly 15 to 25 minutes with the defaults. If the site is your own, you can lower
requestDelayMs. - Redirects made by JavaScript are not followed. Only HTTP redirects, the
Refreshheader and meta refresh tags are. - Some sites answer automated requests differently from browsers, for example with 403 or a challenge page. The row then shows what the site answered to this checker, which may not be what a visitor sees.
contentLengthcomes from theContent-Lengthheader. When the server does not send one, it is filled in only for HTML pages that were read in full.
This Actor is an independent tool. It is not affiliated with the owners of the websites you check.