Do 301 redirects really transfer 100% of PageRank and SEO signals?

What does "all signals" really mean in this statement?

When Google talks about transferring all signals, it refers to PageRank, accumulated authority, link anchors, and ranking history. The wording implies that a properly implemented 301 redirect acts as a simple address change: the new URL inherits everything the old one built up.

Mueller even clarifies that UTM or other parameterized links follow suit. If a URL like example.com/old?utm_source=newsletter redirects to example.com/new, Google consolidates these signals at the new destination. This is crucial for sites that track their campaigns through parameters.

Does this statement contradict previous recommendations about "PageRank loss"?

For years, SEO doctrine stated that a 301 redirect resulted in a slight loss of PageRank—between 10% and 15% according to estimates. This theory stemmed from old statements by Matt Cutts and empirical observations.

Mueller brushes aside this belief. According to him, no loss is to be expected if the redirect is correctly set up. This change in narrative likely reflects an evolution in the algorithm: Google may have refined its handling of redirects to avoid penalizing legitimate migrations.

Why is Google emphasizing this point now?

This clarification comes at a time when site migrations and technical overhauls are multiplying. Modern CMS platforms, transitions to HTTPS, domain changes: all scenarios where redirects become critical.

By asserting that the transfer is complete, Google is likely trying to reassure webmasters who hesitate to migrate for fear of losing their rankings. It’s also a way of saying: "Do it correctly, and you have nothing to lose."

• Complete transfer: PageRank, authority, link anchors, ranking history
• UTM parameters: Tracked links are also consolidated at the new URL
• No theoretical loss: Contradicts old estimates of 10-15% loss
• Sine qua non condition: The redirect must be technically flawless (301, not 302 or meta refresh)
• Consolidation time: Google must recrawl the old URLs and discover the new ones, which takes time

Is this statement consistent with real-world observations?

Let’s be honest: many SEOs report temporary drops after a migration, even with impeccable 301 redirects. If the transfer were truly 100%, these declines should not exist. Several hypotheses: either Google consolidates signals gradually (and the drop is temporary), or other factors come into play (structure change, loading speed, modified content).

It’s also possible that Mueller refers to a theoretical final state once Google has completely digested the migration. The issue is the timeline: between the moment you redirect and when Google has recrawled all your old URLs, weeks can pass. During this time, your rankings may fluctuate. [To be verified]: no Google study has published a precise timeline on consolidation speed.

In which scenarios could this rule not fully apply?

If you redirect to a thematically distant page, Google may determine that the continuity doesn’t make sense. For example: redirecting /running-shoes to /kitchen-accessories makes no sense. Google might treat this redirect as a soft-404 and not transfer the signals.

Another problematic case is redirect chains. If URL A redirects to B, which redirects to C, Google may follow the chain… or decide it’s too costly in crawl budget and abandon it. The recommendation has remained the same for years: always redirect directly to the final destination.

What does this statement say about 302 redirects and meta refresh?

Mueller only talks about 301 (permanent) redirects. 302 (temporary) redirects are not designed to transfer PageRank permanently, as they indicate to Google that the old URL will return soon. Meta refresh and JavaScript redirects are even murkier: Google may follow them, but there’s no guarantee of a complete transfer of signals.

If you are permanently migrating a URL, there’s no reason to use a 302. This is a classic mistake that is still seen too often in audits. Yet, some CMS or CDN still default to serving 302. Check your HTTP headers with a tool like Screaming Frog or cURL.

What should you do during a site migration?

First, map all your URLs: old to new, one by one. No generic redirection to the homepage. Each old URL must point to its closest thematic equivalent. If a page disappears without an equivalent, a 410 (Gone) is more honest than a forced redirect to unrelated content.

Next, test your redirects before going live. A staging environment with active redirects allows you to check that each URL returns the correct HTTP code (301, not 302 or 200). Use a crawler to simulate how Googlebot behaves and spot redirect chains or infinite loops.

How to monitor signal transfer after migration?

The Search Console becomes your main dashboard. Monitor impressions and clicks on the new URLs: if they gradually rise while the old ones fall, that’s a good sign. If both stagnate or drop, there’s a problem (broken redirects, new pages not indexable, degraded content).

Also check backlinks in third-party tools (Ahrefs, Majestic). Google follows redirects, but third-party tools may take time to update their databases. If a backlink still points to the old redirected URL, that’s normal—as long as the redirect is in place, the SEO juice passes through.

What mistakes should you absolutely avoid?

Never remove redirects too early. Some webmasters remove 301s after a few months, thinking Google has “figured it out.” Mistake: as long as there are backlinks to the old URL, the redirect must remain. Ideally, keep them in place for several years, or indefinitely if server costs are negligible.

Another trap: redirecting all old URLs to the homepage. Google detects this pattern as a soft-404 and may ignore these redirects. If you’ve truly removed hundreds of pages without an equivalent, it’s better to return 410s than to pollute your homepage with diluted SEO juice.

• Map each old URL to its thematically coherent new destination
• Test all redirects in staging with a crawler (Screaming Frog, Sitebulb)
• Ensure that HTTP codes are indeed 301, not 302 or meta refresh
• Eliminate redirect chains: always point to the final destination
• Monitor Search Console (impressions, clicks) and backlink tools for 3-6 months post-migration
• Keep redirects in place for several years at minimum, as long as backlinks exist