Do redirects really cause a loss of PageRank or not?

How does this statement change the game for site migrations?

For years, the SEO community firmly believed that a 301 redirect lost 10 to 15% of PageRank at each hop. This idea, ingrained in the collective imagination since Matt Cutts' early statements, has hindered many redesigns. SEOs feared that a chain of redirects (A → B → C) would turn a powerful backlink into an inaudible whisper.

John Mueller's statement shatters this myth. Google tracks the full path of a link: if URL A redirects to B, and then B to C, the engine directly associates the power of the originating link with the final destination. No cascading loss, no tax at each step. This technical precision now allows for more flexible architectures during migrations, where you can gradually correct chains of redirects without panic.

What’s the difference between 'keeping track' and 'transferring all the power'?

Mueller uses the phrase 'without significant loss'. This 'significant' leaves room for interpretation. Google does not say 'zero loss', but 'no loss that really matters'. In practice, this means that the algorithm treats the redirect as a signal of continuity: the URL has changed, but the underlying entity remains the same.

The practical nuance? A well-implemented redirect (permanent 301, clean HTTP response, no loop) transmits almost all equity. Conversely, a badly constructed chain of redirects can slow down crawling, increase response time, and indirectly affect indexing. It's no longer a matter of diluted PageRank, but of technical performance and user experience.

Does this apply to all types of redirects?

The statement primarily targets 301 redirects, which signal a permanent move. 302 (temporary) redirects operate differently: Google may choose not to transfer all signals since the source URL is supposed to return one day. Meta-refreshes or JavaScript redirects do not receive the same treatment as server 301s.

A concrete example: you redesign an e-commerce site and redirect 5,000 product pages. If each old product page points to the new one via a clean 301, Google will consolidate the link history, domain age, and social signals to the new URLs. You're not starting from scratch, contrary to what urban legend might suggest.

• No PageRank tax on correctly configured 301 redirects: Google tracks the complete path and assigns power to the final destination.
• Tolerated redirect chains: even if A → B → C works, it’s better to correct to avoid latency and crawl budget problems.
• Difference between 301 and 302: only 301 guarantees signal transfer; 302 is interpreted as temporary, so Google can keep the source URL in the index.
• Critical HTTP response: a redirect that returns a 404 or an infinite loop cancels any equity transfer, regardless of the theories on PageRank.
• Peaceful migration possible: you can now restructure your URL hierarchy without fearing the loss of years of accumulated authority.

Is this statement consistent with real-world observations?

In practice, well-executed migrations confirm this theory. Sites that redirected thousands of URLs in 301 maintained their positions at 80-90% in the weeks following the switch, as long as the logical structure remained consistent. If you redirect '/running-shoes' to '/sport/running/shoes', Google understands the thematic continuity and transfers equity.

On the other hand, wild migrations (redirecting all 404s to home, or grouping 10 distinct pages into one) show net losses. It's not the redirect that’s the problem, it's the relevance of the destination. Google does not just follow a link: it assesses whether the destination content satisfies the search intent associated with the anchor and the context of the incoming link.

What nuances should be added to this statement?

Mueller talks about 'non-significant loss', but he avoids quantifying it. Some internal tests from agencies show that a chain of more than three redirects can slow down indexing by 20 to 30%, even if the final equity remains intact. The issue is no longer the lost PageRank, but the time it takes for Googlebot to traverse the chain and consolidate signals.

Another limitation: this rule applies in a stable context. If you redirect URL A to B, then change B to C a month later, and then C to D six months after that, Google may eventually consider your site lacks editorial consistency. This is not an algorithmic penalty; it’s a gradual loss of trust in the stability of your content. [To be verified]: Google has never published a precise threshold for 'too many successive redirects', but field feedback suggests that beyond 3-4 hops, consolidation slows down.

In which cases does this rule not apply?

Inter-domain redirects (from domain A to domain B) work differently. Google follows the redirect, but it also assesses whether the two sites share the same owner, the same theme, or if the operation resembles an attempt at manipulating PageRank. A network of sites that bounce links back and forth via 301 won’t benefit from any equity transfer; quite the opposite.

Conditional redirects (for example, a 301 served only to Googlebot while users see a 200) are detected and can trigger a manual action. Transparency remains key: if you redirect for bots, do it for humans, too.

What should you do concretely during a site migration?

Map all URLs that receive significant traffic or backlinks. Use Search Console, Ahrefs, or Majestic to list pages that have incoming links. Each source URL should point to a thematically close destination, not to a catch-all page. If your old 'iPhone 12' page redirects to 'Apple Smartphones', that’s acceptable; if it redirects to home, you’re wasting equity.

Test your redirects before the switch. A crawl with Screaming Frog or OnCrawl can help detect loops, unnecessary chains, or 302s that should have been 301s. On the big day, check that each redirect returns a clean HTTP 301 code, with no excessive latency. A response time over 500 ms on a redirect hinders Googlebot and can delay the consolidation of signals by several weeks.

What mistakes should absolutely be avoided during and after migration?

Never redirect in bulk to home or a handful of 'safe' pages. Google interprets this practice as content abandonment and will not transfer any authority. It’s better to return a 410 (Gone) on truly obsolete pages and reserve 301s for content that has a legitimate equivalent.

Avoid touching redirects for several months after the migration. Each modification restarts the crawling and consolidation process. If you need to correct a wrongly pointed redirect, do it quickly, but then let the system stabilize. Google needs consistency to understand your new URLs are permanent.

How can you check that the link power has been properly transferred?

Three weeks after the migration, compare positions on your strategic keywords. A drop of over 20% in overall organic traffic signals a problem: redirect chains, 302 instead of 301, or irrelevant destinations. Use Search Console to monitor crawl errors and de-indexed pages. If Google continues to reference your old URLs instead of the new ones, your redirects are not being correctly detected.

Also, check the re-indexing speed of the new URLs via the URL inspection tool. If Googlebot takes more than a month to crawl your redirected pages, you likely have issues with crawl budget or server performance. In this case, optimize response time, reduce redirect chains, and submit an updated XML sitemap to accelerate discovery.

• Map all URLs with backlinks or significant traffic before migration.
• Check that each redirect returns a HTTP 301, not a 302 or a meta-refresh.
• Test redirects with Screaming Frog to detect loops and unnecessary chains.
• Avoid massive redirects to home: each old page should point to a thematic equivalent.
• Monitor the Search Console for 3 months to catch crawl errors and de-indexed pages.
• Do not modify redirects for several weeks after the switch to allow Google to consolidate signals.