# URL Status and Expected Redirect Checker (`menobi/profitbot-linkcheck`) Actor

Check supplied public URLs and compare redirect destinations with expected URLs. Includes a readable report and explicit inconclusive statuses.

- **URL**: https://apify.com/menobi/profitbot-linkcheck.md
- **Developed by:** [Mart Z](https://apify.com/menobi) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 checked urls

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

## URL Status and Expected Redirect Checker

Check a list of public URLs and find out whether they respond and reach the destination you intended. Useful for testing a supplied migration map, checking redirects after a site change, or verifying a batch of links.

### What you provide

A JSON list of URLs. Add an expected destination when checking a migration or redirect rule:

```json
{
  "checks": [
    {"sourceUrl": "https://old.example.com/product", "expectedUrl": "https://new.example.com/product"},
    {"sourceUrl": "https://new.example.com/contact"}
  ],
  "requirePermanent": true,
  "ignoreQuery": false
}
```

These example domains illustrate the format; they are not claims of live working customer sites. Use URLs you are authorized to request. Do not submit login credentials, secret query strings, or private-network addresses.

### What you receive

One structured result per completed unique check, plus a readable HTML report. Results include the observed HTTP status, each redirect hop, final URL, expected URL, a verdict, and a suggested next action.

A final 200 response does not automatically pass: when an expected destination was supplied, it must also match. An access restriction or rate limit is reported as inconclusive rather than mislabeled a missing page.

Exact duplicate input rows are skipped. Invalid or prohibited URLs appear in the complete report but are not charged as checked results. Network/DNS/time-out outcomes are reportable checked results, not guarantees that a page is missing.

### Limits

Only supplied URLs are checked; the tool does not crawl a website, discover a sitemap, render JavaScript, inspect page content, or bypass access controls. It does not predict search rankings or traffic. A URL fragment is not part of an HTTP request and is not verified. Query strings are compared unless you explicitly turn that comparison off.

At most 1,000 input rows are accepted per run. Run limits and customer spending limits can stop processing early; the report identifies unprocessed rows. Use smaller batches for slow targets. Only public HTTP(S) destinations and standard ports are supported. No proxy or login is used.

### Pricing

The price is $0.003 per completed unique URL check ($3 per 1,000), plus $0.01 each time the Actor starts. There is no dataset-insertion fee and no separately configured customer platform-usage surcharge.

One run completing 10 chargeable results costs $0.04; 100 costs $0.31; 1,000 costs $3.01. Rejected unsafe or malformed rows have no result charge, but a started run still has its start charge. Completed negative HTTP, DNS, TLS, and timeout findings are charged because they are delivered check results.

Customer maximum-charge limits can stop a batch before every row is processed. Set a limit of at least $0.013 to cover one start and one result. The final report identifies unprocessed rows.

Each resurrection incurs another $0.01 start charge. In testing, resurrecting an already completed run added this charge even beyond the original maximum-charge setting. Do not resurrect completed runs; start a new run with a new spending limit to perform fresh checks.

### Support boundary

For a suspected defect, supply the run ID and a nonsensitive example URL. This utility reports observations; it does not modify your website or sell custom migration consulting.

### Verified platform examples

A private Apify run checked two purpose-built public testing-service URLs:

| Supplied URL | Observed HTTP status | Report verdict |
| --- | --- | --- |
| https://httpbingo.org/status/200 | 200 | PASS |
| https://httpbingo.org/status/404 | 404 | NOT\_FOUND |

The run completed both checks and produced two dataset rows, an HTML report, and a complete JSON report. With live private pricing, Apify recorded two `$0.003` URL events and one `$0.01` start event, totaling `$0.016`.

A `$0.013` maximum-charge test delivered one result, left one row unprocessed, and recorded exactly one URL event plus one start event. An interrupted run was aborted after two stored rows, resurrected, and finished with six unique rows and no duplicate URL charges. Apify recorded six URL events and two start events, totaling its `$0.038` limit.

These are owner-run public-test integration and billing-control checks, not customer work. They do not establish demand, revenue, profitability, or payout.

These observations are a historical sample. A later request can produce different results when a test service or network is unavailable.

# Actor input Schema

## `checks` (type: `array`):

Customer-supplied URLs you are authorized to check. Each row requires sourceUrl; expectedUrl is optional. No login tokens or private URLs. Exact duplicate rows are skipped.

## `requirePermanent` (type: `boolean`):

Flag temporary redirects when an expected destination is provided.

## `ignoreQuery` (type: `boolean`):

Ignore query strings when comparing destinations.

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

Stop after this many redirect hops per URL.

## `timeoutSeconds` (type: `number`):

Maximum socket wait per request, in seconds.

## `perUrlSeconds` (type: `number`):

Processing budget per URL, in seconds; operating-system DNS lookup can exceed it.

## `maxRunSeconds` (type: `number`):

Processing budget for the batch, in seconds; the hosted run timeout also applies.

## Actor input object example

```json
{
  "checks": [
    {
      "sourceUrl": "https://example.com/",
      "expectedUrl": "https://example.com/"
    }
  ],
  "requirePermanent": true,
  "ignoreQuery": false,
  "maxRedirects": 8,
  "timeoutSeconds": 8,
  "perUrlSeconds": 30,
  "maxRunSeconds": 300
}
```

# Actor output Schema

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

No description

## `report` (type: `string`):

No description

## `summary` (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 = {
    "checks": [
        {
            "sourceUrl": "https://example.com/",
            "expectedUrl": "https://example.com/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("menobi/profitbot-linkcheck").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 = { "checks": [{
            "sourceUrl": "https://example.com/",
            "expectedUrl": "https://example.com/",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("menobi/profitbot-linkcheck").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 '{
  "checks": [
    {
      "sourceUrl": "https://example.com/",
      "expectedUrl": "https://example.com/"
    }
  ]
}' |
apify call menobi/profitbot-linkcheck --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,menobi/profitbot-linkcheck"
        }
    }
}
```

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/30u3Z7gGK8SCjJ8oc/builds/Vyt3rBIWkeAy4DluX/openapi.json