Site QA · broken links

Public pages checked for broken and risky URLs

Check public pages for broken links and generate source-linked URL health report rows.

Not a start-URL HTML crawler that only lists 404s (use Broken Link Checker). Not a known-URL HTTP status list (use Bulk URL Status Checker). Not an AI crawler robots/llms.txt pack. You supply the URLs.

from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per URL health issue detected; $5.00 per URL health report generated; $7.00 per Site export generated. No Actor Start.

Open Site QA Broken Link Report on Apify

Site QA Broken Link Report, not a neighboring Actor

Use this page for this Actor’s job. Use Broken Link Checker for Crawl start URLs for 404s; Use Bulk URL Status Checker for Known URL list HTTP status; Use Site QA Indexability AI Crawler Report for robots.txt and llms.txt signals.

This ActorBroken Link CheckerBulk URL Status CheckerSite QA Indexability AI Crawler Report
IntentURL-health issues, report, and export on supplied pagesCrawl start URLs for 404sKnown URL list HTTP statusrobots.txt and llms.txt signals
Primary inputurlsstart URLsURL listurls
What it readsUser-supplied public pages and their linksLinked HTTP statusesHTTP status codesrobots.txt / llms.txt
Primary outputIssue, report, and export eventsBroken-link rowsStatus rowsPolicy-check and indexability events
Not this jobNot a start-URL HTML crawler that only lists 404s (use Broken Link Checker). Not a known-URL HTTP status list (use Bulk URL Status Checker). Not an AI crawler robots/llms.txt pack. You supply the URLs.Not a billed URL-health report pack.Not an HTML link crawl or report pack.Not broken-link URL health issues.

Store ID: taroyamada/site-qa-broken-link-report-scraper. Respect source terms, robots.txt, and rate limits.

Use cases

How is Site QA Broken Link Report different from Broken Link Checker and Bulk URL Status Checker?

Site QA Broken Link Report (taroyamada/site-qa-broken-link-report-scraper): Check public pages for broken links and generate source-linked URL health report rows. Not a start-URL HTML crawler that only lists 404s (use Broken Link Checker). Not a known-URL HTTP status list (use Bulk URL Status Checker). Not an AI crawler robots/llms.txt pack. You supply the URLs. Broken Link Checker is for Crawl start URLs for 404s (input start URLs; Linked HTTP statuses; Broken-link rows). Not a billed URL-health report pack. Bulk URL Status Checker is for Known URL list HTTP status (input URL list; HTTP status codes; Status rows). Not an HTML link crawl or report pack. Site QA Indexability AI Crawler Report is for robots.txt and llms.txt signals (input urls; robots.txt / llms.txt; Policy-check and indexability events). Not broken-link URL health issues.

What input is required?

Live required fields: urls. Published exampleRunInput is shown below.

Field Type Default Notes
urls any[] ["https://example.com/?siteQaCanary=links-v2"] Public page URLs. Public URLs that you are allowed to audit. Required.
maxPages integer 10 Max pages. Maximum number of input pages to check. minimum=1 maximum=100
maxLinksPerPage integer 25 Max links per page. Maximum links to check per page for URL health workflows. minimum=1 maximum=250
emitPageRows boolean false Emit raw page rows. Emit optional raw page snapshot rows in addition to value-event issue/report rows.
generateReport boolean true Generate report row. Generate a site-level report row.
emitExport boolean false Generate export row. Generate an export row for handoff workflows.
emitUnchanged boolean false Emit unchanged rows. When false, repeated unchanged runs emit zero rows and zero charges.
dryRun boolean false Dry run. Emit local sample rows without charging.

Published Store example run input (omitted fields take schema defaults):

{
  "urls": [
    "https://example.com/?siteQaCanary=links-v2"
  ],
  "maxPages": 1,
  "maxLinksPerPage": 1,
  "dryRun": false
}

Run Site QA Broken Link Report on Apify

How do dataset, webhook, and dry-run delivery work?

Dataset output is the billable surface when rows are written. See live PPE for which events bill. dryRun true validates or samples without the usual dataset/webhook side effects described on the Store schema. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

What does a result contain?

Published README Output Example / Sample Output JSON. Illustration: { "rowType": "url_health_report", "billingEventName": "url-health-report-generated", "sourceUrl": "https://example.com/?siteQaCanary=links-v2", "checkedUrlCount": 12, "issueCount": 3, "reportStatus": "action_needed" } Treat README samples as illustrations, not a live coverage guarantee. There is no published output JSON schema on the Store page.

How is Site QA Broken Link Report priced?

Billing is pay per event. The live Store card is from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per URL health issue detected; $5.00 per URL health report generated; $7.00 per Site export generated. No Actor Start. Current PPE:

Event Price Emitted when
site-page-extracted (Site page extracted) $0.01 Charged for each optional raw public page snapshot row.
url-health-issue-detected (URL health issue detected) $0.08 Charged for each broken or risky URL health issue row.
url-health-report-generated (URL health report generated) $5.00 Charged for each URL health report row.
site-export-generated (Site export generated) $7.00 Charged for each generated URL QA export row.

from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per URL health issue detected; $5.00 per URL health report generated; $7.00 per Site export generated. No Actor Start.

See Site QA Broken Link Report pricing on Apify

Limits to keep in mind

Open Site QA Broken Link Report on Apify

Related pages