302 Redirect
A 302 redirect is a server response that temporarily sends users and crawlers to a different URL while signaling that the original is expected to return. It is meant for temporary moves, not permanent ones.
A 302 redirect tells browsers and crawlers that a URL is temporarily pointing somewhere else, but the original is expected to come back. The request gets forwarded just like a 301, so the user experience is identical, but the message to search engines is completely different. With a 302, the engine keeps the original URL in its index and treats the redirect as something temporary.
That signal is the whole story. Because the move is framed as temporary, search engines generally keep ranking signals associated with the original URL rather than transferring them to the destination. That is exactly what you want for a short-term redirect, and exactly what you do not want when you have actually moved a page for good.
A 302 keeps the original URL as the indexed, canonical version. Use it only when you truly intend to bring that original URL back.
When a 302 is the right call
- Running a short-term promotion or seasonal landing page that swaps back afterward.
- A/B testing where you temporarily route users to a variant URL.
- Sending users to a maintenance page while the real page is briefly down.
- Geo or device routing where the original URL still needs to exist and rank.
- Any situation where the original URL must stay indexed because it is coming back.
How it differs from a 301
| Question | 301 (Permanent) | 302 (Temporary) |
|---|---|---|
| Which URL stays indexed? | The new destination | The original URL |
| Are ranking signals moved? | Yes, to the destination | No, they stay with the original |
| When should you use it? | Permanent moves | Temporary moves only |
| Common misuse cost? | Rarely misused this way | Lost equity on real permanent moves |
# Apache .htaccess, temporary redirect
Redirect 302 /summer-sale/ https://www.yoursite.com/clearance/
# Nginx, temporary redirect
location = /summer-sale/ {
return 302 https://www.yoursite.com/clearance/;
}warningWATCH OUT
The most common 302 mistake is using it for a permanent move. Many platforms and plugins default to 302, so a real migration can quietly ship as temporary redirects. The result is that ranking signals never transfer and the new URLs struggle to take over. Always confirm the status code your redirects actually return.
targetHow to check the status
Open your browser developer tools, go to the Network tab, request the old URL, and read the status code on the first response. It will say 301 or 302 in plain numbers. You can also use any HTTP header checker. Verify, because the intent in your CMS settings is not always what the server sends.
Temporary means temporary
If you are not genuinely going to restore the original URL, you do not want a 302. When in doubt about a move you expect to keep, reach for a 301 so your ranking signals follow the content to its new home.
It is fair to ask whether Google ever just figures it out. To some degree, yes. If you leave a 302 in place for a long time, Google has said it may eventually treat a persistent 302 as if it were a 301, since the behavior looks permanent. But relying on that is a bad bet. You are leaving the decision to the engine, you may bleed ranking value in the meantime, and you have no control over the timeline. Sending the correct status code from the start removes all of that guesswork.
302s have legitimate uses, but they cause real damage when they stand in for a 301 during a move. Knowing exactly which one to use is core migration discipline. For the full redirect strategy, see my site migrations guide.
RELATED TERMS
Want this handled by someone who has measured search for 20 years?
Work with me