What Is a 302 Redirect?
A 302 redirect is an HTTP response status code that instructs browsers and search engines that the requested page has been found at a different URL, temporarily.
In simpler terms, when a user or crawler tries to visit URL A, the server responds with a 302 status and a new location (URL B), signaling: “This page is temporarily at URL B; use that for now.”
Unlike a 301 redirect (which is permanent), a 302 means you intend to bring the original URL (A) back at some point. The browser will automatically forward the user to the new URL, but it’s understood the change isn’t permanent.
When to Use a 302 Redirect
Use a 302 redirect only when the move is truly temporary – i.e., you fully intend to restore the original URL or content. Some common scenarios where 302 is appropriate:
- Testing or Updating Content: If you are revamping a page and during that period you want users to see an alternate page. For example, you’re redesigning page.html so you temporarily 302 redirect it to a “Page Under Maintenance” or a draft version. Once done, you’ll remove the redirect and put page.html back. A 302 tells search engines not to forget the original page because it’s coming back.
- A/B Testing and Experiments: Suppose you want to test a new landing page design on a subset of users. You might 302 redirect 20% of traffic from the original URL to a variant URL (perhaps controlled by an A/B testing tool). This is temporary and for testing; after the test, all traffic goes back to the original or you decide to permanently move. During the test, a 302 ensures Google doesn’t transfer SEO weight to the test URL (which might be discarded later).
- Short-Term Marketing or Promotion: If you have a short-lived campaign or event. For instance, you might redirect your homepage to a “Black Friday Sale” page for one weekend. That should be a 302, since after the sale you’ll revert the homepage back. Similarly, if a product is temporarily out of stock, you could 302 redirect its page to a category page or an “back soon” page, intending to switch back when restocked (though some might simply leave it up with a note – strategy varies).
- Maintenance or Downtime: If a section of your site is down for maintenance, you might 302 those pages to a maintenance notice page. For example, /user-dashboard could 302 to /maintenance.html while you upgrade the system. This way users get a friendly message, and search engines know the original page isn’t gone forever.
How Search Engines Treat 302 Redirects
Historically, search engines interpret a 302 like this: “The redirect is temporary, so keep the original URL indexed, and do not transfer the ranking signals to the new URL (since the original will return).”
Indexing behavior
Google will typically continue to index the original URL A when it sees a 302 redirect to B.
It might note that A currently redirects to B, but in the search results Google often still shows URL A (especially if the redirect is recent or intermittent). This is because the 302 tells Google that URL B is not the permanent location.
The original URL remains canonical in Google’s view. Only if the 302 persists for a long time might Google eventually treat it like a 301 and swap them. Bing and others similarly keep the old URL.
Link Equity and Ranking
With a 301, as mentioned, the “link juice” flows to the new URL. With a 302, traditionally, link equity does NOT pass to the target (at least not immediately).
The backlinks and authority remain attached to the original URL. As a result, the target URL (B) might not rank well if it doesn’t have its own independent signals.
Google’s John Mueller explained that effectively their system uses canonicalization: in a 302, they often treat the source as the preferred URL (canonical) and the destination as alternate.
Over time, if all signals (links, internal links, sitemaps, etc.) point to the new URL, Google may treat it as permanent anyway. But initially, assume no PageRank transfer.
Pitfalls of misuse
If one mistakenly uses a 302 when the change is permanent, the new page may not rank well. Google won’t transfer SEO value, so the new page B is essentially starting from scratch or getting partial credit at best.
The original page A might still be considered the main one, but it’s redirecting – a confusing state that can hurt visibility.
On the other hand, using a 301 for a temporary change can cause Google to drop the original page, and when you remove the redirect, the original might have lost its standing.
That’s why it’s important to choose correctly.
Best Practices for 302 Redirects
1. Choose the Right Redirect Based on Your Intent
This is where most people slip up. Google recommends using a 301 redirect when the move is permanent and a 302 redirect when it’s temporary.
Sounds simple, but many still use the wrong one out of habit. If you’re permanently changing a URL or migrating a site, go with 301. It passes SEO signals like PageRank and helps Google understand this new page should replace the old one.
If it’s a temporary redirect, like during A/B testing or maintenance, 302 is the safer choice. That way, Google keeps the original page in the index, assuming it’ll return. Using the wrong one could confuse search engines and harm your rankings, so always match the redirect to your actual intent.
2. Keep 301 Redirects Live for at Least a Year
Let’s say you’ve permanently redirected a page using a 301. Don’t yank it down a month later. Google’s John Mueller recommends keeping 301s in place for at least a year. That gives search engines and users (think bookmarks, links, cached results) enough time to adjust.
Remove the redirect too soon, and people may land on broken pages. While this tip is aimed at 301s, it’s also a reminder to stay committed. If your 302 ends up being permanent, switch it to a 301 instead of leaving it in limbo.
3. You Don’t Lose PageRank on Redirects—If Done Right
This is a big one. For years, SEOs feared that 302s would tank PageRank. But Google has clarified that no PageRank is lost through 3xx redirects, including 302s.
That’s a relief, but there’s a caveat: Google needs to interpret the redirect as legitimate. If you're using a 302 when you should be using a 301, Google might still treat it like a temporary move and not consolidate signals.
The bottom line? Don’t stress about link equity loss if you’re using redirects correctly, but also don’t abuse them. Use the right type and let Google do the rest.
4. Use Server-Side Redirects Whenever Possible
Google’s official docs make this clear: server-side redirects are the best option. That means setting up redirects via .htaccess, your server config, or backend logic.
These are clean, fast, and clear to crawlers. Avoid using JavaScript or meta refresh redirects if you can help it. They’re client-side, which means they load slower and are a bit messier for search engines to process.
Even though a meta refresh with “0 seconds” is often treated like a 302, it’s not ideal. If SEO matters to you, stick with server-side.
5. Follow Proper Redirect Practices for Site Moves
If you’re moving to a new domain or consolidating URLs, you’ll want to get this right. Google offers a Change of Address tool in Google Search Console, but that doesn’t replace setting up proper 301 redirects from old URLs to new ones.
You still need to guide Google through the transition with clear signals. For partial moves or temporary content switches, communication is key. If you’re doing scheduled downtime, consider using a 503 status with a Retry-After header instead of a 302.
That way, Google knows it’s temporary and won’t index a maintenance page by mistake. Save 302s for when you’re actually showing alternative content, not just blocking access.
Frequently Asked Questions
What’s the difference between a 301 and 302 redirect?
A 301 redirect is for permanent changes, while a 302 is meant for temporary ones. Google recommends using 301 when you’re permanently moving content, as it passes SEO signals like PageRank to the new URL. A 302 tells Google the original page might come back soon, so it keeps the original URL in the index to preserve its rankings.
Can using the wrong type of redirect hurt SEO?
Yes. If you use a 302 for something that’s actually permanent, Google might not transfer rankings or link equity properly. This could lead to unpredictable indexing behavior or loss of visibility. Google explicitly advises using the redirect type that matches your true intent—301 for permanent, 302 for temporary—to avoid SEO issues.
How long should I keep a 301 redirect in place?
John Mueller from Google recommends keeping 301 redirects up for at least one year. That gives search engines and users enough time to adjust to the new URL. If you remove it too soon, users with old bookmarks or websites linking to the original page may end up hitting errors or being cut off from your updated content.
Do redirects still pass PageRank?
Yes. Google has confirmed that 3xx redirects—including 302s—do not dilute PageRank. This is a shift from earlier beliefs. If you’re using redirects correctly and they align with Google’s understanding of the situation, link equity should flow normally. Still, it’s best not to overuse or misuse 302s. Google may treat them differently depending on context.
Why are server-side redirects better than JavaScript or meta refresh?
Server-side redirects (set up via .htaccess, backend logic, or server config) are more reliable and faster for both users and search engines. Google recommends avoiding meta refreshes or JavaScript-based redirects when SEO is a priority. While a “0 second” meta refresh can act like a 302, it’s not as clean or efficient.
What’s the best way to handle domain changes or site moves?
For full domain moves, use 301 redirects and submit a Change of Address request in Google Search Console. For temporary URL changes or offline sections, you can use a 302 or even a 503 with a Retry-After header if you want to pause crawling. Be clear about your intent, and avoid mixing redirect types for the same content.
How many redirect hops are too many?
Googlebot may stop following after 4 or 5 redirects in a row. If you have long redirect chains, simplify them. Too many hops slow down page loads and can confuse crawlers. From an SEO and UX standpoint, direct and minimal redirects are always best. If possible, point to the final destination right away.
