HTTP Status Code Checker & Bulk URL Checker API

Check current HTTP status evidence for up to 10,000 URLs per run. The actor sends an HTTP GET request to each URL and returns the final status code, redirect chain, response time, content type, final URL, and an explicit broken/error flag. The three-URL first run costs at most $0.0031 including the minimum start event.

Use cases

• SEO audits — find 4xx/5xx pages and redirect chains before migrations or content releases
• Bulk URL validation — check URL lists from sitemaps, spreadsheets, CRMs, or link exports
• Redirect mapping — capture 301, 302, 307, and 308 hops during site migrations
• Monitoring workflows — schedule repeated point-in-time checks for critical URLs
• Link QA — identify connection errors, timeouts, moved pages, and changed content types

Input

Field	Type	Default	Description
urls	array of strings	Three deterministic test URLs	URLs to check, one per line
followRedirects	boolean	true	Follow redirects and record the chain
maxRedirects	integer	10	Maximum redirects per URL
timeout	integer	30	Request timeout in seconds
concurrency	integer	10	Parallel requests
maxResults	integer	3	Total paid URL-record cap; increase up to 10,000 for bulk checks

Output

Each non-empty input URL produces one record:

Field	Type	Description
url	string	Original URL submitted
statusCode	integer	Final HTTP status code; 0 when no HTTP response was received
statusText	string	Standard status text such as OK or Not Found
finalUrl	string	Final URL after followed redirects; empty when the request failed before a response
redirectChain	array	Ordered redirect hops with URL and status code
responseTimeMs	integer	Total elapsed time for the request and followed redirects
contentType	string	Final response Content-Type header
isBroken	boolean	true for HTTP 4xx/5xx responses or request/connection errors
error	string	Request, DNS, TLS, timeout, or redirect-limit error when present

Example output

{
  "url": "http://github.com",
  "statusCode": 200,
  "statusText": "OK",
  "finalUrl": "https://github.com/",
  "redirectChain": [
    { "url": "http://github.com", "statusCode": 301 }
  ],
  "responseTimeMs": 142,
  "contentType": "text/html; charset=utf-8",
  "isBroken": false
}

Interpretation limits

Results are point-in-time network evidence from the actor's execution environment, not a continuous uptime guarantee. A 2xx response does not prove that page content, JavaScript, authentication, or application behavior is correct. WAFs, robots policies, rate limits, geolocation, and transient network conditions can produce different results for another user or region. Re-run important checks and inspect the target directly before acting on a status change.

Bulk reliability and cost control

The actor checks and saves large URL lists in bounded 500-record batches rather than sending one oversized dataset request. maxResults is a total response cap, and an Apify maximum-total-charge limit can reduce it further before requests begin.

Pricing

Pay per event: $0.0001 minimum actor-start event plus $0.001 per output record (about $1 per 1,000 checked URLs, plus the start event). The three-record default costs at most $0.0031. Apify displays an estimated maximum before each run.