Why doesn't a 301 redirect always transfer 100% of PageRank to the new URL?

What does it really mean to “transfer SEO signals” in the context of a redirect?

When Google speaks of transferring SEO signals, it refers to all the ranking criteria accumulated by a URL over time. PageRank is the most well-known example, but there are also thematic authority, inbound link anchors, content history, and even user signals associated with that page.

A permanent redirect (301 or 308 in HTTP/2) tells Google that the resource has permanently moved. The engine must then consolidate the signals from the old URL to the new one. This isn’t a simple alias: it’s a migration of digital identity that takes time and is never instantaneous.

Do all redirects transfer PageRank in the same way?

No. A 302 redirect (temporary) is not supposed to transfer signals in the same way as a 301, even though Google has stated in the past that it treats both similarly in certain contexts. But in reality, a 302 that is maintained over several months often leads to unpredictable behaviors: the old URL may stay indexed, and the new one can take weeks to regain visibility.

Chain redirects (A→B→C) dilute the transfer. Each hop introduces a consolidation delay and potentially a marginal loss of signal. Google has always recommended pointing directly to the final destination, but in practice, many sites accumulate chains of 3-4 redirects without realizing it, especially after several successive migrations.

How long does it take for the transfer to be effective?

Google never gives a precise timeline, and that’s where the problem begins. On sites with a high crawl budget, redirects can be consolidated in a few days. On less crawled sites, it can take several weeks, or even months for deep pages.

During this transition period, you can observe position fluctuations, a hybrid indexing (both old and new URLs present simultaneously), and a temporary dilution of traffic. That’s why a site migration requires daily monitoring of crawl metrics and positioning for at least 60 days.

• 301 redirects transfer PageRank, but not instantaneously or necessarily at 100%
• The type of redirect matters: 301/308 for permanent, never prolonged 302
• Chain redirects dilute signals and slow down consolidation
• Crawl budget determines the speed of consideration by Google
• The transition period generates fluctuations that must be anticipated and monitored

Is this statement consistent with real-world observations?

Yes and no. The theory is validated: well-implemented redirects do allow for migrating a site without catastrophic loss of visibility. But Google intentionally simplifies the message. In reality, the exact transfer rate of PageRank via a redirect has never been officially confirmed. Some tests suggest that it is not exactly 100%, even though Google has claimed otherwise for several years.

On the ground, we regularly observe organic traffic losses of 10 to 30% after a migration, even with perfectly configured redirects. These losses are not always due to the redirect itself: often, it's the change in content structure, internal linking modifications, or variations in user signals that explain the drop. But isolating the exact cause remains an analytical challenge.

What nuances is Google intentionally omitting in this statement?

First, the context of the redirect plays a huge role. Redirecting page A to page B with strictly identical content is ideal. But redirecting 50 old product pages to a single category page is a consolidation that will dilute signals and often lead to a drop in positions. Google never publicly distinguishes this.

Also, the thematic relevance between the old and new URL is never mentioned. If you redirect a page about “running shoes” to a page about “sports clothing,” Google will detect a semantic break and will likely not transfer the signals as effectively. [To be checked] because Google never documents these edge cases, but A/B tests show inconsistent behaviors.

In which cases does this rule not fully apply?

Mass redirects (thousands in a few days) can trigger alerts at Google and significantly slow down the consolidation process. The engine may interpret this as a suspicious overhaul and monitor the URLs for several weeks, just to ensure that it’s not an attempt at manipulation.

Punished sites are another edge case. If a URL has been hit by a manual action or an algorithmic penalty, redirecting to a new URL does not magically transfer authority by making the penalty disappear. Google has confirmed that penalties can follow redirects in certain contexts, particularly for artificial link schemes.

What should you concretely do before migrating URLs?

First, map out all the URLs to redirect by pulling a full crawl of your site using Screaming Frog or Oncrawl. Cross-reference this list with your Google Search Console data to identify the pages that actually generate organic traffic and deserve individual redirects rather than massive consolidation.

Define a 1:1 mapping strategy as precisely as possible. Each old URL must point to the most semantically relevant new URL. If you do not have a direct equivalent, create content on the new URL before redirecting, or accept to lose that page by sending a 410 instead of a forced redirect to an off-topic page.

How can you check that the redirects are working properly after the migration?

Manually test a sample of redirects using a HTTP code checker tool such as Redirect Path or httpstatus.io. Ensure that there are no redirect chains (A→B→C) and that the returned code is a 301 or 308, never a 302 or 307.

Monitor Google Search Console daily: crawl errors, indexed pages (the old URL should gradually disappear from the index), and organic traffic by page. A spike in 404 errors after a migration indicates missing or poorly configured redirects. Also set up alerts in Google Analytics for sudden drops in organic traffic on a per-page basis.

What mistakes should be absolutely avoided during a URL migration?

Never redirect all old URLs to the homepage. This is the worst possible mistake: Google detects the pattern, ignores the redirects, and you lose 100% of the accumulated PageRank. Each redirect should point to equivalent content or at least the closest parent category.

Avoid removing old URLs from the XML sitemap immediately after the migration. Leave them for a few weeks to allow Google to crawl the redirects, then gradually replace them with the new URLs. This speeds up the consideration and avoids situations where Google never discovers the redirect.

• Crawl the entire site and identify all URLs to redirect
• Create a precise mapping file (old → new) manually validated
• Implement 301 or 308 redirects, never 302
• Eliminate any redirect chains by pointing directly to the final destination
• Test a sample of redirects before and after deployment
• Monitor Search Console and Analytics daily for at least 60 days