# Broken Link Redirect Map (`junipr/broken-link-redirect-map`) Actor

Crawl pages to identify broken links, redirect chains, status codes, and redirect-map issues.

- **URL**: https://apify.com/junipr/broken-link-redirect-map.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.90 / 1,000 page auditeds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Broken Link Redirect Map

### Store Positioning

**Store title:** Broken Link Redirect Map

**Short description:** Crawl pages to identify broken links, redirect chains, status codes, and redirect-map issues.

**SEO title:** Broken Link Redirect Map — technical SEO, web, and domain audit

**SEO description:** Crawl pages to identify broken links, redirect chains, status codes, and redirect-map issues. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

**Categories:** SEO\_TOOLS, AUTOMATION

**Keywords:** broken, link, redirect, map, web/domain audit

### Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: W1 — Web/domain audit
- Primary event: `page-audited` at $0.00490 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. Broken Link Redirect Map: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `page-audited`: base $0.00490, GOLD $0.00392. Broken Link Redirect Map: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `record-extracted`: base $0.00372, GOLD $0.00298. Broken Link Redirect Map: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `finding-emitted`: base $0.00372, GOLD $0.00298. Broken Link Redirect Map: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `audit-report-generated`: base $0.05000, GOLD $0.04000. Broken Link Redirect Map: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit Broken Link Redirect Map controls with capped supplied targets
- Find high-priority Broken Link Redirect Map issues before release
- Validate Broken Link Redirect Map evidence from supplied pages
- Prioritize Broken Link Redirect Map fixes with severity and proof
- Export Broken Link Redirect Map QA rows for client review

### What does Broken Link Redirect Map do?

Broken Link Redirect Map turns page/link snapshots into structured rows that identify broken links, redirects, redirect chains, HTTP status codes, final URLs, and cleanup recommendations.

The actor is safe by default: the default run uses bundled fixture page snapshots and makes no network calls. Enable `fetchPages` or `checkLive` only when you want capped live HTTP requests.

### Use Cases

- Find internal 404 links before publishing a site or landing page.
- Map old URLs to final URLs after a migration.
- Identify stale source links that still point at redirected pages.
- Check external resource links from a small page set.
- Produce a compact redirect-map report for SEO, web QA, or client delivery workflows.

### Input Example

```json
{
  "fetchPages": false,
  "checkLive": false,
  "maxPages": 1,
  "maxLinksPerPage": 20,
  "includeExternal": true,
  "includeReport": true,
  "maxChargeUsd": 10
}
```

`maxChargeUsd` is a hard PPE cap covering actor start, checked links, and report generation. The actor stops gracefully before any event that would exceed the cap.

To run a tiny live check later:

```json
{
  "urls": ["https://example.com/"],
  "fetchPages": true,
  "checkLive": true,
  "maxPages": 1,
  "maxLinksPerPage": 10,
  "requestTimeoutMs": 5000,
  "maxRedirects": 5
}
```

### Output Example

```json
{
  "sourceId": "example-homepage",
  "sourceUrl": "https://example.com/",
  "linkUrl": "/missing-page",
  "normalizedUrl": "https://example.com/missing-page",
  "finalUrl": "https://example.com/missing-page",
  "status": "fail",
  "severity": "high",
  "httpStatus": 404,
  "redirectCount": 0,
  "isBroken": true,
  "isRedirect": false,
  "issueCodes": ["broken-link"],
  "recommendation": "Fix or remove this link; it returns HTTP 404."
}
```

The default dataset contains one row per checked link. The key-value store includes:

- `BROKEN_LINK_REDIRECT_RESULTS.json`
- `BROKEN_LINK_REDIRECT_SUMMARY.json`
- `BROKEN_LINK_REDIRECT_REPORT.md`

### Live Check Behavior

`fetchPages: false` and `checkLive: false` is the default Store-quality path. It analyzes supplied page snapshots or the built-in fixture.

`fetchPages: true` fetches the configured page URLs and extracts anchors.

