Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Page analysis
  3. Broken Link Checker

Broken Link Checker

Find the dead links on your site before your visitors run into them.

A real crawl of the site, page after page, checking the response code of every link. The pace is deliberately moderate so as not to overload your server.

What this tool is for

A broken link never gives warning. A page renamed during a rebuild, an article deleted, a partner site closing: the link stays in place and leads nowhere. Nobody notices, except the visitor who clicks.

The effect on rankings is indirect but measurable. A dead internal link interrupts the circulation of authority between your pages, and makes Google spend crawl budget for nothing. On a site of a few hundred pages, that can delay the discovery of your recent content.

The effect on credibility is more direct. A page of advice riddled with dead references does not inspire confidence — and that is exactly what Google assesses under expertise and trustworthiness.

The critical moment: a rebuild. Changing the address structure with no redirect plan breaks the entire internal linking at once. It is the first thing to check after going live.

How to read the results

404 is the classic case: the page does not exist. On an internal link, fix at source. On an external one, replace the reference or remove it.

403 means access is refused. Nine times out of ten the remote server is simply blocking bots and the page opens normally in a browser. Check by hand before changing anything.

500 reveals an error on the remote server. That is often temporary: run the analysis again a few days later before concluding.

A timeout designates a server that did not answer in time. On an internal link, that is a performance signal to take seriously — your visitors suffer the same slowness.

The “page of origin” column is the most useful in practice: it says where to fix. When the same dead link appears on fifty pages, it nearly always comes from the menu or the footer, and one fix is enough.

Common mistakes

Dealing with external links before internal ones. Broken internal links are under your control, are fixed immediately, and weigh more since they affect your own linking. Always start with them.

Redirecting everything to the home page. That is the easy way out, and Google treats it as a disguised error. A deleted page with no equivalent should return a plain 404, or better a 410 if the deletion is permanent.

Stacking redirects. Fixing a dead link with a redirect to a page that is itself redirected creates a chain that slows loading and dilutes the signal. The redirect checker reveals those stacks.

Checking only the home page. Dead links lodge in older content, the pages nobody rereads. Yet those are often the pages receiving the most organic traffic.

Forgetting to check after a migration. That is when the most links get broken, and when people least think of checking. Run the tool systematically in the days after going live.

Going further

Frequently asked questions

Do broken links penalise rankings?

Not directly: Google has said on several occasions that dead links trigger no sanction. The effect is indirect but real. A broken internal link wastes crawl budget and interrupts the circulation of authority between your pages. And a visitor landing on an error leaves, which sends an unfavourable quality signal.

Fix or redirect?

Fixing the link at source is always preferable: it is clean, final, and costs nothing in performance. A redirect is called for when the link comes from a third-party site you do not control, or when it exists in too many places to change everywhere. A redirect is a dressing, not a repair.

What about external links to sites that have disappeared?

Three options, in this order. Replace with an equivalent living source, which is best. Remove the link while keeping the mention, if the reference still makes sense. Point to the web archive for historical citations. What you must not do is leave a dead link in reference content: it damages your credibility.

Why are some links reported broken when they work?

Some servers refuse automated requests and return a 403 or 429 to a bot while answering a browser normally. That is frequent on large sites protected by an application firewall. Always check a link reported as 403 by hand before changing it.

How often should I check?

Once a quarter for a stable site, once a month for one publishing regularly. Internal links break mainly during rebuilds and address changes; external links degrade continuously, at roughly 5 % a year. A systematic check after every migration is indispensable.

What does a 999 or 429 code mean?

999 is a non-standard code used notably by LinkedIn to refuse bots: the link works for a human. 429 means you have sent too many requests too fast, and the server is asking you to slow down. Neither designates a genuinely dead link.