Internal URL Not Found (4XX): Fix Broken Internal Links

What this means

A 4XX status code is the server telling a browser or crawler that the request failed on the client side. The most common is 404 Not Found, but the family also includes 410 Gone, 403 Forbidden, and 401 Unauthorized. When SEO ProCheck flags an "Internal URL Not Found (4XX)," one of your pages contains a hyperlink pointing to a URL on your own domain that no longer resolves to a working page. The page is still published and the link still looks normal, but anyone who clicks it lands on an error.

Why it matters

Broken internal links hurt on three fronts at once:

• User experience. A visitor following the link hits a dead end instead of the content they expected. That erodes trust and often ends the session.
• Crawl efficiency. Search engines follow internal links to discover pages. Every request that resolves to a 4XX is wasted effort that could have gone toward pages you want indexed.
• Link equity and signals. Internal links pass relevance and ranking signals between pages. A link to a dead URL passes that value nowhere, and a site full of broken links signals poor maintenance.

For the bigger picture on structuring and maintaining links, see our complete guide to internal linking.

How it gets flagged

A crawler like Screaming Frog or Sitebulb requests every URL it finds and records the status code returned. In Screaming Frog you open the Response Codes tab and apply the Internal and Client Error (4XX) filters to list every internal URL returning a 4XX.

To find the pages holding the broken links, select a flagged URL and open the Inlinks tab. The From column shows the source page; the To column shows the dead destination. To handle them at scale, use Bulk Export > Response Codes > Client Error (4XX) Inlinks for a spreadsheet of every source page and broken URL. SEO ProCheck surfaces the same relationship so you know which page to edit.

How to fix it

Work from the exported source-to-destination list. For each broken internal link, pick one of three fixes:

1. Correct the link. If the target still exists at a different address, or the URL has a typo, edit the link on the source page to point to the live URL. This is the cleanest fix because it removes the bad request entirely.
2. Remove the link. If the destination is gone for good with no replacement, delete the hyperlink or repoint it to a relevant existing page.
3. Redirect the target. If the page genuinely moved, add a 301 redirect from the old URL to the closest live equivalent. A 301 is permanent and passes signals to the new location, which is why it beats a 302 here. See 301 vs 302 redirects.

A redirect is a safety net, not a substitute for the first fix. Where you control the source link, update it directly. A 404 means "not found," while a 410 means "gone on purpose," so if you deliberately removed content with no replacement, a 410 can be the honest signal, as explained in 404 vs 410 status codes. Either way, correct or remove the internal link. When done, re-crawl to confirm the 4XX count has dropped to zero.

False positives

Not every flagged URL is a genuine problem. Watch for these:

• Rate limiting. A fast crawl can trip a 429 or temporary 403 from servers that throttle automated requests. Re-crawl more slowly to confirm.
• Login-gated pages. A 401 or 403 on member or admin areas is expected, not a broken link. Exclude these from the report.
• Bot blocking. Some WAFs or CDNs serve a 4XX to the crawler's user agent while real browsers load the page fine. Verify in a browser before editing.

FAQ