Broken Links Finder — the dead links a visitor finds first
A dead link is a small trust leak with a big blast radius: the visitor clicks, gets a 404, and concludes the site is abandoned. This tool fetches one page, tests every link on it up to 25, and tells you which ones fail. It does not crawl the site, and it cannot see a link behind a login. Start with the pages that get traffic, because that is where the leak costs money.
What it checks
One page, up to 25 links, and the status code each one returns: 200, redirects, 404, 410, 403, 429, 5xx, and timeouts. Free, no signup, no captcha. The cap exists so the check finishes in seconds instead of hanging on a slow site.
Which statuses matter
404 and 410 are dead: the reader cannot get there. 5xx is often transient, so retry before changing anything. 403 and 429 usually mean the destination blocks bots or rate-limits requests, so open those in a browser before you delete the link. MDN's status-code reference is the honest source for what each code means.
Fix or redirect?
Redirect only if the old URL has traffic or backlinks. Otherwise fix the link in the page. A redirect chain on an internal link is a slow page on a phone, and redirecting every dead source link turns a link problem into a crawl problem.
Internal vs outbound
An internal dead end is a crawl and UX problem: the reader is stranded and the crawler finds nothing. An outbound dead link is a credibility problem: the source you cited no longer exists, and the page looks unmaintained. Fix both, but fix the internal one first.
Run it after every publish
Links rot later, not at publish time. Sites go down, pages move, old domains expire. Put this in the monthly pass and run it on the ten pages that carry the traffic, not on all 500.
What it cannot do
It cannot crawl the site, test authenticated links, or discover links rendered by JavaScript. It cannot prove a 403 is dead, and it cannot tell you which link is important: that is traffic data, not link data.
The 20-minute cleanup
Pick the money page, run the check, fix the internal dead ends, replace the dead sources, then recheck. If you find a redirect chain, decide whether the destination should be the new URL. Do the whole page in one sitting; half a cleanup is how a page ends up with two broken links and a stale screenshot.
What the table says
| Status | What it means | Action |
|---|---|---|
| 404 | The URL does not exist | Fix the link, or redirect if the old URL has traffic |
| 410 | Gone on purpose | Remove the link; do not redirect into a dead end |
| 5xx | Server failed | Retry; likely transient, not a dead link |
| 403 | Forbidden | Often a bot block; open it in a browser |
| 429 | Rate limited | Wait and retry; not proof the link is dead |
| 301/302 chain | Redirect | Point the link at the final URL |
Questions people actually ask
Does it crawl my site?
No. It fetches one page and tests the links on that page, up to 25. A site-wide crawl is a different job.
Why does a working link show 403?
Because the destination blocks bots, rate-limits requests, or requires a login. Open it in a browser before you change anything.
How many links per run?
Up to 25. The cap keeps one check fast, so start with the pages that get traffic and run the tool again for the next page.
Related tools
Fix it, do not just read about it
Run the free 40-point scan on the page that earns money first. If the list is short, fix it yourself; I mean that. If it is forty things, the Fix Sprint is $1,500 for one site up to 50 pages, with a report card and a 14-day recheck. No ranking guarantee.
Run the free 40-point scan See the fix service