Linkinator
Scan local site output or a public URL for failing links from a command-line workflow.
Community support
Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.
Claim this tool if you maintain it.
- Best for
- Link checks
- Setup required
- Node.js for npm installation, or an upstream release binary for a supported platform.
- Costs to check
- Budget for CI time and outbound requests on large documentation sites.
- License in catalog
- MIT
GitHub repository
- GitHub stars
- 1,286
- Forks
- 110
- Last push
- 2026-11-06
- Primary language
- TypeScript
GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.
How to install Linkinator
- Install linkinator with npm in a test project.
- Build a small static site fixture and confirm npx linkinator --help runs from the project.
First tutorial for Linkinator
- Run npx linkinator ./dist --recurse against your fixture output directory.
- Inspect the report for the expected broken URL and verify its referring page before fixing the source file.
Where Linkinator fits
Use it when a static-site build needs a link check before deployment.
- When to choose another tool
- Use a browser-based test when important links only become visible after interaction.
- First evaluation
- Scan a tiny output directory containing a known working link and a known broken destination.
- How to interpret the result
- Confirm whether a failed link is missing, redirected or blocked before editing it. Network failures can be transient.
Reviews and discussion
Reader reviews
Be the first to share your experience with this tool.
Discussion
Ask a question or share a setup tip.
Flag an outdated detail
Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.
Write a review or join the discussion