Does a link to a 404 page still pass on SEO juice?

Why does Google believe a 404 interrupts the transmission of PageRank?

When an external or internal link points to a URL that returns a HTTP 404 code, Google interprets this as a dead end. Crawling stops, no resources are indexed, and mechanically, no trust signals can flow back to the rest of the site.

The logic is simple: if the target page no longer exists, it cannot receive or redistribute PageRank. The link becomes an algorithmic dead end. This is where many sites struggle, accumulating 404 errors without realizing it.

What does Google mean by 'appropriate' redirection?

Google doesn't always specify what it means by 'appropriate', but in practice, it means choosing between a 301 redirect (permanent) and a 302 (temporary). A 301 transfer most of the PageRank to the new URL, while a 302 retains some for the old one.

The pitfall is redirecting to a page with no semantic relevance. A redirect to the homepage by default often results in a net loss of value. It's better to point to a thematically related resource, even if it isn't identical.

Does this rule apply to internal links as well?

Absolutely. Broken internal links dilute the internal linking structure and fragment the flow of PageRank across the site. Regular audits of internal 404s help identify these leaks before they impact SERP performance.

Many corporate or e-commerce sites generate 404s due to product deletions, poorly-planned CMS redesigns, or poorly managed dynamic URLs. These errors accumulate and eventually slow down crawling and degrade the overall authority of the domain.

• A link to a 404 does not transmit any PageRank, neither to the target page nor elsewhere.
• A 301 redirect preserves most of the value of a backlink if the target page is thematically relevant.
• Internal 404s degrade the linking structure and slow down crawling, especially on large sites.
• Regular audits of 404 errors must include external backlinks, not just internal links.
• Google Search Console reports crawled 404s but does not always detect those discovered through infrequent backlinks.

Is this statement consistent with observed practices on the ground?

Yes, and it's even one of the few areas where Google remains very consistent over the years. Site migration tests show that a 404 page without redirection quickly loses its ranking, even if it had a strong backlink profile.

However, Google remains vague about the exact loss of PageRank when a 301 redirect is used. Officially, there is 'no loss', but in practice, many observe slight erosion, especially if the redirect chain gets longer. [To be verified] with rigorous A/B tests on comparable pages.

In what situations does this rule not fully apply?

There are edge cases. For example, if a 404 page is still cached by Google or accessible via archive.org, some signals may persist temporarily. But this is marginal and should not serve as a strategy.

Another case is soft 404s, pages that return a 200 OK but show empty or generic content. Google often detects these as masked 404s and treats them as such, not transmitting any PageRank. Be cautious not to assume that an HTTP status 200 guarantees the transmission of value.

What nuances should be considered regarding redirects?

A poorly targeted redirect can be worse than a blatant 404. Redirecting all orphan URLs to the homepage dilutes the signal and creates algorithmic confusion. Google prefers a clean 404 over an incoherent redirect.

Furthermore, redirect chains (A → B → C) slow down crawling and erode PageRank with each jump. Limit yourself to a single direct redirect whenever possible. Also, watch for redirect loops; they can block the complete indexing of a section of the site.

What actionable steps should be taken to preserve the value of backlinks?

Start with a complete audit of 404s via Google Search Console (Coverage > Excluded). Cross-reference with a crawling tool to identify orphan pages that still receive external links. Prioritize those with the most backlinks or the best referring domain profile.

Next, determine the best destination for each redirect. If the page was about a specific product, redirect to the parent category or a similar product. If it's a blog article, find the semantically closest content. Avoid the easy route of redirecting everything to the homepage.

How can you check that redirects are correctly configured?

Use an HTTP checking tool (like httpstatus.io or your browser's network console) to ensure that the redirect returns a clean 301, without an intermediate chain. Also, test the redirect speed: a response time that’s too long can penalize crawling.

Then monitor progress in Search Console: redirected URLs should gradually disappear from 404 errors, and new targets should see an increase in their crawl frequency if they inherit strong backlinks.

What mistakes should be avoided when managing 404s and redirects?

Do not create cascading redirects (A → B → C). Google recommends always pointing directly to the final destination. Do not mass redirect to the homepage; it's a weak signal that adds no relevance.

Avoid soft 404s as well: if a page no longer exists, return a true 404 or 410 (Gone), not a 200 with an error message. Lastly, do not let 404s linger for months without action: it degrades the crawl budget and the perceived authority of the site.

• Audit 404s via Search Console and a crawler (Screaming Frog, Sitebulb).
• Identify 404s that receive external backlinks via Ahrefs or Majestic.
• Implement 301 redirects to thematically relevant pages.
• Check for absence of redirect chains or loops.
• Monitor crawl and indexing progress post-redirect in Search Console.
• Regularly clean up internal 404 errors to optimize linking and crawl budget.