Site owners
A small business owner wants to find old service-page URLs after changing navigation.
The report creates a focused repair list instead of requiring every page to be opened by hand.
Definition guide
A broken link checker is a tool that tests links on a website and reports destinations that cannot be reached as expected. It turns a vague concern about dead pages into a reviewable list of URLs, status signals, and next actions.
Related reading
Start with the angle that matches your question, then return here for the basic concept and its limits.
Practical uses
The same basic check serves different people: each starts with a different risk and ends with a more usable site.
A small business owner wants to find old service-page URLs after changing navigation.
The report creates a focused repair list instead of requiring every page to be opened by hand.
An editor reviews an article library containing links to sources, tools, and internal pages.
They can separate a genuinely failed destination from a link that only needs updated wording or context.
An SEO specialist checks whether crawlers and visitors encounter unnecessary error paths.
They can prioritize internal links, redirect chains, and important pages that no longer resolve cleanly.
A developer validates links after a migration, redesign, or CMS content import.
A repeatable crawl exposes references that manual spot checks are likely to miss.
The basic process
A useful check is less mysterious than it sounds: discover links, request destinations, and interpret the result in context.
The checker starts from a page or site address, follows accessible links, and builds a list of destinations to test.
It sends web requests and records signals such as response status, redirects, timeouts, access restrictions, and unreachable hosts.
The resulting list helps you confirm the problem, identify the source page, and choose a repair such as updating, redirecting, or removing the link.
Concept at a glance
A checker is not the same thing as a browser or a human review. Each method answers a different question.
| Automated link check | Manual review | |
|---|---|---|
| Main purpose | Find many link destinations that need attention | Judge whether a page is useful, accurate, and well presented |
| Coverage | Can inspect links across many pages consistently | Usually limited to selected pages or examples |
| Primary signal | Response status, redirect behavior, timeout, or access failure | Human interpretation of content, intent, and relevance |
| Repeatability | Can be run again after changes using the same process | Results may vary with the reviewer and selected pages |
| Best at finding | Misspelled URLs, stale paths, failed hosts, and broken internal references | Outdated claims, poor anchor text, and misleading destinations |
| What it needs next | Confirmation and a suitable repair | A technical check when the issue may be hidden across the site |
Visible outcome
The change is not cosmetic: a crawl turns scattered link complaints into a traceable repair workflow.
The report guides the next human decision; it does not replace one.
Before: unknown failuresAfter: reviewable findingsHonest boundaries
A checker is a diagnostic aid, not a guarantee that every destination is correct, useful, or permanently available.
A URL may return successfully while pointing to a page that is outdated, irrelevant, or misleading.
What to do instead
Read important destinations and compare them with the promise made by the link text.
Robots rules, authentication, firewalls, rate limits, and temporary blocks can prevent a complete request.
What to do instead
Review access settings, test with permission, and treat blocked results as needing verification rather than automatic failure.
A working link can break after the check because content, domains, or redirects change.
What to do instead
Schedule sensible rechecks after migrations and important content updates.
The report identifies candidates, but changing URLs or removing references can affect navigation and editorial intent.
What to do instead
Fix the source page deliberately, then run a second check to confirm the result.
Status signals
These familiar response codes illustrate the kinds of technical evidence a checker may surface; the code still needs context.
Next practical step
Whether you manage one site or a large content library, a structured check gives you a starting point for verification. Review the evidence, fix the source page, and check again after important changes.
Common question
Here is the short answer first, followed by the distinctions that make the definition useful in practice.
It is a tool that tests links on a website and reports destinations that fail, redirect unexpectedly, time out, or cannot be accessed. The result helps a site owner locate the source link and decide what to do next.
It usually looks at whether a destination responds and what kind of response it returns. Depending on the tool and access available, it may also identify redirects, timeouts, blocked requests, and the page where each link was found.
The terms are often used for the same general purpose: finding links that no longer work as expected. In practice, some tools use dead link for a failed destination and broken link for the wider checking process, so the exact scope depends on the tool.
No. It can provide useful technical evidence about reachability and response behavior, but a successful response does not prove that the page is relevant, accurate, readable, or current. Important results still need human review.
There is no single schedule for every site. Recheck after migrations, navigation changes, large content imports, or important URL updates, and use a recurring review when the site publishes or changes links frequently.