Which HTTP responses should a broken-link checker flag automatically?
by•
I’m preparing the launch of PAH Broken Link Checker and would value practical feedback from site owners and developers.
Many scanners treat every non-200 response as broken, even when 401, 403, 429, timeouts, or firewall blocks require manual verification. This tool keeps working links, redirects, broken responses, blocked responses, and scan errors separate.
When reviewing a link-audit report, which information helps you act fastest: HTTP status, source page, link type, redirect target, or CSV export? Are there any response codes you would never classify automatically?
2 views

Replies