Best Free Broken Link Checkers (2026): Crawl, Status Codes, Export

Short answer: the best free broken link checker in 2026 is the one that matches your scope. Use curl or a status-code tool for a single href, a hosted scanner with a page cap for a quick marketing-site pass, Screaming Frog SEO Spider free mode when you need crawl depth and CSV export, and Google Search Console on verified sites when you want Google’s view of not-found and crawl anomalies.

This page covers broken link checkers only: tools that crawl or request URLs and report HTTP status codes, especially 4xx and 5xx. It is not a roundup of meta tag checkers, robots.txt generators, redirect tracers, keyword research tools, or schema markup builders. Those jobs need different pages.

Answer-first shortlist

If you only have a few minutes, start here:

One URL or a short list: curl HEAD requests or a free HTTP status checker.
Whole small site, no install: a hosted broken link scanner with a published page limit (see ranked tools below).
Export with inlinks and status columns: Screaming Frog SEO Spider free mode (URL cap applies).
Google’s crawl picture: Search Console Page indexing and crawl stats on verified properties.
After 404s are fixed: ship cite-ready pages whose outbound citations and internal routes stay live; see the auto SEO tool overview when you want that workflow on your stack.

No checker replaces updating hrefs in your CMS, templates, or markdown. Scanners show symptoms. Your release process owns the cure.

What a broken link checker should show

A useful broken link report answers five questions:

Which URL failed? The exact href the crawler requested.
What status code? At minimum 404, 410, and 5xx, with redirects noted separately.
Who linked to it? Source URL and anchor text when the tool crawls internal links.
Internal or outbound? Broken internal links hurt navigation; broken outbound links hurt trust on cite-ready content.
Can you export? CSV or spreadsheet columns you can sort, assign, and re-check after deploy.

Bulk checks should include crawl depth or inlink count so you fix high-traffic templates first. Re-run the same export after deploy to prove the 404 count dropped.

Ranked free tools by job

This ranking is by fit for common free workflows, not by market share or traffic claims. Free tiers change; validate on export quality and page limits.

Screaming Frog SEO Spider (free mode) for desktop crawl, response-code filters, inlink export, and sitemap-only modes on small sites.
Google Search Console for verified sites when the question is what Google saw, including soft 404 and crawl anomalies.
Dead Link Checker (deadlinkchecker.com) and similar hosted scanners for a fast off-the-shelf crawl with a published page cap.
BrokenLinkCheck.com for another hosted pattern: enter a start URL, wait for the scan, download or review broken rows.
W3C Link Checker (validator.w3.org/checklink) for standards-focused single-page and recursive checks with explicit status reporting.
curl and wget for scripted spot checks, CI gates on critical URLs, and custom loops over a sitemap.
Browser devtools Network tab for one-page manual verification when you suspect JavaScript-rendered hrefs.
Orchory free on-page checker (SEO checker for website) for head tags and content signals on one URL, not a substitute for a full-site 404 export.

TL;DR comparison table

Job	What you learn	Free starting point	Limit to know
Single URL status	One status code and final URL	`curl -sI -o /dev/null -w '%{http_code}\n'` or HTTP status web tools	No source-page context
Hosted site scan	List of broken hrefs with codes	Dead Link Checker, BrokenLinkCheck.com, similar	Page caps, queue wait times
Crawl plus export	Inlinks, depth, response codes	Screaming Frog free mode	500 URL crawl cap at time of writing
Google’s index view	Excluded URLs, not found patterns	Search Console Page indexing	Verified properties only
Internal link graph	Orphan and underlinked routes	Crawl export plus internal linking in HTML audit habits	Needs interpretation, not just a red list

This table avoids invented vendor rankings or traffic statistics. Evaluate tools on whether they show status codes explicitly and whether exports include source URLs.

curl and spot checks

For developers, curl is the always-free broken link checker for a known URL list. Request headers only to avoid downloading bodies:

curl -sI -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://example.com/docs/missing'

Loop over critical paths after a deploy, or over every loc in a sitemap when the sitemap lists only canonical URLs. Fail the build when any row returns 404 or 5xx.

Pair spot checks with internal link discipline. Google documents crawlable links as HTML anchors with href values (Google crawlable links guide). A status check on a URL nobody links to still matters for outbound citations on blog posts.

Free hosted crawlers

When you need a shareable report without installing software, hosted broken link scanners are the fastest path. Common patterns among reputable free tools:

Dead Link Checker crawls from a start URL and lists broken links with status information.
BrokenLinkCheck.com offers a similar workflow with a visible queue during large scans.
W3C Link Checker suits single-page validation and recursive checks when you want a standards-oriented tool.

Compare hosted tools on clarity: do they distinguish 404 from 403, show which page contained the link, and let you export results? Avoid tools that only report a count without URLs you can paste into tickets.

Hosted crawlers usually fetch HTML without executing JavaScript. If your site renders links client-side, confirm with a rendered crawl or manual Network inspection.

Desktop crawl and export