`checkLive: true` checks each link with a HEAD request, falls back to GET for common unsupported HEAD responses, and follows redirects manually up to `maxRedirects`.

Live requests are capped by:

- `maxPages`
- `maxLinksPerPage`
- `requestTimeoutMs`
- `maxRedirects`
- no browser rendering
- no proxy usage

Start with one page and 5-10 links before expanding.

### Limitations

- This is a lightweight HTTP/link QA actor, not a JavaScript-rendered crawler.
- Default runs do not fetch pages or links live.
- Regex-based HTML extraction is intentionally simple; provide explicit `links` if you need deterministic parsing from complex markup.
- It does not log in, submit forms, bypass robots, or access private pages.
- It does not collect sensitive personal data.

### Troubleshooting

- `status-unknown` means no fixture status was supplied and live checks were disabled or failed.
- `redirect-chain` means the source link should usually be updated to the final URL.
- `broken-link` means the supplied or live HTTP status is 4xx/5xx.
- If report artifacts are missing, check whether the `audit-report-generated` event limit was reached.

### FAQ

#### Does the default run crawl my site?

No. The default run uses fixture snapshots and no network calls.

#### Can I supply my own HTML?

Yes. Add `pages[].html` or explicit `pages[].links` and optional `linkStatusMap`.

#### Can it follow redirects?

Yes, only when `checkLive` is true or when fixture redirect chains are supplied.

#### Does it use a browser?

No. It uses plain HTTP requests for optional live checks.

### Changelog

- `1.0.0`: Initial local-first build with fixture link snapshots, optional capped live HTTP checks, redirect mapping, PPE billing, examples, and fixture tests.

# Actor input Schema

## `pages` (type: `array`):

Optional page snapshots with HTML or explicit links. Defaults use tiny fixture pages and make no network calls.

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

Optional page URLs to fetch and extract links from. Used only when fetchPages is true.

## `fetchPages` (type: `boolean`):

Fetch page HTML for each URL. Default false avoids network usage.

## `checkLive` (type: `boolean`):

Run live HTTP status checks for each link. Default false uses supplied/fixture status snapshots.

## `maxPages` (type: `integer`):

Maximum pages to analyze in one run.

## `maxLinksPerPage` (type: `integer`):

Maximum links emitted per page after extraction.

## `requestTimeoutMs` (type: `integer`):

Timeout per live HTTP request. Used only when fetchPages or checkLive is true.

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

Maximum redirects followed during live link checks.

## `includeExternal` (type: `boolean`):

Include external http(s) links in output.

## `maxItems` (type: `integer`):

Alias for Max Targets/Maximum Records used by the Junipr actor baseline. When both are provided, actor-specific limits still apply.

## `includeReport` (type: `boolean`):

Store result JSON, summary JSON, and a Markdown redirect-map report in the key-value store.

## `maxChargeUsd` (type: `number`):

Hard local spending cap for actor-start, per-item, and report events. The actor stops before work or withholds uncharged output when the next event would exceed this amount.

## `dryRun` (type: `boolean`):

Validate input and write a dry-run summary without PPE charges or dataset output.

## `debug` (type: `boolean`):

Enable verbose logs.

## Actor input object example

```json
{
  "pages": [],
  "urls": [],
  "fetchPages": false,
  "checkLive": false,
  "maxPages": 1,
  "maxLinksPerPage": 20,
  "requestTimeoutMs": 8000,
  "maxRedirects": 5,
  "includeExternal": true,
  "maxItems": 1,
  "includeReport": true,
  "maxChargeUsd": 10,
  "dryRun": false,
  "debug": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

Structured broken-link and redirect rows.

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

Run summary artifact stored in the default key-value store.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/broken-link-redirect-map").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/broken-link-redirect-map").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/broken-link-redirect-map --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=junipr/broken-link-redirect-map",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/bng5rkubl7uF7kqkc/builds/C9WW3WbxmHKbe9bTU/openapi.json