Do 302 redirects really transfer PageRank like 301s?

Why has the 301 vs 302 distinction always obsessed SEOs?

For years, the official doctrine was clear: a 301 transfers PageRank, a 302 does not. This technical difference explained why everyone kept saying 'always use 301s for migrations'.

The logic behind this? A 301 signals a permanent change, allowing Google to consolidate signals from the old URL to the new one. A 302, meant to be temporary, didn’t justify this transfer in the eyes of the algorithm.

What does Google actually say in this statement?

The nuance is crucial: Google 'understands the URL change' even with a 302, and 'tends to maintain rankings' for the relevant queries. In other words, the algorithm no longer just blindly applies the HTTP specs.

The engine analyzes the context, the duration of the redirect, and user signals. If a 302 remains active for months, Google ends up treating it almost like a 301. It's no longer binary.

In what cases does this flexibility apply?

Google refers to 'relevant queries', a deliberately vague term. We can assume that if the destination URL matches the content expected by the user, the ranking is maintained.

Conversely, a 302 pointing to an off-topic page risks losing its positions. Semantic relevance likely plays as much of a role as the HTTP code itself.

• 301s are still recommended for definitive moves — Google explicitly repeats this
• 302s no longer systematically block PageRank, contrary to historical dogma
• The duration of the redirect likely influences Google's behavior towards a 302
• The relevance of the destination conditions ranking maintenance, regardless of the code used
• The choice of code should reflect actual intent, not artificial SEO optimization

Is this statement consistent with field observations?

Yes, but with a time lag. Tests conducted by SEOs for several years showed that 302s no longer devastated rankings like they did in the 2010s. Google simply took time to formalize what the algorithm was already doing.

The issue is that this flexibility creates uncertainty. How long does a 302 take to be treated like a 301? Google doesn’t say. The phrase 'tends to maintain' remains deliberately vague. [To verify]: no specific timeframe is provided.

Should we still be concerned about choosing between 301 and 302?

Absolutely. This statement doesn’t mean the two codes are interchangeable. A 301 remains the clearest and fastest signal to consolidate PageRank during a migration.

Using a 302 by mistake for a permanent move lets Google guess your intent. Why take that risk when the right HTTP practice exists? The flexibility of the algorithm does not justify technical negligence.

What risks remain with 302 redirects?

The main danger is the temporal dilution of the signal. Even if Google eventually understands, the initial weeks can exhibit unstable positions and visibility fluctuations. Unacceptable in a competitive context.

Another point: third-party tools (Ahrefs, SEMrush, Screaming Frog) continue to flag 302s as potential errors. If you audit a site and find 200 'temporary' 302 redirects from three years ago, it's technically unsound even if Google can accommodate it.

What should you practically do during a migration?

Always use 301s for all permanent moves. This statement does not change this basic rule. The 301 remains the optimal, fastest, and cleanest choice.

Reserve 302s for cases where you really need a temporary redirect: scheduled maintenance, short A/B test, occasional geo-targeted redirect. If you can't define a specific end date, it's probably a 301.

How do you audit existing redirects on your site?

Crawl the entire site with a technical tool (Screaming Frog, Oncrawl, Botify). Identify all active 302 redirects older than 30 days. These are priority candidates for conversion to 301.

Also check redirection chains: a 302 followed by a 301 creates unnecessary signal loss. Each additional jump increases the risk of PageRank loss, even if Google is more lenient than before.

What mistakes should you absolutely avoid?

Don’t mix codes out of negligence. I've seen sites with 50% 301s and 50% 302s on the same migration, simply because the provider didn’t standardize the server rules. Google may manage it, but technically it's just patchwork.

Another trap: using a 302 'while finalizing the destination'. If you don’t yet know where to point, keep the old URL active instead of creating a faulty redirect that will change in two weeks.

• Convert all 302s older than 30 days to 301 if the move is permanent
• Eliminate redirection chains (302 → 301, 301 → 301, etc.) to limit loss
• Ensure that remaining 302s have documented technical justification
• Test returned HTTP codes using curl or a crawler to detect server configuration errors
• Monitor positions in the 4 weeks following a migration, even with clean 301s
• Update internal links to point directly to the new URLs without going through redirects