Best of · SEO & Web Analytics

8 Best Free Broken Link Checkers for Website Repairs

Finding a dead URL is half the job; you also need the page containing its link. My best free broken link checkers cover small business sites, growing blogs and documentation projects. The picks draw on official features, current free allowances and developer or user discussions. I'd start with Screaming Frog for a small site's repair list, or Dr. Link Check for a browser workflow.

A magnifying glass examines a broken link between paper website pages.
On this page
  • Small site audit: Screaming Frog SEO Spider. Trace a failed URL back to its linking pages in the desktop report.
  • Browser report: Dr. Link Check. Free Lite covers two projects and 1,500 links per project.
  • Occasional manual scan: Dead Link Checker. Start from a public website without installing software.
  • Larger free page allowance: BrokenLinkCheck.com. Its free limit is 3,000 pages.
  • A site you can verify: Ahrefs Webmaster Tools. Free Site Audit credits support ongoing owner checks.
  • Links and anchors in one document: W3C Link Checker. A focused public checker with optional recursion.
  • Broader local report: SiteOne Crawler. Open-source crawling with HTML and machine-readable reports.
  • Docs in a repository: lychee. Check links in Markdown and built HTML during development.

Compare the free allowances carefully #

ToolBest forPlatformsFree limitsPaid optionWhere it runsStandout strength
Screaming FrogFinding source pages for repairsWindows, macOS, Linux500 URLs per crawlAnnual license adds larger crawls and advanced featuresYour desktopInlinks and exports
Dr. Link CheckBrowser-based project reportsWebTwo projects, 1,500 unique links each; one-time checksPaid plans add allowances and scheduled checksService serversSimple project-based scans
Dead Link CheckerManual checks of public sitesWebManual checks free; full scan depth limited to 10Auto Check subscriptionsService serversSingle or multiple-site checking
BrokenLinkCheck.comChecking more pages onlineWeb3,000 pages; hyperlinks within them aren't cappedCommercial version for larger jobsService serversLink location in source HTML
Ahrefs Webmaster ToolsAuditing a verified propertyWeb5,000 crawl credits per project per monthBroader Ahrefs subscriptionsCloud crawlerOwner audit alongside SEO data
W3C Link CheckerA page's links and anchorsWebPublic checker; choose recursion depthNo paid account requiredService serversAnchors and referenced objects
SiteOne CrawlerWider technical reportsWindows, macOS, LinuxFree MIT project; hardware and crawl settings applyNo license subscription requiredLocal applicationHTML, JSON and text output
lycheeSource docs and built filesWindows, macOS, LinuxFree; remote URL input checks that page, without recursive site crawlingNo paid planCLI on your computer or build runnerMarkdown and HTML inputs

Official references: Screaming Frog, Dr. Link Check plans, Dead Link Checker FAQ, BrokenLinkCheck.com, Ahrefs free allowances, W3C checker, SiteOne repository and lychee usage.

Paidscreamingfrog.co.uk/seo-spiderDetails

Screaming Frog: the best starting point for a small repair list

The detail I'd look for first is the lower Inlinks panel. Selecting a failed destination shows the pages linking to it, so you can go straight to the content that needs changing. The official broken-link tutorial explains this report and its bulk export.

Users in a September 2026 discussion praised the crawler's detailed reporting and configuration. One reply also acknowledged that the interface looks less polished than a broad SEO suite. For a repair job, I'd prioritize a clear source-and-destination report over a pretty overview.

The free version crawls 500 URLs on Windows, Mac or Linux. That's its serious restriction, but it still wins for a small site because the report helps you act on the findings. Larger crawls and advanced features require an annual license.

Don't count only your published articles when judging that allowance. A site can expose many more URLs than the number of posts in its editor. Start with a modest audit and check whether the crawler reached the end.

Pick it if you want a practical desktop repair report for a small website. Skip it if a full site scan needs more than the free URL allowance. Use the Screaming Frog guide for the basic workflow.

ahrefs.comDetails

Ahrefs Webmaster Tools: the owner option for a growing site

Ahrefs gives verified projects 5,000 Site Audit crawl credits per month. Its official free-tools page explains an unusual counting rule: credits are used for HTML pages returning status 200. Broken URLs, redirects and non-HTML resources don't consume those credits.

That makes Ahrefs worth considering when you manage a growing public site and can verify ownership. I'd use the audit alongside the site's other SEO data, then turn each confirmed broken internal link into an editing task. A cloud report can be easier to revisit than a one-off desktop export.

The weakness is ownership and account setup. This free route is for verified websites, so it isn't the easiest way to check a random site's links. It also puts the crawl in an external service rather than on your own computer.

The free allowance renews monthly per project. Broader Ahrefs subscriptions increase access and allowances, but I'd first see whether the owner audit covers the job. Paying for a large SEO suite solely to find a few broken links is hard to justify.

