Bulk Broken-Link & Redirect Audit — Fix List & Health Score

Check a list of URLs, or crawl a seed site's links, and get an actionable fix list: 404s, 410s, server errors, redirect chains longer than one hop, blocking (401/403/429) and timeouts. Every record says what to do about it, and the run ends with a health score and a prioritised attention list. No browser required, so it is fast and cheap. Built by PAOE.

Each item is processed individually and charged as its own event, so you pay only for what the run actually delivers. Results are written to the run's dataset as one JSON object per item, ready to download as JSON, CSV or Excel, or to pull through the Apify API.

What it checks

For each URL: the HTTP status, whether it is broken (404, 410, 5xx), whether it redirects and how long the chain is, whether it is blocked (401, 403, 429) and whether it times out. Each record carries the final URL after redirects and a fix action telling you what to do about that specific result.

Pricing

Event	What it covers	Price
url-checked	URL checked (primary)	$0.02 per event

Volume tiers reduce the price automatically on higher Apify plans: Bronze 15% off, Silver 25% off and Gold or above 40% off the listed free-tier price. The charge is per item processed, not per run.

Input

Field	Type	Required	Default	Description
urls	array	yes	["https://example.com"]	One or more URLs. Each URL checked is one charged event.
crawlLinks	boolean	no	True	When on, links discovered on the first few seed pages are checked too, so one seed URL produces a whole-site audit.
maxUrls	integer	no	200	Hard cap on the total number of URLs checked in a run.

Example input:

{
  "urls": [
    "https://example.com"
  ],
  "crawlLinks": true,
  "maxUrls": 200
}

Output

One JSON object per item in the run's dataset. Every result carries the input it came from plus the fields this Actor measures, so the output can be joined back to your own data without guessing which row is which. The final dataset entry is a summary object with the run's totals.

Typical use cases

• Find broken links across a site before visitors do.
• Audit redirect chains after a migration or a domain move.
• Produce a fix list for a content or SEO team, sorted by severity.

Limitations

No: a broken link is a successful result, because it is exactly what you asked to find. The run fails only if the Actor itself cannot execute. By default the Actor expands each seed URL with the links found on it, and maxUrls caps the total, so a large site cannot produce an unbounded bill. Set crawlLinks to false to check only the URLs you pass.

Does a 404 count as a failed run?

Every limitation above is reported per item in a findings entry with a level of fail, warn, info or ok, a machine-readable code and a concrete action. If something cannot be checked it is reported as such rather than assumed to be fine.

Can it run on a schedule?

Yes. Save a task from this Actor with your inputs, then set a schedule on the task. Scheduled runs recur with the same inputs, which is the intended way to use it for ongoing monitoring.

How do I keep the cost predictable?

maxUrls is a hard cap on the total number of URLs checked, and each checked URL is one charged event. Set it to the most you are willing to pay divided by the url-checked price.

Notes

If a site returns something unexpected, open an issue on the Actor's page with the URL and the input used, and it will be looked at.

Related Actors

• AI Agent Readiness Audit

Keywords

broken link checker, 404 checker, redirect audit, link checker, SEO audit, site crawl, bulk URL checker, redirect chain.