Bulk URL Status & Redirect Chain Checker

Check thousands of URLs for broken links, redirect chains and HTTP status — and see every hop, not just where you landed.

Most checkers follow redirects silently and report the final code. This one records each hop, so you can see that a link 301s to http://, then to www, then to the real page — three round-trips that cost you crawl budget and link equity.

What you get

{
  "url": "http://github.com",
  "ok": true,
  "finalStatus": 200,
  "statusClass": "ok",
  "finalUrl": "https://github.com/",
  "redirectCount": 1,
  "httpsUpgraded": true,
  "crossDomain": false,
  "redirectLoop": false,
  "responseTimeMs": 412,
  "redirectChain": [
    { "url": "http://github.com", "status": 301, "location": "https://github.com/" },
    { "url": "https://github.com/", "status": 200, "location": null }
  ]
}

statusClass buckets every result into ok, redirect, not-found, blocked, rate-limited, client-error, server-error or unreachable, so you can filter without writing status-code logic.

Main use cases

• Broken-link audits across a whole site or backlink profile.
• Migration QA. After a replatform, confirm every old URL lands where it should — and in one hop.
• Redirect-chain cleanup. redirectCount > 1 is the list to fix.
• HTTPS coverage. httpsUpgraded shows which links still start on http://.
• Redirect-loop detection, reported explicitly rather than as a timeout.
• Affiliate and outbound link monitoring on a schedule.

Pricing

Event	Price	When
URL checked	$0.001	One URL checked, including every redirect hop

Not charged for URLs that could not be parsed.

1,000 URLs = $1.00. 10,000 URLs = $10.00.

For comparison at the same volume: smart-digital/complete-seo-audit-tool charges $0.04 per page — 40× more, though it runs a broader audit — and automation-lab/http-status-checker adds $0.035 per run on top of its per-URL price. This Actor has no per-run fee at all.

Input

Field	Type	Default	Notes
urls	array	required	Bare domains work: example.com → https://example.com. Up to 20,000.
maxRedirects	integer	10	Hop ceiling. Loops are detected separately.
method	select	GET	HEAD is faster but some servers answer it incorrectly.
concurrency	integer	8	Parallel requests.

Limitations

• No JavaScript. A page that redirects via window.location or a meta-refresh tag reports the status the server returned. Server-side redirects (301/302/307/308) are what this measures.
• Bot protection reports as blocked (401/403) rather than being bypassed. That is the honest result, not a failure to work around.
• Response times include network variance and are indicative, not a benchmark.

Related Actors

• Link Preview API — OpenGraph metadata for the URLs that come back ok.
• Website Brand & Favicon Extractor — brand assets for the same URL list.

Reliability

• Retries on 429 and 5xx with exponential backoff; permanent 4xx errors are not retried.
• Bad input is reported and skipped, never charged.
• One failing target never aborts the rest of the run.
• Concurrency is bounded and configurable — this work is network-bound, so parallel requests, not memory, are what control speed.

Data source and responsible use

Reads only publicly available data. No authentication bypass, no CAPTCHA circumvention, no browser automation.

Not affiliated with any of the services checked.