Do 302 redirects really pass PageRank like 301 redirects?

What makes this statement a game changer?

For years, SEO doctrine has hammered that a 301 redirect was the only surefire way to transfer PageRank during a migration. 302 redirects were deemed temporary solutions that did not transfer signals—or only partially.

Mueller breaks this dogma: Google now treats both types of redirects almost identically for passing SEO signals. The engine analyzes the context and decides which URL to index, but the flow of PageRank and authority passes in both cases.

So what’s the difference between 301 and 302?

The distinction lies in the signal of intent sent to Google. A 301 indicates a permanent relocation: Google will consolidate signals on the target URL and deindex the old one. A 302 signals a temporary move: Google may choose to keep the source URL indexed.

Specifically, if you redirect example.com/a to example.com/b using a 302, Google might still show example.com/a in results even though the user lands on /b. With a 301, it’s example.com/b that appears in the SERP. This nuance matters when managing seasonal campaigns or A/B tests.

Do all 302 redirects really pass link juice?

Mueller claims yes, but the reality is nuanced. Google bases its decision on the observed duration of the redirect: a 302 maintained for several months will be treated as a 301 in practice. The engine is not fooled.

Conversely, a 302 that changes targets every week—a classic case of rotating promotions—won’t allow Google to consolidate the signals effectively. While PageRank circulates, it dilutes among the different successive targets without ever accumulating.

• Both 301 and 302 pass PageRank and other ranking signals similarly
• The main difference lies in the choice of the canonical URL displayed in search results
• Google analyzes the duration and context to determine if a 302 should be treated as permanent
• Temporary redirects that frequently change targets dilute signals instead of concentrating them
• The type of redirect sends a signal of intent that Google considers for indexing

Is this statement consistent with real-world observations?

Yes and no. Tests conducted by various SEOs over the last few years do show that long-term 302 redirects eventually pass PageRank. However, the total equivalence claimed by Mueller deserves nuance—it simplifies a mechanism that remains contextual.

Google has likely refined its algorithms to better interpret the intent behind each redirect. But claiming that a 302 that lasts for three days and a definitive 301 produce the same effect is more about corporate communication than actual mechanics. [To be verified]: The exact timeframes for signal consolidation with a 302 are not documented.

In what cases does this rule not fully apply?

Redirect chains remain problematic regardless of the HTTP code used. A sequence A → B → C → D fragments the transfer of PageRank even if each link is a perfect 301. Add 302s into the mix, and you multiply friction points.

Conditional redirects—based on language, device, geolocation—also complicate the equation. Google has to crawl multiple variants to understand the structure, and signals scatter between the alternative URLs. A 302 to /mobile from /desktop does not pass link juice like a classic migration.

Should you then always use 302 redirects?

No. Let’s be honest: using a 301 for a definitive migration remains the undisputed best practice. Why? Because it sends an unmistakable signal to Google and speeds up signal consolidation.

302 redirects still hold their utility for specific cases: temporary A/B tests, seasonal redirects, scheduled maintenance. But generalizing their use on the premise that they "pass juice" introduces unnecessary complexity into your architecture. And that’s where it gets tricky: Google can take weeks to decide that a 302 should be treated as permanent.

What should you do during a migration?

Always prioritize 301 redirects for any permanent URL change—domain migration, site restructuring, content merging. It’s the clearest signal to Google and the quickest to process.

Reserve 302 redirects for documented temporary cases: a page under maintenance that will revert to its original URL, a seasonal campaign lasting a few weeks, a controlled A/B test. And even in these cases, monitor the duration: beyond 3-4 months, switch to 301.

How do you check if your redirects are passing signals correctly?

Use Search Console to monitor the indexing of target URLs. If you’ve redirected A to B using a 301 but Google continues to index A several weeks later, you have a problem—likely a conflicting canonical or internal links still pointing to A.

Audit your redirect chains with Screaming Frog or an equivalent tool. Each additional link slows down PageRank transfer. The ideal scenario is a direct redirect from the source to the final destination, with no intermediate steps.

What mistakes should you absolutely avoid?

Do not mix 301s and 302s within the same migration. You create confusion for Googlebot that doesn’t know what intent you are pursuing. If you’re launching a redesign, all old URLs should redirect with 301 to their new counterparts.

Avoid default redirects to the homepage. A deleted product page should redirect to the closest category or an equivalent product, never to the homepage—you would lose thematic relevance and PageRank would dissolve into the mass.

• Use 301 for any permanent URL or domain migration
• Limit 302 redirects to documented temporary cases under 3 months
• Eliminate redirect chains—aim for a single jump from the old URL to the new one
• Check in Search Console that Google is indexing target URLs, not redirected sources
• Regularly audit your redirects with a crawler to detect loops and 404 errors
• Never redirect by default to the homepage—prioritize thematic relevance