# Website Up & Link Checker: Status, Redirects, Response Time (`tudorlane/site-up-link-check`) Actor

Is it up right now? Bulk check URLs for status code, response time, full redirect chain and final URL, broken links, SSL errors and timeouts. Unshortens short links. Built for AI agents.

- **URL**: https://apify.com/tudorlane/site-up-link-check.md
- **Developed by:** [Tudor Lane](https://apify.com/tudorlane) (community)
- **Categories:** Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 url checks

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

## Website Up & Link Checker: Status, Redirects, Response Time

### Use when…

- You need HTTP status, redirects and response time for one or many URLs.
- An uptime or QA agent must confirm pages are up and links are not broken.
- You want a bulk link check with clear ok/fail rows for automation.

### Try this input

Copy-paste this JSON as the Actor input (it matches a successful run / the default schema):

```json
{
  "requests": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://github.com/apify"
    },
    {
      "url": "http://apify.com"
    },
    {
      "url": "https://httpbin.org/status/404"
    }
  ]
}
```

### Sample output (real run 2026-10-26)

One dataset item, shortened:

```json
{
  "url": "https://httpbin.org/status/404",
  "up": false,
  "status": 404,
  "result": "client_error",
  "response_ms": 13,
  "total_ms": 13,
  "final_url": "https://httpbin.org/status/404",
  "redirected": false,
  "redirect_count": 0,
  "redirect_chain": [
    {
      "url": "https://httpbin.org/status/404",
      "status": 404,
      "ms": 13
    }
  ],
  "content_type": "text/html",
  "server": "gunicorn/19.9.0",
  "…": "+3 more keys"
}
```

An instant "is this link alive?" check before an agent cites, buys from or sends a link.

- `up` true/false, HTTP status and a plain `result`: ok, client_error, server_error, blocked_or_auth, timeout, ssl_error, connection_error, redirect_loop
- Response time of the final hop and total time
- Every redirect hop with status and timing; `final_url` unshortens bit.ly-style links
- Thousands of URLs per run, 10 in parallel
- Safe: public addresses only, each redirect re-checked
- For scheduled down/up alerts use **domain-watch**; for content changes use **page-change-watch**

### Quick start

Leave the default input (it is prefilled) and click **Start**:

```json
{"requests": [{"url": "https://apify.com"}, {"url": "https://github.com/apify"}, {"url": "http://apify.com"}, {"url": "https://httpbin.org/status/404"}]}
```

Send many items in one run (cheaper and faster than one run each). Settings outside `requests` apply to every item.

### Sample output (real run, 26 Oct 2026, default input)

| url | up | status | result | response_ms | redirect_count | final_url |
|---|---|---|---|---|---|---|
| https://httpbin.org/status/404 | false | 404 | client_error | 18 | 0 | https://httpbin.org/status/404 |
| http://apify.com | true | 200 | ok | 84 | 1 | https://apify.com/ |
| https://apify.com | true | 200 | ok | 124 | 0 | https://apify.com |
| https://github.com/apify | true | 200 | ok | 467 | 0 | https://github.com/apify |

Each row also has `redirect_chain` (every hop with status and ms), `total_ms`, `content_type`, `server` and `checked_at`.

### Use cases

- Check links are alive before an agent cites or sends them.
- Find broken links in a list of pages, product URLs or bookmarks.
- Unshorten bit.ly-style links to see the real destination.
- Quick status and speed check across all your sites.

### Pricing

Pay per event: **$0.001 per url check** (one url checked). Rows with errors are not charged. No subscription.

### FAQ

**Does it crawl a whole site?** No. It checks the URLs you send. Use a sitemap or crawler tool to get the list first.

**Do I need an API key?** No.

**How many URLs?** Thousands per run, 10 checked in parallel.

### Limits & failure modes

- Response times are measured from Apify's cloud servers, not from your location.
- Some sites block cloud servers or bots and return 403 (`blocked_or_auth`) even though they work in a browser.
- One check per run, so it is not continuous uptime monitoring (use domain-watch on a schedule for that).
- Only public addresses are checked; private and local network addresses are refused.
- Sites that block datacentre IPs can look “down” from Apify even when up for users.
- Soft-404 pages that return HTTP 200 are not always detected as broken.

### Output

One dataset row per request. Errors come back as a row with `error` set, so a batch never fails because of one bad item.

### Use from AI agents (MCP)

Add it to any MCP client via `https://mcp.apify.com?actors=tudorlane/site-up-link-check`, or call the Apify API / run-sync endpoint.

### Sources and licences

Live HTTP requests only. No third-party data.

# Actor input Schema

## `requests` (type: `array`):

Each item: {"url": "https://example.com"} or just a URL string. Optional: head_only, timeout_secs (max 30), max_redirects. Max 10000. Errors are not charged.

## Actor input object example

```json
{
  "requests": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://github.com/apify"
    },
    {
      "url": "http://apify.com"
    },
    {
      "url": "https://httpbin.org/status/404"
    }
  ]
}
```

# Actor output Schema

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

One item per request.

## `dataset` (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 = {
    "requests": [
        {
            "url": "https://apify.com"
        },
        {
            "url": "https://github.com/apify"
        },
        {
            "url": "http://apify.com"
        },
        {
            "url": "https://httpbin.org/status/404"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tudorlane/site-up-link-check").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 = { "requests": [
        { "url": "https://apify.com" },
        { "url": "https://github.com/apify" },
        { "url": "http://apify.com" },
        { "url": "https://httpbin.org/status/404" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tudorlane/site-up-link-check").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 '{
  "requests": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://github.com/apify"
    },
    {
      "url": "http://apify.com"
    },
    {
      "url": "https://httpbin.org/status/404"
    }
  ]
}' |
apify call tudorlane/site-up-link-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tudorlane/site-up-link-check"
        }
    }
}
```

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/OFE3onLyEjCGww0LP/builds/RzGTGwQuYUZHCO4zS/openapi.json