Practical Guide

Broken Link Checker — Usage Guide and Technical Principles

Broken Link Checker

Open tool

Overview

Broken link checking is the process of validating URLs to ensure they are accessible and return appropriate HTTP status codes. It helps identify dead links, redirects, and server errors in websites, ensuring better user experience and SEO performance. Regular link checking is essential for maintaining website quality and discovering connectivity issues before they affect users.

Key concepts

HTTP Link Validation

Broken link checking involves sending HTTP requests to URLs and analyzing the response status codes. The tool supports both HEAD and GET methods. HEAD requests are faster as they don't download the full resource, but some servers block HEAD requests, requiring fallback to GET. Status codes in the 2xx range indicate success, 3xx codes indicate redirection, 4xx codes indicate client errors (like 404 Not Found), and 5xx codes indicate server errors.

Concurrent Checking

The tool uses concurrent HTTP requests to check multiple URLs simultaneously, significantly reducing total checking time. Concurrency can be configured (1-12 requests) to balance speed and server load. Each request runs independently with its own timeout, allowing partial results even if some requests fail.

Timeout Management

Timeout settings prevent requests from hanging indefinitely. When a timeout is reached, the request is aborted using AbortController API. Configurable timeout values (3-60 seconds) help identify slow or unresponsive servers. Response duration is measured from request initiation to response completion, providing performance metrics.

CORS and Browser Limitations

Browser-based link checking is subject to CORS (Cross-Origin Resource Sharing) policies. Some servers may block requests from browser origins. For server-side checking or bypassing CORS, consider using server-side tools or browser extensions. The tool uses fetch API with CORS mode to maximize compatibility.

Features

Concurrent Checking

Check multiple URLs simultaneously with configurable concurrency (1-12 requests) to dramatically reduce checking time for large URL lists

Status Code Detection

Automatically detect and display HTTP status codes (2xx success, 3xx redirect, 4xx client error, 5xx server error) with color-coded indicators

Performance Metrics

Measure response times for each URL to identify slow or unresponsive servers, with configurable timeout settings (3-60 seconds)

Error Handling

Comprehensive error handling for timeouts, CORS issues, network errors, and blocked requests with clear error messages and recovery options

Use Cases

Web debugging

Use Broken Link Checker to inspect browser, HTTP, API, storage, or configuration behavior while diagnosing frontend and backend integration issues.

Pre-release checks

Broken Link Checker is useful before release when validating headers, browser data, URLs, CORS settings, API behavior, or client-side assumptions.

Support and handoff

Create reproducible examples with Broken Link Checker for bug reports, support tickets, implementation guides, and team knowledge base articles.

Frequently asked questions

Why do some links show 'HEAD method blocked'?

Some servers disable HEAD requests for security or configuration reasons. If you see this message, the tool has detected that the server blocked the HEAD request. Try switching to GET method for more reliable results, though it may be slightly slower.

What causes timeout errors?

Timeout errors occur when a server takes longer to respond than your configured timeout (default 10 seconds). This can happen due to slow servers, network issues, or unresponsive endpoints. Increase the timeout value if you're checking slow but valid URLs.

Why can't I check some URLs?

Browser-based link checking is limited by CORS (Cross-Origin Resource Sharing) policies. Some servers block requests from browser origins. For checking such URLs, consider using server-side tools or browser extensions that can bypass CORS restrictions.

What's the difference between HEAD and GET methods?

HEAD requests only fetch response headers without downloading the body, making them faster. GET requests download the full resource. Some servers block HEAD requests, so GET is more reliable but slower. Use HEAD for speed when checking many URLs, or GET for accuracy.

How does concurrency affect checking?

Higher concurrency (more parallel requests) makes checking faster but increases server load. Lower concurrency is gentler on servers but slower. Start with 4 concurrent requests and adjust based on your needs and server capacity.

Related documentation

Broken Link Checker

Open the tool to try these features.

Open tool