Skip to content
EasyWebWeb design & development studio
Free tool

Find the dead links before your visitors do.

Every link on the page followed and verified — internal and external — with the reason each failure happened rather than a bare status code. Genuine 404s are separated from servers that merely block bots, so you are not sent chasing links that were never broken.

What it checks

Everything in one pass.

Every link on the page

Up to 150 links, internal and external, deduplicated and followed one by one.

Real 404s, not false alarms

A refused HEAD is retried with GET, and 403 or 429 responses are reported as blocked rather than broken, because they usually work fine in a browser.

Redirects

Links that resolve via a redirect are flagged separately, along with where they actually end up.

Internal versus external

Filter to just your own pages, or just outbound links to sites you do not control.

Response times

How long each link took, so you can spot the ones that technically work but keep visitors waiting.

nofollow

Which outbound links carry rel=nofollow, which matters if you are auditing how link equity leaves the page.

Questions

What this tool is, and is not.

Does it crawl my whole site?
No. It checks every link on the single page you enter, up to 150. Crawling a whole site properly takes minutes to hours and a queue of background workers, which is a different kind of tool. Checking one page well in twenty seconds is more useful than checking a hundred badly.
What is the difference between broken and blocked?
Broken means the link genuinely does not resolve — a 404, a dead domain, a refused connection. Blocked means the server answered with 403 or 429, which usually means it refuses automated requests but works perfectly well in a browser. Most checkers report both as broken and send you chasing links that were never broken.
Why does it flag redirects if they still work?
Because a redirect in your own markup is a wasted round trip on every visit, and a chain of them is worse. They are not urgent, which is why they are amber rather than red — but pointing links at their final destination is free speed.
It says a link is broken but it opens fine for me.
Some servers treat any non-browser request as hostile, and some geo-block. The tool retries with a normal GET when a HEAD is refused, which catches most of it, but a small number of false positives are unavoidable. Always click through before deleting a link.

Too many to fix by hand?

Broken links are usually a symptom rather than the problem — a migration that went sideways, or a CMS quietly renaming things. Send the report and I will tell you what actually caused it.