# Redirect Checker & Website Status Checker – Bulk URLs (`rowfeed/redirect-checker`) Actor

Check thousands of URLs: HTTP status, every redirect hop, final URL, 301 or 302, redirect loops, dead links and response time. For SEO migrations and link audits. $0.10 per 1,000 URLs, invalid addresses free.

- **URL**: https://apify.com/rowfeed/redirect-checker.md
- **Developed by:** [Rowfeed](https://apify.com/rowfeed) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 4 total users, 3 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.10 / 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

## Redirect Checker & Website Status Checker – Bulk URLs

Check thousands of URLs in one run: HTTP status, every redirect hop, the final URL, whether redirects are permanent or temporary, loops, dead links and response time.

Built for SEO site migrations, link audits, cleaning URL lists, and AI agents that need to know whether a link works.

### What you get

One row per URL:

```json
{
  "url": "http://apify.com",
  "status": 301,
  "final_url": "https://apify.com/",
  "final_status": 200,
  "ok": true,
  "redirects": 1,
  "redirect_type": "permanent",
  "redirect_chain": [{"url": "http://apify.com", "status": 301, "to": "https://apify.com/"}],
  "https_upgrade": true,
  "response_ms": 212,
  "problem": null,
  "may_refuse_robots": false,
  "checked_at": "2026-11-06T10:00:00Z"
}
```

- `status` is the first answer and `final_status` the answer at the end of the chain.
- `redirect_type` is `permanent` (301, 308), `temporary` (302, 303, 307) or `mixed`. A temporary redirect on a moved page is a common SEO mistake.
- `problem` says why a URL has no final answer: `no_connection`, `ssl_error`, `timeout`, `redirect_loop`, `too_many_redirects` (more than 10 hops), `bad_redirect`, `internal_address` or, rarely, `failed: ...` with the technical reason.
- `may_refuse_robots` is `true` on answers like 403 or 429. The page may work fine in a browser: some sites refuse automated visitors, and this Actor always says honestly what it is and does not try to get around that.

### Input

| Field | What it does |
| --- | --- |
| `urls` | Addresses to check, up to 50,000 per run. Without a scheme, `https://` is used. Duplicates are checked once. |
| `onlyProblems` | Leaves out addresses that answer 200 directly. You pay only for the rows you get. |

### Pricing

Pay per event, no subscription:

- **$0.10 per 1,000 URLs** ($0.0001 each). A dead link is a result, so it counts as a URL.
- $0.001 per run start.

Text that is not a web address gets a free row explaining why. You can cap a run with the maximum charge setting and it stops cleanly there. Examples: 100 URLs cost $0.011, and 10,000 URLs cost $1.00.

### Good to know

- It reads only the status and headers of each hop, not the page content.
- A few requests at a time per site, so a very long list from one site takes longer (give the run a longer timeout) but does not hammer it.
- Each address is checked as a first-time visitor without cookies. A site that insists on a cookie before it answers can show as a redirect loop.
- It checks from Apify's servers, so a site that answers differently by country or blocks data centers can look different from your browser.
- Addresses inside private networks are refused and reported as `internal_address`.

### More tools from Rowfeed

- [Broken Link Checker](https://apify.com/rowfeed/broken-link-checker) – crawl a site and find every broken link and image on it.
- [SEO Audit Tool & Website Crawler](https://apify.com/rowfeed/seo-site-audit) – titles, canonicals, noindex and a score per page.
- [Sitemap URL Extractor](https://apify.com/rowfeed/sitemap-url-extractor) – get every URL of a site to check here.

# Actor input Schema

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

The addresses to check, up to 50,000 per run. Without http:// or https://, https:// is used.

## `onlyProblems` (type: `boolean`):

Leave out addresses that answer 200 directly. Only delivered rows are charged.

## Actor input object example

```json
{
  "urls": [
    "http://apify.com",
    "https://apify.com/store",
    "https://www.iana.org/domains/example"
  ],
  "onlyProblems": false
}
```

# Actor output Schema

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

No description

# 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": [
        "http://apify.com",
        "https://apify.com/store",
        "https://www.iana.org/domains/example"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("rowfeed/redirect-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": [
        "http://apify.com",
        "https://apify.com/store",
        "https://www.iana.org/domains/example",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("rowfeed/redirect-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": [
    "http://apify.com",
    "https://apify.com/store",
    "https://www.iana.org/domains/example"
  ]
}' |
apify call rowfeed/redirect-checker --silent --output-dataset

```

## MCP server setup

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