# Bulk URL Status & Redirect Checker (`dr.skywalker/bulk-url-checker`) Actor

Audit thousands of URLs for broken links, redirect chains, and final destinations in one run. Built for SEO audits, site migrations, and link monitoring — you only pay for URLs actually checked, never for timeouts or errors.

- **URL**: https://apify.com/dr.skywalker/bulk-url-checker.md
- **Developed by:** [Luqin Wang](https://apify.com/dr.skywalker) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 33.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 url check job completeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Bulk URL Status & Redirect Checker

Find every broken link and redirect chain on your site in one run. Paste in a list of URLs — or point at a sitemap or URL list file — and get back HTTP status codes, full redirect chains, and final destinations for each one.

Built for SEO audits, broken-link sweeps, and site migrations where you need to verify thousands of URLs without babysitting a script.

### Why this actor

- **You only pay for URLs actually checked.** Billing is computed from results published to the dataset — not from attempts. Timed-out, skipped, or errored URLs are never charged.
- **No lost work.** Every result is published before it is counted, so a failed run can't charge you for data you didn't receive.
- **Full redirect chains.** See every hop (`301 → 301 → 200`), not just the final status — essential for migration and canonical audits.
- **One SUMMARY record.** Totals (requested, checked, OK, broken, errors) land in the `SUMMARY` key-value record, ready for dashboards and reports.

### Input

| Field | Description |
|---|---|
| Paste URLs (one per line) | Paste one URL per line. Used only when no file or URL is provided. |
| Upload URLs file | Upload a text file with one URL per line. |
| Urls list URL | Public URL of a text file with one URL per line. Used only when no file is provided. |
| Timeout per URL (seconds) | How long to wait for each URL before giving up. |
| Max URLs | Maximum number of URLs to check per run. |
| Max redirects | Maximum redirects to follow per URL. |

### Output

- **Dataset**: one item per URL: `url`, `finalUrl`, `status`, `ok`, `redirectCount`, `redirectChain`, `error`
- **Key-value store `SUMMARY`**: JSON totals (`requested`, `checked`, `ok`, `broken`, `errors`)

#### Example result

```json
{
  "url": "https://example.com/old-page",
  "finalUrl": "https://example.com/new-page",
  "status": 200,
  "ok": true,
  "redirectCount": 1,
  "redirectChain": ["https://example.com/old-page", "https://example.com/new-page"],
  "error": null
}
```

### Pricing (pay-per-event)

- **$0.03** per check job
- **$0.0005** per URL checked — only URLs that produced a result

# Actor input Schema

## `urlsText` (type: `string`):

Paste one URL per line. Used only when no file or URL is provided. Example: https://example.com

## `urlsFile` (type: `string`):

Upload a text file with one urls per line.

## `urlsUrl` (type: `string`):

Public URL of a text file with one URLs per line. Used only when no file is provided. Example: https://example.com/URLs.txt

## `timeoutSec` (type: `integer`):

Per-hop timeout allowance. One HEAD probe has a single overall budget of timeoutSec x (maxRedirects + 1) seconds across all redirect hops; if a GET fallback is needed, it receives a fresh budget of the same size.

## `maxUrls` (type: `integer`):

Maximum number of URLs to check per run.

## `maxRedirects` (type: `integer`):

Maximum redirects to follow per URL (capped at 5 as a safety bound).

## Actor input object example

```json
{
  "urlsText": "https://example.com\nhttps://example.com/nonexistent-page-xyz123\nhttps://www.ietf.org",
  "timeoutSec": 15,
  "maxUrls": 1000,
  "maxRedirects": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset with confirmed URL results and, when charged, the additional job-completion receipt.

## `files` (type: `string`):

Key-value store with downloadable result files and summary.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urlsText": `https://example.com
https://example.com/nonexistent-page-xyz123
https://www.ietf.org`
};

// Run the Actor and wait for it to finish
const run = await client.actor("dr.skywalker/bulk-url-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urlsText": """https://example.com
https://example.com/nonexistent-page-xyz123
https://www.ietf.org""" }

# Run the Actor and wait for it to finish
run = client.actor("dr.skywalker/bulk-url-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urlsText": "https://example.com\\nhttps://example.com/nonexistent-page-xyz123\\nhttps://www.ietf.org"
}' |
apify call dr.skywalker/bulk-url-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dr.skywalker/bulk-url-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ql7WHM8NDo51BkRHx/builds/wNMCPw1cSCWWkHlYf/openapi.json