# Bulk URL Status Checker (`properscraper/bulk-url-status-checker`) Actor

Check a list of web addresses in bulk: HTTP status code, the full redirect chain, final address, response time, content type and server. Finds broken links, dead domains and redirect loops.

- **URL**: https://apify.com/properscraper/bulk-url-status-checker.md
- **Developed by:** [jake mcclure](https://apify.com/properscraper) (community)
- **Categories:** SEO tools, Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.05 / 1,000 url checkeds

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 Checker

Check a list of web addresses in bulk. For each one you get the HTTP status code, every step of its redirect chain, the final address, the response time, the content type and the server.

No browser is used, so it is fast and cheap: thousands of addresses in a few minutes.

Use it to:

- find broken links (404s), dead domains and server errors in a list of URLs
- check that old addresses redirect to the right new ones after a site migration
- spot redirect chains and loops that slow pages down and waste crawl budget
- verify a list of backlinks, affiliate links or ad landing pages still works
- monitor important pages by running it on a schedule

### Input

| Field | What it does |
|---|---|
| **URLs** | One per line. An address without `http://` or `https://` in front is checked as `https`. |
| **Follow redirects** | On by default: each redirect is followed to the final address and every step is reported. Turn it off to see only the first answer and where it points. |

```json
{
    "urls": ["https://apify.com", "http://github.com", "example.com/old-page"],
    "followRedirects": true
}
```

### Output

One record per address:

```json
{
    "input": "http://github.com",
    "url": "http://github.com/",
    "result": "ok",
    "httpStatus": 200,
    "finalUrl": "https://github.com/",
    "redirected": true,
    "redirectCount": 1,
    "redirectChain": [{ "url": "http://github.com/", "status": 301 }],
    "redirectsTo": null,
    "contentType": "text/html; charset=utf-8",
    "contentLength": null,
    "server": "github.com",
    "lastModified": null,
    "responseTimeMs": 212,
    "method": "HEAD",
    "error": null,
    "scrapedAt": "2026-11-18T12:00:00.000Z"
}
```

- `result` is `ok` (2xx), `redirect` (a redirect that was not followed), `client_error` (4xx, such as 404), `server_error` (5xx) or `unreachable` (nothing answered: dead domain, timeout, refused connection, certificate problem or a redirect loop).
- `httpStatus` is the status of the final address. `redirectChain` lists each redirect on the way there, in order, with its own status.
- `redirectsTo` is filled only when redirects are not followed.
- `responseTimeMs` is the time to the first answer, added up over the redirects.
- `error` explains an `unreachable` result in plain words, for example `Domain not found` or `Timed out`.

A `SUMMARY` record in the run's key-value store counts how many addresses were fine, broken and unreachable.

### Pricing

Pay per result. You are charged once for each address checked, at the per-result price shown on this page, however many redirects it has. Lines that are not web addresses and repeated addresses cost nothing. The run stops as soon as it reaches the maximum charge you set for it.

### Limits

- Each address is asked with a lightweight HEAD request. If the server refuses that or reports an error, it is asked once more with a normal GET, so a page is not called broken just because the server dislikes HEAD.
- Requests to the same site are spaced half a second apart, so a long list of pages on one site takes longer than the same number of pages across many sites.
- Up to ten redirects are followed. Redirects made by JavaScript or a `<meta>` tag inside the page are not seen.
- Some sites answer automated requests differently from a browser (for example with 403). The Actor identifies itself honestly and reports what it was told; it does not disguise itself to get a different answer.
- Each request waits at most 20 seconds.

### Is this allowed?

The Actor asks each address the same question a browser asks before loading a page, once, and downloads nothing. It identifies itself in its User-Agent and paces its requests.

# Actor input Schema

## `urls` (type: `array`):

One per line. An address without http:// or https:// in front is checked as https.

## `followRedirects` (type: `boolean`):

Follow each redirect to the final address and report every step. Turn off to see only the first answer and where it points.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com",
    "http://github.com",
    "https://example.com/this-page-does-not-exist"
  ],
  "followRedirects": true
}
```

# Actor output Schema

## `urls` (type: `string`):

One record per URL checked.

## `summary` (type: `string`):

Totals for the run and, for each batch of URLs, how many results were saved and any error.

# 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 = {
    "urls": [
        "https://apify.com",
        "http://github.com",
        "https://example.com/this-page-does-not-exist"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("properscraper/bulk-url-status-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 = { "urls": [
        "https://apify.com",
        "http://github.com",
        "https://example.com/this-page-does-not-exist",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("properscraper/bulk-url-status-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 '{
  "urls": [
    "https://apify.com",
    "http://github.com",
    "https://example.com/this-page-does-not-exist"
  ]
}' |
apify call properscraper/bulk-url-status-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,properscraper/bulk-url-status-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/GoqQZJJSdEyeXPfnZ/builds/cCJaFFOeuJpqmomyr/openapi.json
