Why broken links quietly destroy SEO
Every broken link on your site is a small leak. Internal broken links waste crawl budget (Googlebot spends time fetching 404s instead of indexing real pages) and signal poor maintenance. External broken links degrade user experience and can be interpreted as a quality signal against your domain.
This checker fetches every link on a page and tests its HTTP status, classifying results into healthy (2xx), redirects (3xx), broken (4xx and 5xx), and slow (over 2 seconds). For site-wide audits across thousands of pages, the full DarnItSEO Audit crawls everything and reports broken links per source page.
What counts as a broken link
4xx status codes (404 Not Found, 410 Gone, 403 Forbidden) and 5xx status codes (500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable) are unambiguously broken. Network errors (DNS failures, connection refused, timeouts) also count as broken from the user's perspective.
Redirects (3xx) are not broken but introduce latency and chain risks. A 301 to a still-live destination is fine. A 301 to another 301 to another 301 (a redirect chain) wastes crawl budget and degrades performance. Use the Redirect Chain Checker for deeper redirect analysis.
Internal versus external broken links
The report separates broken links by where they point, and the distinction drives how urgently you should act. Internal broken links point to other pages on your own site, so they are entirely your responsibility and entirely within your power to fix. They are also the more damaging kind for SEO, because they waste crawl budget on your own domain and stop internal authority from flowing where it should. These deserve your attention first.
External broken links point to other people's sites, which you do not control. They matter mainly for user experience and credibility: a reader who clicks a dead citation loses trust, and a page full of rotted outbound links looks abandoned. You cannot stop a third party from taking their page down, but you can and should replace or remove the dead link on your end. Sorting the report into these two groups lets you fix the high-impact internal problems quickly and schedule the external cleanup as ongoing maintenance.
The most damaging broken-link scenarios
Internal links to pages you have deleted but forgotten to update. Common after content migrations, URL slug changes, or consolidating pages. Find with this tool and either fix the link or 301-redirect the deleted URL.
Outbound links to third-party domains that have gone offline or changed structure. Less under your control but still worth fixing because user-facing 404s damage trust. Replace with archived versions (web.archive.org) or different sources.
Image src links that fail. Missing images render as broken icons and inflate Largest Contentful Paint when the image was supposed to be the LCP element. Fix immediately.
How often to audit broken links
Monthly for active content sites. Quarterly minimum for static sites. After every major content migration or theme change. The DarnItSEO Audit can be scheduled to run weekly with email alerts on newly detected broken links.
Pages with high inbound links and high traffic deserve more frequent checks because broken links there compound the cost. Pages buried at depth 5+ matter less.
What this checker tests, link by link
When you submit a page, the tool fetches its HTML, extracts every link it can find, including anchor hrefs and image sources, and then sends a request to each destination to see how it responds. It records the HTTP status code, whether the URL redirected before resolving, and how long the response took. The result is a per-link verdict rather than a vague "some links may be broken" warning: you see exactly which URL failed, with which code, on the page you submitted.
Because it tests the actual destinations rather than just reading the markup, the checker catches links that look fine in your source but no longer resolve, which is the whole point. A link can be spelled perfectly and still be broken because the page it points to was deleted or moved. This single-page focus makes the tool fast and precise for auditing one page at a time; for testing every page on a domain at once, you move up to a full crawl.
How to read the status codes this tool reports
The checker groups every link by its HTTP response so you can act on the right ones first. A 2xx (usually 200 OK) means the link works. A 4xx means the client request failed and the link is broken from the user's side: 404 Not Found is a missing page, 410 Gone is a page intentionally removed, 403 Forbidden is access denied, and 401 Unauthorized means the resource needs a login. A 5xx means the destination server itself failed, which may be temporary, so it is worth re-testing a 500 or 503 before assuming the link is permanently dead.
Redirects (301, 302, 307, 308) are reported separately because they are not failures but they are not free either. A single 301 to a live page is fine. Watch for redirects that land on a 404, which is a broken link hiding behind a redirect, and for long redirect chains that add latency to every fetch. The slow bucket (links that respond but take more than two seconds) flags destinations that work today but signal an unreliable third party or an overloaded server.
Why some links report broken when they are not
Occasionally a link works in your browser but this tool reports it as broken, and the reason is almost always how the destination treats automated requests. Some sites return a 403 or 429 to any client that is not a logged-in human browser, including link checkers and even Googlebot. Others block requests that arrive without cookies, a referrer, or a specific user agent. These are false positives in the sense that a real visitor can reach the page, but they are still worth noting, because a destination that blocks crawlers may also be invisible to search engines.
The opposite mistake is more dangerous: a link that returns 200 OK but shows a "page not found" message in the body. That is a soft 404, and because the status code is healthy, an HTTP-only checker cannot catch it. If you suspect a destination is serving an error page under a 200 status, verify it manually or use a soft 404 detector that inspects the page content rather than just the status line.
Broken links and crawl budget on larger sites
On a small brochure site a handful of 404s barely matter. On a large site they compound. Every internal link to a dead URL sends Googlebot to fetch a page that returns nothing useful, spending crawl budget that should have gone to your real content. When a meaningful share of your internal links are broken, crawlers waste time, recrawl your important pages less often, and may slow how quickly new or updated pages get discovered and indexed.
Broken links also fragment the flow of internal PageRank. Authority that should have passed from a strong page to a deeper one leaks into a dead end instead. Fixing internal broken links is therefore not just a tidiness exercise; it directly improves how efficiently your link graph distributes ranking signals to the pages you want to rank.
Fixing strategies
For internal broken links, two options. If the destination page exists at a new URL, update the link or 301 redirect the old URL to the new one. If the destination is permanently gone, either remove the link or redirect to the most relevant live page. Avoid sending all 404s to the homepage; that creates soft 404s and wastes link equity.
For external broken links, replace with a working source if possible. If the original source is permanently gone, link to the Internet Archive's saved copy. As a last resort, remove the link and rephrase the surrounding text so it still flows.
Always prefer fixing the link itself over relying on a redirect. Updating the href to point straight at the correct live URL gives users and crawlers the shortest path and avoids accumulating redirect hops over time. Reserve redirects for cases where you cannot edit every link that points at the old URL, such as inbound links from other sites you do not control.
Broken links, trust, and AI search in 2026
Link health has quietly become an AI-search signal as well as a classic SEO one. AI answer engines and large language models evaluate the quality and reliability of a source partly by how well maintained it is. A page riddled with dead outbound links and broken internal navigation reads as neglected, which makes it a weaker candidate to be cited or summarized. Clean, working links signal an actively maintained, trustworthy resource.
Outbound links to authoritative, still-live sources also help AI systems place your content in context and verify its claims. When those citations rot into 404s, you lose that supporting evidence and the surrounding text can read as unsupported. Keeping your links healthy is part of keeping your content credible to both traditional search and the AI systems that increasingly decide which pages get surfaced.
What to do after you run this check
Triage first. Fix internal broken links before external ones, because those are fully in your control and they damage crawl efficiency and link equity directly. Within the internal group, prioritize broken links on high-traffic, high-authority pages, where the cost compounds. Then work through external 404s, replacing or removing them.
Make the check recurring rather than a one-off. Re-run it after every content migration, slug change, or page consolidation, since those are exactly the moments links break. This tool inspects one page at a time; for a site-wide picture across thousands of pages, the full DarnItSEO Audit crawls everything, reports broken links per source page, and can be scheduled to run on a regular cadence with alerts on newly detected breaks.