Do 301 and 302 redirects really transmit the same amount of PageRank?

Why is Google challenging a well-established SEO belief?

For years, the SEO community believed that 301 redirects (permanent) transmitted PageRank better than 302s (temporary). This belief was based on simple logic: a permanent redirect signals a definitive change, so Google should transfer authority.

John Mueller sweeps away this distinction. According to him, the search engine treats these two types of redirects identically regarding PageRank. The temporary/permanent nuance does not influence authority transmission — it only serves to indicate the webmaster's intent.

What actually differentiates a 301 from a 302 for Google?

The difference lies in the treatment of the source URL. A 301 indicates that the old page will not return: Google eventually deindexes it and consolidates signals on the new URL. A 302 suggests that the redirect is provisional: the original URL remains theoretically indexable.

In practice, if a 302 remains active for several months, Google may treat it as a de facto 301. The engine interprets actual behavior rather than strictly adhering to the HTTP code.

Does this statement undermine all SEO best practices?

No. Using a 301 for permanent changes and a 302 for testing or temporary redirects remains the recommended standard. What changes is the anxiety about potential PageRank loss if you accidentally use a 302 during a migration.

Google affirms that SEO juice passes through regardless. The real risk of a 302 misused is confusion in indexation, not a PageRank penalty.

• 301 and 302 redirects transmit PageRank identically according to Google
• The permanent/temporary distinction serves to guide indexation, not to modulate authority
• A 302 that persists for a long time can be interpreted as a 301 by Google
• The choice of redirect type should reflect the webmaster's actual intent

Is this statement consistent with real-world observations?

Yes and no. Many SEO professionals have observed that migrations using 302s instead of 301s ended up losing rankings after a few weeks. But is this due to less effective PageRank transmission, or progressive deindexation of old URLs that creates instability?

My hypothesis: the observed losses mainly stem from indexation problems — Google hesitating between two URLs, retaining the old one in the index when it redirects to the new one. It's not PageRank that's blocking, it's signal consolidation that's dragging on.

What nuances doesn't Google clarify here?

Mueller remains vague about the speed of transmission. Even if a 301 and a 302 theoretically transmit the same PageRank, do they do so at the same pace? A 301 clearly signals that the old page is dead: Google can consolidate signals immediately. With a 302, it might wait to see if the redirect remains in place.

[To be verified] The official documentation provides no figures, no timeframes, no quantifiable data on consolidation. We remain in general discourse.

In what cases might this rule not apply?

Redirect chains complicate everything. Even if Google claims to treat 301 and 302 the same, a chain containing 302s can slow crawling and fragment signals. The longer the chain, the greater the risk of inconsistency.

Another case: cross-domain redirects. Google may be more cautious when a 302 points to an external domain — it might interpret this as temporary hosting or an attempted manipulation. Again, nothing official, but the engine's behavior suggests more nuanced analysis.

What should you concretely do after this statement?

Continue to use 301s for definitive migrations and permanent URL changes. Nothing changes on this front. PageRank transmission is just one criterion among many: the clarity of your architecture and indexation logic matter just as much.

If you have 302s in place by mistake for a long time, don't panic — PageRank passes through. But verify that Google has properly consolidated signals on the correct URL. Check Search Console, Coverage section, to identify duplicate indexed pages.

What mistakes should you avoid now that we know this?

Don't switch everything to 302s under the pretense that it's equivalent. Semantic consistency takes priority: if a page has definitively changed URLs, the HTTP code must reflect this reality. Otherwise, you're sending contradictory signals to Google.

Also avoid creating mixed 301/302 redirect chains. Even if PageRank theoretically passes, each link slows crawling and increases the risk that Google loses track. Prioritize direct redirects to the final destination.

How can you verify that your redirects are correctly interpreted?

Use Search Console to identify old URLs still indexed despite redirects. If redirected pages persist in the index weeks after a migration, it means Google hasn't consolidated.

On the crawl side, analyze your logs: a source URL that continues to be heavily crawled after a 301 signals a problem — outdated internal links, obsolete sitemaps. Fix the source rather than relying on the redirect.

• Use 301s for all definitive URL changes
• Reserve 302s for truly temporary redirects (tests, events, maintenance)
• Audit redirects in place to eliminate unnecessary chains
• Verify in Search Console that old URLs don't remain indexed
• Update all internal links to point directly to new URLs
• Monitor crawl logs after a migration to detect anomalies