Does a 302 redirect really dilute PageRank?

What does this statement change compared to the old doctrine?

For a long time, standard SEO doctrine stated that only 301 redirects fully passed PageRank, while 302s were seen as temporary solutions that diluted juice. This distinction was based on simple logic: a 301 signals a permanent move, so Google consolidates signals on the new URL.

Mueller clarifies here that this view is outdated. 302s maintain PageRank on either the destination or source URL, depending on the context. The real impact of a 302 is not about the juice transmission, but indexing: Google always indexes the final visible content, not the interim URL.

Why does Google impose indexing of the final content?

Google's logic centers on user experience. A 302 indicates that the source URL might revert to its initial state, but during the redirect period, users land on the destination. Therefore, Google prioritizes indexing what users actually see, not the technical URL that serves as a stepping stone.

This rule also prevents abuse. If Google were to systematically index the source URL of a 302, malicious actors could manipulate the SERPs by creating temporary redirects to third-party content while keeping their own URL visible. Indexing the final content imposes consistency between what appears in the results and what the user views.

What does it mean to “maintain PageRank on the destination or the source URL”?

This vague phrasing deserves attention. Mueller suggests that PageRank can remain attached either to the source URL or to the destination, depending on the duration of the redirect and the contextual signals. In practice, if a 302 lasts for several months, Google will eventually consolidate the signals on the destination, similar to a 301.

Conversely, if the 302 is short and the source URL becomes active again quickly, PageRank may remain anchored on the source. This flexibility explains why Google now treats 301 and 302 as virtually equivalent in terms of juice transmission, but maintains a strict distinction on indexing.

• 302s pass PageRank as effectively as 301s, contrary to previous beliefs.
• The indexing of final content is systematic: Google indexes what the user sees, not the technical source URL.
• PageRank can stay on the source or migrate to the destination, depending on the duration of the redirect and the contextual signals observed by Google.
• 302s are not “temporary degraded solutions”: they are neutral for PageRank but restrictive for indexing.
• This rule prevents manipulations: you cannot display a URL in SERPs while redirecting to different content for an extended period.

Is this statement consistent with field observations?

Yes, largely. For several years, practitioners have noticed that 302s no longer cause significant ranking loss compared to 301s. A/B tests show that switching a 301 to a 302 (or vice versa) does not lead to a drastic drop in positions, as long as the redirect remains stable.

The nuance lies elsewhere: in indexing. If your goal is to maintain the source URL in the SERPs while temporarily redirecting traffic, a 302 will fail. Google will index the destination, and your original URL will gradually disappear from the results. This behavior is consistent with what Mueller describes but contradicts a common practice where some SEOs use 302s thinking they are keeping the source URL visible.

In what situations does this rule create practical conflicts?

The main trap concerns geolocation or contextual redirects. Imagine an e-commerce site that redirects users to regional subdomains via 302. If Google systematically indexes final destinations (fr.example.com, de.example.com), your main domain (example.com) loses visibility in international SERPs.

Another problematic scenario involves A/B or promotional redirects. You want to test a temporary landing page by redirecting 50% of the traffic via a 302, while keeping the main URL indexed. Result: Google indexes the test version, and your main URL loses its position. [To be verified]: Mueller does not clarify how Google arbitrates when multiple 302s coexist on the same source URL.

What nuances should be added regarding the “retained PageRank”?

Mueller's phrasing remains intentionally vague. “Maintaining PageRank on the destination URL or the source URL” suggests that Google decides on a case-by-case basis, without transparent criteria. In practice, if a 302 lasts over 6 months, Google treats it like a 301 and consolidates PageRank on the destination.

But this duration is never officially communicated. Field observations show variations: some 302s are treated as 301s after 3 months, others after a year. [To be verified]: no official data quantifies this threshold. If you rely on a 302 to preserve PageRank on the source URL beyond a few weeks, you are playing with fire.

What should you do if you are already using 302 redirects?

Start by auditing all your active 302s. Identify those in place for more than 3 months: they are likely treated as 301s by Google, with indexing of the destination. If your goal was to keep the source URL visible, you've already lost that battle. Convert these 302s to 301s to clarify your intention and avoid future confusion.

For genuinely temporary 302s (promotions, tests, maintenance), ensure that the destination URL corresponds well to the content you want indexed. If you are temporarily redirecting to a “Under Construction” page or a test landing page, know that Google will index this version, not the original. Plan a quick return strategy to the source URL to limit contamination of the SERPs.

What critical errors should be avoided with 302s?

Classic mistake: using a 302 to permanently move a page while thinking of “keeping a door open.” If your move exceeds a few weeks, Google will treat your 302 as a 301 in practice. It's better to use a 301 from the start and gain clarity of signal. 302s are not “cautious” 301s.

Another trap: geolocation redirects without hreflang annotation. If you redirect via 302 to regional versions, Google will index these versions but without understanding your site's linguistic structure. Result: cannibalization between variants and loss of international visibility. Geolocation 302s must always come with robust hreflang tags.

How can I check if my redirects are being correctly interpreted by Google?

Use Google Search Console to analyze indexed pages. If you see Google systematically indexing the destinations of your 302s while you wanted to keep the source URLs, it's a clear signal that your use of 302s contradicts your strategy. Compare indexed URLs with your stated intentions in robots.txt and sitemaps.

Next, monitor server logs. If Googlebot is heavily crawling the destinations of your 302s but neglecting the source URLs, it means Google has shifted its attention. Also, check the coverage reports in GSC: source URLs marked as “Redirected” confirm that Google has acknowledged the transfer, even if you used a 302.

• Audit all active 302s older than 3 months and consider converting them to 301s if the move is permanent.
• Verify that the destinations of temporary 302s match the content to be indexed, without polluting the SERPs with test pages.
• Accompany any geolocation or multilingual 302 with properly implemented hreflang tags.
• Monitor indexed pages in Google Search Console to detect gaps between intention and reality.
• Analyze server logs to identify source URLs neglected by Googlebot after a prolonged 302.
• Avoid chains of 302 redirects (A → B → C) that complicate the interpretation of PageRank by Google.