Broken Link Redirect Map avatar

Broken Link Redirect Map

Pricing

from $4.90 / 1,000 page auditeds

Go to Apify Store
Broken Link Redirect Map

Broken Link Redirect Map

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

Pricing

from $4.90 / 1,000 page auditeds

Rating

0.0

(0)

Developer

junipr

junipr

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

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

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

{
"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:

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

Output Example

{
"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.