Do 302 redirects really pass PageRank?

Why does this statement disrupt certain established practices?

For years, SEO dogma was clear: a 302 redirect dilutes PageRank, while a 301 preserves it completely. This distinction was based on the idea that a temporary redirect signals to Google that it should continue indexing the source URL.

Mueller is here to set the record straight. 302s typically pass PageRank to the target, just like 301s. The real issue is not a loss of juice but ambiguity in intent: Google does not know which version to prioritize for indexing if you use a 302 for a permanent migration.

What truly differentiates a 302 from a 301?

The difference is not so much technical as it is semantic. A 301 clearly tells Google that the source URL is dead and that it should transfer all signals to the target. Indexing gradually shifts.

With a 302, Google considers that the original URL remains valid and can come back at any moment. Therefore, it keeps the source URL in its index while following the redirect for the user. PageRank flows, but the canonical URL remains unclear. It is precisely this uncertainty that poses a problem in production.

What role does rel='alternate' play in this equation?

Mueller emphasizes the use of rel='alternate' to establish equivalence between language versions. It is a distinct signal from the redirect itself. When you have a French version and an English version of the same page, rel='alternate' tells Google that it is not duplication but legitimate variations.

Without this marker, Google may interpret the language versions as competing content, even with geolocated redirects in place. Rel='alternate' clarifies editorial intent and prevents your pages from cannibalizing each other in the SERPs.

• 302 redirects do pass PageRank to the target version, contrary to popular belief
• The correct use of a 302 is only for verifiable temporary situations (maintenance, A/B testing, seasonality)
• Rel='alternate' remains mandatory for managing language equivalence, regardless of redirect type
• The real risk of a poorly placed 302 is indexing ambiguity, not PageRank loss

Is this statement consistent with field observations?

Yes and no. In observed migrations between 2018 and today, sites that switched using 302s instead of 301s often temporarily lost traffic. However, this loss can be explained more by chaotic indexing than by pure dilution of PageRank.

Google has likely unified how PageRank is treated between 301s and 302s for several years. The issue is that crawlers do not know which URL to display in search results as long as the redirect is marked as temporary. Rankings can fluctuate violently during this period of uncertainty, giving the impression of a loss of juice. [To be verified]: no official data specifies exactly when Google started treating 302s like 301s in terms of PageRank.

When does this rule not fully apply?

If you stack multiple redirects in a chain (A → B → C), the passage of PageRank can be degraded regardless of the HTTP code used. Google typically follows a maximum of 5 hops, but each additional link dilutes signals.

Another case: geolocated redirects based on IP. Google usually crawls from the United States. If your 302 redirects French visitors to /fr/ but leaves Americans on /en/, Googlebot will never see the French version through the redirect. Rel='alternate' with hreflang then becomes critical, not optional.

What nuances should be added to this statement?

Mueller says 'typically', and this word matters. It implies that in certain contexts, behavior may vary. A/B tests with 302 redirects can trigger conflicting signals if Google detects cloaking. The PageRank may pass, but the site risks a manual action.

Additionally, processing speed differs. A 301 is generally consolidated in the index within a few weeks. A 302 may remain in a state of ambiguity for months if Google expects the redirect to be lifted. Technically, PageRank flows, but strategically, it is a nightmare.

What should be done concretely on a live website?

Auditing all existing 302 redirects is the first step. If they have been in place for more than three months, they are probably no longer temporary. Switch them to 301s to clarify intent and accelerate consolidation in the index.

For language versions, systematically implement rel='alternate' with hreflang in the head of each page. Do not rely solely on geolocated redirects: Google needs both signals to properly manage international variants. Test your tags with Search Console to ensure they are correctly detected.

What mistakes should be absolutely avoided?

Never use a 302 for a domain migration or structural redesign. Even if PageRank passes, indexing will remain shaky for months. You will lose traffic not from dilution but from position volatility.

Also avoid mixing 302s with contradictory canonicals. If your page A redirects in 302 to B, but B contains a canonical pointing to C, Google will not know which version to index. PageRank may flow, but your visibility will be sacrificed to technical inconsistency.

How can I check that my site respects these recommendations?

Use Screaming Frog or an equivalent tool to list all redirects and identify their age. Cross-reference this data with your server logs: a 302 that has been crawled for six months should be a 301.

On the international side, validate your hreflang tags with dedicated tools (Merkle, Aleyda Solis, or Search Console). An error in hreflang syntax completely nullifies the benefit of rel='alternate', even if your redirects are perfect. Complex multilingual configurations often require specialized support to avoid recurring technical pitfalls. An experienced SEO agency can audit your international architecture and correct inconsistencies before they impact your rankings.

• Convert all permanent 302s (> 3 months) to 301s
• Implement rel='alternate' with hreflang on all language versions
• Eliminate redirect chains (maximum 1 hop)
• Check consistency between redirects and canonicals
• Test hreflang tags in Search Console
• Monitor the indexing of international variants in coverage reports