Do redirects really weaken your link power?

Where does this 50% loss rumor originate?

For years, the SEO community has spread the idea that a redirect results in an automatic loss of 50% of link power. This belief dates back to the early days of PageRank sculpting, when some practitioners observed ranking fluctuations after migrations.

The myth has fueled itself through partial observations and random correlations. When a site lost traffic after a redesign with redirects, many attributed this decline to a mechanical loss of PageRank rather than implementation or structural errors.

What exactly does Google say about this?

The statement is unambiguous: no 50% loss exists. Google treats both 301 and 302 redirects similarly, regarding them as signals for transferring link authority to the destination page.

Technically, the algorithm follows the redirect chain and allocates the full PageRank to the final page. There is no reduction coefficient automatically applied at each redirect hop.

Why does this clarification change the game?

This confirmation frees technical projects that require complex URL migrations. You can restructure your hierarchy, switch to HTTPS, or change domains without fearing systematic penalties on your authority.

However, Google does not say that redirects are 100% neutral. A poorly designed chain can slow down crawling, generate crawling errors, or create loops. It is the technical implementation that poses problems, not the redirect principle itself.

• Both 301 and 302 redirects transfer PageRank without a mechanical loss of 50%
• Redirect chains remain functional but should be limited to a maximum of 3 hops
• Correct implementation (HTTP status, absence of loops) is more critical than the number of redirects
• A well-planned migration with clean redirects does not penalize the site's authority
• The myth of PageRank Sculpting through redirects is no longer technically valid

Is this statement consistent with field observations?

Overall, yes. Well-executed migrations with clean 301 redirects show authority preservation in most cases. Sites that lose traffic after migration often have structural issues (broken architecture, destroyed internal linking, content loss).

The real issue is never the redirect itself, but its context: too long chains, redirects to irrelevant pages, or worse, lazily redirecting to the home page. Google follows the redirect, but if it leads to inappropriate content, the relevance signal collapses.

What nuances should be added to this statement?

Google remains vague on a crucial point: the speed of PageRank transfer. Saying that there is no loss does not mean that the transfer is instantaneous. Observations show variable delays depending on the crawling frequency of the source page.

Additionally, there is a difference between not losing PageRank and maintaining your actual ranking. If you redirect 50 URLs to a single consolidated page, PageRank theoretically adds up, but thematic relevance may dilute. [To be verified] how much Google adjusts the relevance signal in these massive consolidations.

In what cases might this rule show its limits?

Temporary 302 redirects have long been treated differently. Google now claims they also transfer PageRank, but the historical behavior was less clear. If your site has been using 302s for months, check that Google hasn't interpreted this as a signal of non-permanence.

Excessive redirect chains (5+ hops) pose a crawl budget problem more than a PageRank loss. Googlebot may abandon tracking before reaching the final page, which effectively results in a total loss of the link.

How can you check if your redirects are transferring authority?

First step: audit your redirect chains with Screaming Frog or Oncrawl. Identify any chain exceeding 2 hops and correct them to point directly to the final destination.

Secondly, check in the Search Console that Google is properly indexing the destination URLs, not the old redirected URLs. If the old ones persist in the index after several weeks, it’s a sign that something is blocking the crawl.

What mistakes should be avoided during a migration with redirects?

Never redirect in bulk to the home page for convenience. Each old URL must point to the most thematically relevant page. A generic redirect destroys the relevance signal even if the technical PageRank is passed.

Avoid redirect loops and client-side redirects via JavaScript. Google can follow them, but it’s slower and less reliable than a standard HTTP 301 server redirect.

What concrete steps should you take after this clarification?

If you've delayed a redesign out of fear of losing SEO juice, you can now plan with confidence. Prepare a 1:1 mapping table between old and new URLs, implement clean 301 redirects, and monitor the evolution of organic traffic over 3 months.

For complex sites with thousands of pages, a technical migration remains a delicate project that requires expertise and specialized tools. If your internal team lacks experience on these projects, it may be wise to consult a specialized SEO agency to avoid classic pitfalls and ensure a seamless transition without loss of visibility.

• Audit all existing redirect chains and reduce them to a maximum of 1-2 hops
• Ensure that each redirect points to a thematically relevant page, not just to the home page
• Test HTTP codes (301 vs 302) and correct accidental 302s to 301 for permanent changes
• Monitor the indexing of new URLs in the Search Console for 4-6 weeks post-migration
• Document the mapping table to facilitate rollback in case of critical issues
• Avoid JavaScript or meta-refresh redirects; favor server-side redirects