TiloBox
Back to directory
broken-link-checker project preview

broken-link-checker

Find broken links, dead images, and iframe targets in HTML pages, directories, and whole sites.

LicenseMIT
GitHub stars1.5k
Last commit6 days ago
Tags5 topics
Dead Link DetectorHtml Asset CheckerBrokenlinkchecker NodeSeo Link AuditorMarketing
Overview

Why consider broken-link-checker?

broken-link-checker is an open-source link verification engine for Node.js written by Steven Vachon. It parses HTML elements (`<a>`, `<img>`, `<script>`, `<link>`), checking HTTP status codes, honoring robots.txt exclusions, and caching verified URLs for high-speed audits.

Guided learning

Learn broken-link-checker by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

broken-link-checker scans websites recursively to detect dead image links and broken hyperlinks.

Quickstart

bash
1npm install -g broken-link-checker
2blc https://company.com -ro

broken-link-checker is licensed under the permissive MIT License.

Related tools

More options with a similar category or technology profile.

broken-link-checker FAQs

broken-link-checker is listed as a Marketing tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

broken-link-checker is listed under the MIT license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

broken-link-checker is listed as an alternative to W3C Link Checker. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.