3 4 5 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

What is Link Checker

Illustration of a link checker toolDefinition:

A link checker is a tool that crawls pages, files or URL lists to verify whether their links respond and lead to the expected destination. It can find broken links, redirects, server errors and other issues that may hinder navigation or website crawling.

The scope of analysis depends on the tool. Some check a single page, others crawl an entire website, and others query external indexes to study links that point from different domains.

What a link checker analyses

The check starts by requesting every URL found and recording its technical response. The report usually includes the source page, link destination, HTTP status, link type and, in some cases, crawl depth or anchor text.

  • 2xx responses: normally indicate that the requested resource is available.
  • 3xx redirects: show that the URL leads to another address and help reveal chains or loops.
  • 4xx/5xx errors: identify missing resources, restricted access or server failures.
  • Fragment links: make it possible to check internal anchors that point to a specific section of a page.

The report may also show connection failures, such as timeouts, DNS problems or TLS errors. It is advisable to repeat the test before correcting them because some failures are temporary or depend on server configuration.

What it is used for

A link checker supports the periodic maintenance of websites with many pages and reduces the time needed to locate outdated references. Common uses include:

  • Content control: checking internal and external links after publishing or updating a page.
  • Internal linking: finding deleted destinations or unnecessary redirects within the website architecture.
  • Website migrations: confirming that old URLs lead to the intended destinations and that the new navigation works.
  • Editorial audits: detecting linked sources, downloads and images that are no longer available.

A broken link does not by itself trigger an automatic search penalty. However, an accumulation of errors may harm user experience, waste crawl resources and weaken the internal linking that distributes context and authority across pages.

How to interpret the results

The status code is only the starting point. A URL may return 200 while displaying an error page, the wrong content or an incomplete response generated with JavaScript. Similarly, a redirect may be valid or may lead to a destination that is too generic.

Results can also vary with access conditions, including authentication, robots rules, geographic location, cookies or user agent. Before changing a link, open the destination, check its purpose and, when necessary, confirm the error with more than one request.

The appropriate correction depends on the case: replace the URL, restore the resource, create a redirect, repair a relative reference or remove the link if it no longer provides value. Automating detection does not remove this editorial and technical decision.

Types of link checker

There are several forms of link checking, each suited to a different scope:

  • Desktop crawlers: explore entire websites and export technical reports, such as Screaming Frog.
  • Audit platforms: schedule recurring crawls and group issues by project.
  • CMS plugins: check links from the content management system, although they can consume server resources.
  • Single-page checkers: validate one page or a short URL list without crawling the entire website.
  • External indexes: study backlinks discovered outside the website and help verify whether they remain active.

A site crawler and a backlink index are related sources, but they are not equivalent. The former starts with the pages it can crawl; the latter depends on its own external link index and may not reflect every existing link.

Limits of automated checking

A successful response does not prove that a link is useful or relevant. The tool cannot always assess whether the destination supports a claim, whether the anchor text is clear or whether another page would be a better reference.

  • Dynamic content: some links generated with JavaScript require rendering before they can be discovered.
  • Restricted access: blocks, sessions or rate limits can produce false errors.
  • Incomplete scope: orphan pages, forms and unlinked resources may remain outside the crawl.

An effective review therefore combines the link checker’s technical report with manual and editorial validation. This approach helps prioritize genuine errors and apply improvements within a coherent SEO strategy.