# HTTP Status Code Checker - Bulk URLs & Redirect Chains (`dltik/http-status-checker`) Actor

Bulk-check HTTP status codes and full redirect chains for any list of URLs. For each URL: final status, every redirect hop (status + Location), response time, content-type and server. Pure HTTP, reads headers only — fast and cheap. Great for SEO migrations, link audits and uptime spot-checks.

- **URL**: https://apify.com/dltik/http-status-checker.md
- **Developed by:** [Walid](https://apify.com/dltik) (community)
- **Categories:** Developer tools, SEO tools
- **Features:** Limited permissions
- **Stats:** 43 total users, 16 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 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

## HTTP Status Code Checker — Bulk URLs & Redirect Chains

> ⭐ **Bookmark this actor** so bulk HTTP status checks are one click away whenever you run a migration, audit a sitemap, or vet a list of links.

Check **HTTP status codes** and **full redirect chains** for any list of URLs — in bulk. For every URL you get the final status, each redirect hop (with its status and `Location`), response time, content-type and server header. It reads response **headers only** (the body is never downloaded), so it's fast, cheap, and easy on the targets.

### What it does

For each URL in your list, the actor returns:

- **Final HTTP status** (e.g. `200`, `301`, `404`, `500`)
- **`ok`** flag (true for `2xx`/`3xx`)
- **Full redirect chain** — every hop: `url`, `status`, `Location`
- **Final URL** after all redirects
- **Response time** in milliseconds
- **content-type**, **server**, **content-length**
- **error** message when a URL fails (DNS, timeout, SSL…)

### Input

| Field | Type | Description |
|---|---|---|
| `urls` | array | List of URLs to check (missing scheme defaults to `https://`) |
| `url` | string | Convenience field for a single URL (merged with `urls`) |
| `method` | enum | `GET` (most accurate) or `HEAD` (lighter; auto-falls back to GET if rejected) |
| `followRedirects` | boolean | Follow 3xx and report the chain (default true) |
| `timeoutSecs` | integer | Per-URL timeout, 1–60 (default 15) |
| `concurrency` | integer | Parallel checks, 1–50 (default 25) |

#### Example input

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

### Output

One record per URL:

```json
{
  "input_url": "http://github.com",
  "final_url": "https://github.com/",
  "final_status": 200,
  "ok": true,
  "redirected": true,
  "redirect_count": 1,
  "redirect_chain": [
    { "url": "http://github.com", "status": 301, "location": "https://github.com/" },
    { "url": "https://github.com/", "status": 200, "location": null }
  ],
  "content_type": "text/html; charset=utf-8",
  "server": "GitHub.com",
  "response_time_ms": 142,
  "error": null
}
```

### Use cases

- **SEO migrations** — verify every old URL 301-redirects to the right new URL (no chains, no 404s).
- **Link audits** — find broken links and unexpected redirects across a sitemap or backlink list.
- **Redirect-chain cleanup** — spot multi-hop chains that waste crawl budget and slow users down.
- **Uptime spot-checks** — batch-confirm a set of endpoints returns `200`.

### Pricing

Pay-per-event, no subscription: **$0.001 per URL checked** ($1 per 1,000 URLs). Up to 1,000 URLs per run — split larger lists across runs.

### Next step: is your site ready for AI crawlers?

Status codes are table stakes. To see whether ChatGPT, Claude and Perplexity can actually read and cite your pages, run **[GEO Site Audit](https://apify.com/dltik/geo-site-audit)** — it scores robots.txt, `llms.txt`, sitemap, Schema.org, meta tags and content extractability for AI readiness.

***

Built by [dltik](https://apify.com/dltik). Pure HTTP, headers-only — fast and cheap.

# Actor input Schema

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

List of URLs to check (e.g. \["https://google.com", "github.com"]). Missing scheme defaults to https://.

## `url` (type: `string`):

Convenience field to check just one URL. Merged with the 'urls' list if both are set.

## `method` (type: `string`):

Request method. GET is most accurate; HEAD is lighter but some servers reject it (the actor auto-falls back to GET when that happens).

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

Follow 3xx redirects and report the full chain. Disable to see only the first response.

## `timeoutSecs` (type: `integer`):

Per-URL request timeout in seconds (1-60).

## `concurrency` (type: `integer`):

How many URLs to check in parallel (1-50). Higher is faster but heavier on the targets.

## Actor input object example

```json
{
  "urls": [
    "https://google.com",
    "http://github.com",
    "https://apify.com"
  ],
  "method": "GET",
  "followRedirects": true,
  "timeoutSecs": 15,
  "concurrency": 25
}
```

# Actor output Schema

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

HTTP status and redirect chain for each URL.

# 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://google.com",
        "http://github.com",
        "https://apify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dltik/http-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://google.com",
        "http://github.com",
        "https://apify.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dltik/http-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://google.com",
    "http://github.com",
    "https://apify.com"
  ]
}' |
apify call dltik/http-status-checker --silent --output-dataset

```

## MCP server setup

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