Pick it if you want an audit of a website you can verify and maintain. Skip it if you only need a quick check of a page on someone else's site.

Open sourcegithub.com/janreges/siteone-crawlerDetails

SiteOne Crawler: wider reports without a license subscription

SiteOne Crawler is an MIT-licensed project with Windows, Mac and Linux support. Its repository offers an interactive command-line wizard and a separately linked desktop GUI. Reports include HTML, JSON and text, with checks for errors such as 404s and redirects.

I'd consider it when broken links are one part of a wider technical review. You can keep the report local and hand a readable HTML result to someone working on the site. Machine-readable output gives a developer another route for repeatable checks.

The breadth is also its weakness. The project includes auditing, cloning and export features, so a first-time user has more choices to understand than in a dedicated link form. Choose an audit workflow and avoid adding jobs that aren't part of the repair request.

There is no paid license subscription required for the open-source crawler. Hardware, configuration and the website's response still affect what it can scan. I'd treat it as a tool for someone willing to learn the report, rather than the default for an editor making two quick corrections.

Pick it if you want local open-source crawling and wider technical reports. Skip it if a single-page browser checker already answers the question.

Open sourcelychee.cli.rsDetails

For developers: lychee checks the files before they go live

lychee reads links from Markdown, HTML and other input files. Its getting-started documentation makes a key distinction: directories are traversed recursively, but a remote webpage input doesn't become a recursive crawl of the entire website. Supply the pages or built files you want checked.

The surprise is how a working GitHub fragment can fail a checker. In issue 1729, opened June 2025 and still active in 2026, a maintainer explained that some GitHub Markdown headings work through JavaScript without matching HTML IDs. That's a reason to inspect fragment reports before deleting perfectly good references.

I'd choose lychee for a documentation repository or static-site build. You can make the check part of the publishing workflow instead of waiting for a reader to report a dead link. The drawback is configuration: online URLs and local build paths can need explicit mapping. The Screaming Frog vs lychee comparison covers that choice.

Pick it if your content lives in source files and you want repeatable checks. Skip it if you expect one homepage URL to discover and audit every page for you.

Decide what the report needs to contain #

For a content repair, keep source page, failed destination and link text together. The source tells the editor where to work, and the text helps identify the right reference when the page has many links. A bare list of failed URLs pushes that search back onto the editor.

For a static website, decide whether you are checking the current public site or the build you're about to publish. They can contain different files. A successful public URL doesn't prove the next build includes that resource.

Choose one checker that fits the workflow, then make a clear repair list. The step-by-step Screaming Frog guide shows how to turn crawl output into source-page edits.

How we chose #

I checked official feature descriptions, free allowances, documentation and current project activity on October 9, 2026. Recent user discussions and maintainer explanations informed the practical catches, with browser tools favored for occasional owners and source-file checkers kept in the developer section.

FAQ #

I'd start with Screaming Frog when the site fits its 500-URL free crawl. The source-page report makes it practical to locate and change the links. Dr. Link Check is my browser alternative for occasional scans. Choose by the size of the crawl and the kind of report you'll actually use to make repairs.

It can be, if the tool's allowance and discovery method cover the blog. BrokenLinkCheck.com offers 3,000 pages, while Ahrefs provides monthly crawl credits for verified properties. These units aren't interchangeable. Check whether the scan finished and whether older archives were reached before treating the report as a complete list of repairs.

Yes, several picks check external destinations referenced by the pages they scan. Screaming Frog and BrokenLinkCheck.com document internal and external checks. The repair still happens on your own source page: update the reference, replace it with a better destination or remove it when the resource is gone. A report doesn't make that editorial decision for you.

The tools listed here primarily help you find and inspect failures. I'd make the correction in the CMS or source file, then check the changed page again. Automatically replacing a URL with the homepage can hide the error while sending readers somewhere irrelevant. Choose a replacement that answers the same question as the original reference.

I'd use Search Console and a link checker for different questions. Search Console provides Google's view of a verified property; a crawler helps trace links in the pages you're auditing. For a repair task, you need the source page containing the bad reference. Keep that source-and-destination information in the task you give an editor or developer.

Sources #

Official tool and allowance links are in the table and individual sections. The exclusive experience sources here are September Screaming Frog feedback and lychee's GitHub fragment discussion.

Featured illustration: WebIndexly, created with OpenAI image generation.

D
Donna PickardSenior Technical Writer

Donna Pickard is a Senior Technical Writer dedicated to making enterprise software and SaaS products easy to navigate. With 7+ years of experience delivering everything from deep-dive API guides to intuitive online help systems, she knows how to make technical content click. Donna currently lives…

More best-of lists

All lists