Bulk URL Status Checker

CTA: Open Input (link below) → leave defaults (1 URL) → Start. First paid proof ≈ USD 0.009. Open Input (leave defaults → Start) Paid first run ≈ USD 0.009 total (1 URL): Actor Start USD 0.001 + 1×USD 0.008. Open Console Input (deep link above) and run this JSON.

{
  "urls": [
    "https://example.com"
  ],
  "concurrency": 3,
  "timeoutMs": 10000,
  "followRedirects": true,
  "delivery": "dataset",
  "dryRun": false
}

Run the next report

• Turn status and redirect findings into a source-linked report/export handoff with Site QA Broken Link Report Scraper.
• Turn the same URL set into a content issue report with Site QA Content Report Scraper.
• Run an indexability and crawler-access report with Site QA Indexability AI Crawler Report Scraper.

SEO teams, site migration teams, QA teams, and web operations use this actor to turn URL lists supplied by the user into a clean dataset for Site QA & Content Intelligence Pack. Provide focused source inputs, keep the first run small, and expand only after the output shape is useful. Each emitted row includes source context, timestamps, and fields designed for monitoring, QA, research, or workflow handoff.

Store Quickstart

Start with a small URL list as the source step for a value workflow. Confirm status and redirect findings, then send the same URLs to the linked broken-link, content, or indexability report actor.

Recommended first run:

{
  "urls": [
    "https://example.com",
    "https://example.com/docs"
  ],
  "followRedirects": true,
  "delivery": "dataset",
  "dryRun": false
}

Use with Apify MCP

Exact actor: taroyamada/bulk-url-health-checker

Sample input JSON:

{
  "urls": [
    "https://example.com"
  ],
  "concurrency": 3,
  "timeoutMs": 10000,
  "followRedirects": true,
  "delivery": "dataset",
  "dryRun": false
}

Input examples

Small URL batch

{
  "urls": [
    "https://example.com",
    "https://example.com/docs"
  ],
  "followRedirects": true,
  "delivery": "dataset",
  "dryRun": false
}

Migration QA

{
  "urls": [
    "https://old.example.com/page"
  ],
  "followRedirects": true,
  "includeHealthyRows": false,
  "delivery": "dataset",
  "dryRun": false
}

Webhook status report

{
  "urls": [
    "https://example.com/pricing"
  ],
  "delivery": "webhook",
  "webhookUrl": "https://example.com/webhook",
  "dryRun": false
}

Value path output preview

The status row below is the source step. The paid deliverable is produced by the linked report actor:

{
  "actorName": "site-qa-broken-link-report-scraper",
  "rowType": "url_health_report",
  "billingEventName": "url-health-report-generated",
  "sourceUrl": "https://example.com",
  "issueCount": 1,
  "reportStatus": "action_needed"
}

Raw status sample

{
  "meta": {
    "actorName": "bulk-url-health-checker",
    "actorTitle": "Bulk URL Status Checker",
    "bundle": "Site QA & Content Intelligence Pack",
    "fetchedAt": "2026-05-06T00:00:00.000Z",
    "totalRows": 1
  },
  "rows": [
    {
      "actorName": "bulk-url-health-checker",
      "rowType": "url_health_finding",
      "url": "https://example.com/missing",
      "statusCode": 404,
      "finalUrl": "https://example.com/missing",
      "responseMs": 240,
      "severity": "error",
      "fetchedAt": "2026-05-06T00:00:00.000Z"
    }
  ],
  "warnings": []
}

Output fields

• rowType
• url
• statusCode
• finalUrl
• redirectChain
• responseMs
• severity
• warnings
• fetchedAt

Rows also include source URLs, fetch timestamps, warnings when a source is partial, and stable IDs when the workflow supports recurring change detection.

Pricing and no-change runs

$0.001 actor start and $0.008 per emitted URL finding row. Healthy no-issue batches can be held out of the default dataset when configured.

The default dataset is the billable surface. Dry runs, validation-only runs, missing-key warnings, and unchanged recurring polls should not write payable default-dataset rows.

Compliance guardrails

• Check supplied public URLs with reasonable concurrency.
• Use for migration QA, SEO, and site operations.
• Do not use aggressive settings against third-party infrastructure.
• Do not use provider emblems or wording that implies approval by an upstream data provider.

See Also

The three report paths in Run the next report are the complete Site QA handoff for this actor. Use one of those paths instead of adding more raw status rows.