• We've moved. Our community is now at ownd.sh — latest discussions and updates live there.

[TOOL] FIND BROKEN LINKS ON WEBSITES & GITHUB PROJECTS AUTOMATICALLY [2026]

Kinder

Divine
Divine
Kinder Rep
0
0
0
Rep
1714
Kinder Vouches
41
0
0
Vouches
41
Posts
6,022
Likes
8,716
4 YEARS
4 YEARS OF SERVICE
Hidden Content

Ever visited a website and clicked a link only to get a 404 error?

Broken links are a common problem on websites, blogs, documentation pages, and GitHub projects.

Instead of checking every link manually, there's a free, open-source tool called Lychee that automatically checks URLs and identifies broken links.

It's fast, lightweight, and written in Rust.

WHAT CAN IT DO?
- Find broken links on websites

- Detect 404 errors

- Check links inside HTML files

- Scan Markdown documentation

- Check README files in GitHub projects

- Identify links that time out

- Detect unexpected HTTP errors

- Export results as JSON or Markdown

- Check multiple URLs at once

- Suggest archived replacements for certain broken links

- Automate link checking using GitHub Actions

No subscription or API key required for ordinary link checking.

LINKSOfficial GitHub:

https://github.com/lycheeverse/lychee

Latest Releases:

https://github.com/lycheeverse/lychee/releases/latest

Official Website:

https://lychee.cli.rs/

GitHub Actions Integration:

https://github.com/lycheeverse/lychee-action

STEP 1 — INSTALL LYCHEEOn Windows, you can install Lychee using WinGet.

Open PowerShell.

Run:

 

Code:

Code:
winget install --id lycheeverse.lychee

Once installation finishes, reopen PowerShell.

Check the installed version:

 

Code:

Code:
lychee --version

Alternatively, download a prebuilt executable from the official GitHub releases page.

STEP 2 — CHECK A WEBSITERun:

 

Code:

Code:
lychee https://example.com

Replace

Code:

Code:
example.com

with the website or page you want to check.Lychee will inspect the supplied page and check the links it discovers.

It can identify URLs that return errors or cannot be reached.

Note: Checking a website URL does not automatically mean crawling every page on the entire domain.

For a complete site audit, provide a sitemap, exported HTML files, or a collection of URLs.

STEP 3 — CHECK MULTIPLE PAGESYou can check several URLs in one command.

For example:

 

Code:

Code:
lychee https://example.com/about https://example.com/contact https://example.com/blog

Lychee will process the links found in those pages.

This is useful when auditing important sections of a website.

STEP 4 — CHECK AN ENTIRE PROJECT FOLDERThis is one of the most useful features.

Imagine you have a website project containing:

 

Code:

Code:
WEBSITE/ ├── index.html ├── about.html ├── contact.html ├── README.md └── docs/ ├── setup.md └── guide.md

Open PowerShell inside the project directory.

Run:

 

Code:

Code:
lychee .

Lychee will recursively inspect supported files in that directory.

It checks links found in HTML, Markdown, and other supported text formats.

Useful for finding dead links before publishing a website or releasing documentation.

STEP 5 — EXPORT A REPORTWant to save the results?

Run:

 

Code:

Code:
lychee . --format markdown --output broken-links.md

This generates a Markdown report.

You can inspect the results or include them in a development task.

For a JSON report:

 

Code:

Code:
lychee . --format json --output broken-links.json

JSON is useful when you want to process results using another script.

BONUS — FIND ARCHIVED VERSIONS OF BROKEN LINKSHere's a feature that makes Lychee particularly interesting.

It supports suggesting replacement links using the Wayback Machine.

Run:

 

Code:

Code:
lychee --suggest .

When possible, Lychee will attempt to find archived versions of broken links.

This can help recover references to:
- Deleted articles

- Old documentation

- Discontinued projects

- Removed tutorials

- Historical resources

An archived page isn't guaranteed to exist, and an archive link isn't always an appropriate replacement for a live URL.

BONUS #2 — CHECK LINKS IN GITHUB PROJECTSMany GitHub repositories contain README files with links to:
- Documentation

- Dependencies

- Example websites

- Tutorials

- External resources

Over time, some links stop working.

Clone your own repository:

 

Code:

Code:
git clone https://github.com/OWNER/REPOSITORY.git

Replace the owner and repository placeholders with your project details.

Enter the folder:

 

Code:

Code:
cd REPOSITORY

Run:

 

Code:

Code:
lychee .

You can now check the links inside the project's supported files.

This is particularly useful for maintaining open-source documentation.

BONUS #3 — AUTOMATE LINK CHECKINGDon't want to run the tool manually every week?

Lychee has an official GitHub Action.

GitHub Action:

https://github.com/lycheeverse/lychee-action

You can integrate it into your own repository so link checks run automatically.

For example, you could configure checks to run:
- Whenever documentation changes

- Before merging a pull request

- On a weekly schedule

- Before a website release

This helps catch broken links before users find them.

BONUS #4 — USE DOCKERDon't want to install Lychee directly?

It also supports Docker.

Install Docker:

https://www.docker.com/products/docker-desktop/

Open PowerShell inside the folder you want to scan.

Run:

 

Code:

Code:
docker run --init -it --rm -w /input -v ${PWD}:/input lycheeverse/lychee .

Docker will run Lychee against the supported files in your current folder.

CAN YOU USE THIS FOR SEO?Yes, as a technical maintenance tool.

Broken links can create a poor user experience and prevent visitors from reaching useful pages.

You can use Lychee to:

- Identify broken URLs.

- Investigate why they're failing.

- Find suitable replacement destinations.

- Update or remove outdated links.

- Run another scan to verify the changes.

However, fixing links doesn't guarantee higher Google rankings.

Lychee also isn't a replacement for a comprehensive SEO crawler.

IMPORTANT — FALSE POSITIVESNot every failed request means a link is permanently broken.

Some websites may:
- Block automated tools

- Require authentication

- Apply rate limits

- Temporarily return server errors

- Require JavaScript to display content

Always manually investigate questionable results before removing links.

For websites that block

Code:

Code:
HEAD

requests, Lychee supports configuring request methods.For example:

 

Code:

Code:
lychee --method head,get https://example.com

This attempts

Code:

Code:
HEAD

and falls back to

Code:

Code:
GET

if necessary.IS IT STILL MAINTAINED?Yes.

The official GitHub repository is active and continues to provide Windows, Linux, and macOS installation methods.

The project documents its link-checking CLI, output formats, archive suggestions, and GitHub Actions integration.

SOURCEShttps://github.com/lycheeverse/lychee

https://github.com/lycheeverse/lychee/releases

https://github.com/lycheeverse/lychee-action

https://lychee.cli.rs/

If you're managing websites, documentation, or GitHub repositories, Lychee is worth adding to your toolkit.

Instead of manually opening hundreds of URLs, you can check them automatically and focus on fixing the links that need attention.

 

WANT MORE HIGH QUALITY SHIT FOR FREE?

CLICK HERE > (MY PROFILE)

Haven't made a account yet? register here (REF LINK)




 

179,168

126,023

1,405,739

Top