Broken link detection

Audit links after every deploy

Ship with confidence. Check-links renders the page, collects every anchor, and verifies each destination. Internal and external, in one report.

Works with your agent stack

ClaudeCursorCodexVS CodeGeminin8n

Content and SEO teams need post-deploy link checks without running Screaming Frog locally. One POST returns a structured report of failures.

Post-deploy CI

Run after every release on key routes. Fail the build on unexpected 404s.

External link rot

Catch outbound links to pages that moved or returned 403.

Static HTML parsers miss client-rendered footers and nav. We load the page in a browser, then HTTP-check every resolved href.

Internal + external

Toggle include_internal and include_external to match your audit scope.

Status codes

Each link returns HTTP status so you prioritize 404s vs timeouts.

One credit

Full link report per page. Cache repeat checks at 0 credits.

01

Check page

POST URL to /v1/check-links. Parse JSON report.

View docs →
02

CI gate

Fail deploy when broken link count exceeds threshold.

API docs →
03

Combine with crawl

Crawl site, then check-links on each discovered URL for full coverage.

Site crawl →

Link audit FAQs

Questions about broken link detection.

View docs
001Does it follow JavaScript links?

We collect hrefs from the rendered DOM, including client-rendered navigation.

002How is this different from /links?

/links returns URLs. /check-links verifies each URL and reports HTTP status.

003Rate limits on external checks?

External verification runs in parallel with sensible caps. See docs for plan limits.

Audit links today

Broken link reports from one API call.