Bulk Link & Redirect Audit – Status Codes and Chains

What does this Actor do?

Audit a supplied list of public HTTP(S) URLs for HTTP status and redirect chains. Identify 404/410 responses, server errors and restricted or rate-limited responses separately.

Why use it?

Use bounded batches for repeatable data workflows, CSV exports and Apify API integrations. No browser, paid proxy or model calls are required.

Input and first run

1. Supply the source list in the Input tab.
2. Set maxItems and your maximum Apify charge.
3. Run and inspect the dataset plus REPORT.
4. Download OUTPUT.csv or use Apify dataset JSON, CSV or Excel exports.

{
  "urls": [
    "https://example.com/"
  ],
  "maxItems": 5
}

• urls: One to one hundred public HTTP(S) URLs. Credentials and private/reserved addresses are rejected.
• maxRedirects: Maximum redirects per URL, with target DNS validation and connection pinning on every hop.
• maxItems: 1–1000 output rows; default 100.
• maxRunSeconds: 30–600 seconds; default 120.

Output

Field	Type	Meaning
recordId	string	Observed recordId; absent source values remain null.
inputUrl	string	Observed inputUrl; absent source values remain null.
finalUrl	string	Observed finalUrl; absent source values remain null.
statusCode	integer	Observed statusCode; absent source values remain null.
classification	string	Observed classification; absent source values remain null.
redirectCount	integer	Observed redirectCount; absent source values remain null.
redirectChain	array	Observed redirectChain; absent source values remain null.
method	string	Observed method; absent source values remain null.
checkedAt	string	Observed checkedAt; absent source values remain null.

REPORT contains emittedCount, errors, stopReason and paymentsVerified=false. STATE is a recovery checkpoint for this same run and parsed input. OUTPUT.csv quotes values and escapes potential spreadsheet formulas. This protection does not cover other exporters. Source values and observation times are preserved rather than invented.

Pricing

Proposed launch price: $0.003 per dataset row ($3 per 1,000), with no start event. Monetization is a separate provider setting: always inspect the actual Pricing tab. No paid row for invalid input, failed fetch or a duplicate already emitted in the same run. Completed HTTP error observations, including 404/410, are charged audit results.

Limits and recovery

Checks the supplied URLs only; does not discover links by crawling HTML or execute JavaScript. HEAD first, GET fallback for 405/501. A 200 response does not prove content correctness or exclude soft 404s. A 403/429 is inconclusive, not proof of a broken link. Network/DNS/unsafe-target/redirect failures are reported without a paid dataset row. HTTP 404/410 and other completed HTTP observations are useful audit results and are charged. HTTPS downgrade redirects remain visible. No bypass of access controls.

Requests are sequential, bounded and rate-limited. Only public HTTP(S) targets on standard ports are allowed, with DNS address validation and pinning. No retries against blocked pages or paid proxies. On restart, existing rows are checked against a pending-write checkpoint. An uncertain missing write stops for review; this is not an exactly-once billing guarantee. Inputs must remain identical on recovery. A fresh run is a new paid batch. Error reports may contain supplied source identifiers; do not include secret-bearing URLs.

API, source and support

Call through the Apify API tab or MCP and export structured results. Only process sources you have permission to access and reuse; public accessibility does not itself grant redistribution rights. This pilot is independent of Shopify and Greenhouse. Report reproducible issues through the Issues tab with a run ID and error code; never include credentials.