Bulk URL Status Checker

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, confirm status and redirect output, then expand to migration or sitemap-sized batches.

Recommended first run:

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

Input examples

Small URL batch

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

Migration QA

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

Webhook status report

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

Input Examples

Example: Single batch check

{
  "urls": [
    "https://example.com/page-1",
    "https://example.com/page-2"
  ]
}

Example: Following redirects with chain

{
  "urls": [
    "https://bit.ly/abc"
  ],
  "followRedirects": true,
  "maxRedirects": 5
}

Example: With TLS / certificate info

{
  "urls": [
    "https://example.com"
  ],
  "includeTlsInfo": true
}

Sample output

{
  "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

• broken-link-checker
• website-content-extractor
• article-content-extractor

Related report Actors

Use these follow-on Actors when you want a capped, decision-ready report instead of more raw rows. They use public or user-provided inputs, respect maxChargeUsd, and do not promise rankings, revenue, conversion lifts, or sales outcomes.

• CSV Local Business List Scoring - prioritize cleaned URL/business lists for agency follow-up.
• Website RAG Readiness Audit - audit surviving public pages for RAG/source quality.