Unique targets only
Request each destination once even when a template repeats it.
BROKEN LINK AUDIT
A broken link checker fetches the selected page, extracts HTTP and HTTPS links, deduplicates destinations and performs lightweight status checks. 404, 410, 5xx, invalid redirects and persistent connection failures need attention.
A 403 or 429 is not automatically treated as a 404. It means the check was restricted and may involve permissions, rate limiting or firewall policy, so it needs contextual review.
Request each destination once even when a template repeats it.
Separate healthy, broken, restricted and unreachable links.
Limit count, concurrency, timeout and redirects while blocking private targets.
Broken internal links interrupt discovery, waste crawl effort and drive users away. Dead external citations weaken trust. Maintaining useful paths matters more than simply adding more links.
Keep navigation and contextual links leading to valid pages.
Find 404, server errors and bad redirects before users do.
Discover repeated broken destinations in navigation, footers or content templates.
The tool fetches the source page once, then checks up to 30 deduplicated web links. It prefers HEAD and uses a minimal GET only when HEAD is unsupported.
Validate the public URL and read final HTML.
Ignore fragments, email, phone and non-web schemes.
Use 8-way concurrency, 5-second timeouts and up to 5 redirects.
Separate confirmed failures, restricted access and network errors.
Preserve the meaning of a destination. Do not redirect every missing URL to the homepage merely to remove 404 responses.
When the page exists, point directly to its final canonical HTTPS URL.
Redirect only to a close replacement and remove unnecessary redirect chains.
If no replacement exists, remove internal links and let the status describe deletion accurately.
Review 403, 429 and timeouts instead of deleting them as if they were 404s.
Not necessarily. It means this request was denied because of permissions, region, bot policy or a firewall. The tool marks it as restricted for manual review.
The public-tool safety limit controls target load, response time and abuse risk. Repeated destinations are checked once.
Sites, CDNs, rate limits and networks change. A short cache reduces repeated pressure, and later checks may return a new status.
They are not written to the business database or published as history pages. Only a short cache reduces duplicate requests.
Continue auditing link structure, indexability and HTTP responses.