Hosted scans hit page caps quickly on growing sites. Screaming Frog SEO Spider in free mode remains a common desktop starting point: crawl internal URLs, open the response codes report, filter to client error (4xx) and server error (5xx), and export URL, status code, inlinks, and anchor text.

Other free-adjacent workflows teams use:

Crawl sitemap URLs only when the sitemap is trustworthy.
Filter outbound links on citation-heavy pages after publishing a research post.
Cross-check orphan routes using crawl depth, as described in internal linking strategy.

After a content migration, run a broken link export and a redirect map in parallel. Fixing 404s without updating internal anchors leaves users one click away from the next dead URL.

Search Console and server logs

Google Search Console is not labeled a broken link checker, but it is the authoritative free surface for not-found and crawl problems on sites you verify. The Page indexing report shows why URLs are excluded or error, which often surfaces 404 routes Google attempted to crawl.

Server and CDN access logs complement crawlers: filter status 404 after launch week to find URLs real users and bots requested. Logs show demand; crawlers show link graph context. Use both when a 404 appears in Search Console but your last export looked clean.

For crawl-first habits that include link hygiene, read how to do SEO by yourself and why your site is not showing on Google for sitemap, indexing, and discovery checks.

Broken links and cite-ready pages

Broken link checkers diagnose href health. Cite-ready pages are the outcome you want after links work: one stable URL that returns 200, an answer-first opening, claims tied to live sources, and structured data that matches the visible body.

404 outbound links on a guide undermine the same trust you built with careful sourcing. Internal 404s strand readers and crawlers on dead routes inside your product story. Assistants may still quote your headline while the footnotes fail.

Orchory does not ship a dedicated sitewide broken link crawler today. Orchory is built for teams that turn prioritized topics into cite-ready pages on their design system. Free URL tools on Orchory focus on on-page head and content signals rather than exporting every 404 on a ten-thousand URL site.

The practical split:

Broken link checker (this list): export 4xx and 5xx URLs with status codes and source pages.
On-page checker: confirm title, description, canonical, and headings on the live URL.
Orchory workflow: ship new answer-first pages whose internal and outbound hrefs you intend to keep current.

Browse the free tools catalog for meta tag, Open Graph, and related checkers. When link exports are clean and you want automated page production on your stack, read the auto SEO tool overview. Send your site when you want help connecting link fixes with a steady page pipeline.

Broken link checkers vs other SEO tools

Search intent drifts easily. Keep the jobs separate:

Broken link checker: 4xx and 5xx destinations plus source URLs from a crawl export.
Redirect checker: 3xx hop lists and final landing URLs (different workflow).
Meta tag checker: head tags on one URL (different workflow).
Keyword research tool: query discovery (different workflow).

Using the wrong tool wastes time and creates overlapping articles on your own site. This piece stays in the broken-link lane so it can link honestly to crawl and internal-link resources without repeating full comparisons from other listicles.

Ready to run a scan? Export your 404s, fix hrefs in templates and posts, re-crawl to confirm 200s, then explore the free tools hub or the auto SEO tool when you move from measurement to shipping cite-ready pages. Send your site when you want help applying the workflow to your stack.

FAQs

What is the best free broken link checker in 2026?

There is no single winner. For one URL, curl or a free HTTP status tool is enough. For a marketing site under a few hundred URLs, Screaming Frog SEO Spider in free mode or a reputable hosted broken link scanner with a page cap is the usual starting point. For properties you verify in Google, Search Console surfaces crawl issues and not-found patterns alongside other indexing data.

What HTTP status codes count as a broken link?

Most teams treat 404 Not Found and 410 Gone as broken internal or outbound links. 5xx server errors are broken for users even when the URL might return later. Redirects are not broken by themselves, but chains that end in 404 still fail the destination check. A good report lists the status code per URL, not just a red icon.

How is a broken link checker different from a redirect checker?

A broken link checker flags destinations that error, usually 4xx or 5xx, and often shows which source page contains the bad href. A redirect checker follows 3xx hops until a final response. Run both after migrations: redirects for hop hygiene, broken link scans for dead destinations and outdated outbound references.

Can free broken link checkers find JavaScript-only links?

Many free crawlers fetch HTML without executing JavaScript. Links that appear only after client-side rendering may be missed until you crawl with a rendered mode or inspect the live DOM. Pair an HTML crawl with Search Console URL Inspection when a page looks fine in the browser but fails in an export.

Why do broken links matter for cite-ready pages?

Answer engines and search systems prefer pages where factual claims point to live sources. A body full of 404 outbound links erodes trust signals, and internal 404s strand users and crawlers on dead routes. Fixing links is technical hygiene before you invest in answer-first content and structured data.

Does Orchory replace a broken link checker?

No. Orchory prioritizes new cite-ready pages and on-page quality on your stack. Use the free checkers in this list to export 404s and status codes, fix hrefs in your templates and content, then use Orchory when you want a steady pipeline of new pages with working internal and outbound links.