A 302 redirect is an HTTP response with status code 302 Found that sends browsers and crawlers from one URL to another while signaling that the move is temporary. In technical SEO, it tells search engines to keep the original URL in the index and to expect it to return, which is the essential difference from a permanent 301 redirect.
Also called a temporary redirect, the 302 is defined in the HTTP semantics specification, RFC 9110. It is the right tool for short-lived situations such as maintenance, A/B tests or seasonal campaigns, and the wrong tool for permanent moves, where it can delay the transfer of ranking signals to the new address.
How a 302 redirect works
A 302 redirect works through a status line and a Location header in the server response. When a client requests the original URL, the server answers with status 302 and the target address, and the client then issues a new request to that target.
Because the redirect is temporary, clients do not cache it by default unless cache headers say otherwise. A browser that returns tomorrow asks the original URL again, which is exactly what makes the 302 suitable for changes that will be reversed.
A historical detail still affects behavior. The original HTTP/1.0 meaning was Moved Temporarily, and browsers began converting a POST request into GET when following a 302. The specification now permits this behavior, so codes 303 and 307 were introduced to make method handling explicit.
| Step | Actor | What happens |
|---|---|---|
| 1. Request | Browser or crawler | Requests the original URL |
| 2. Response | Server | Returns 302 with a Location header |
| 3. Follow-up | Client | Requests the target URL |
| 4. Delivery | Server | Returns the target page, usually 200 |
| 5. Next visit | Client | Requests the original URL again |
How search engines treat a 302 redirect
Search engines treat a 302 redirect as a weak signal for canonicalization. Google normally keeps the source URL indexed and shows it in results, while the content shown to users comes from the target, because the redirect promises that the source will return.
This interpretation is not absolute. When a 302 stays in place for a long time and the target looks like the lasting home of the content, Google may treat it like a permanent redirect and index the target instead. Google has also stated that 3xx redirects of either type do not lose PageRank, so the practical difference lies in which URL is indexed and how quickly, not in a fixed loss of value.
| Aspect | 302 redirect | 301 redirect |
|---|---|---|
| Meaning | Temporary move | Permanent move |
| URL usually indexed | Original source URL | New target URL |
| Canonical signal strength | Weak | Strong |
| Browser caching by default | Not cached | Cached, often for a long time |
| Long-term behavior | May be reinterpreted as permanent | Stays permanent |
| Typical use | Maintenance, tests, campaigns | Migrations, URL changes, merges |
302 compared with other redirect codes
The 302 is one of five HTTP redirect codes commonly used on the web, and choosing among them depends on two questions: is the move permanent, and must the request method be preserved.
| Code | Name | Permanence | Method handling |
|---|---|---|---|
| 301 | Moved Permanently | Permanent | May change POST to GET |
| 302 | Found | Temporary | May change POST to GET |
| 303 | See Other | Temporary | Always changes to GET |
| 307 | Temporary Redirect | Temporary | Method preserved |
| 308 | Permanent Redirect | Permanent | Method preserved |
For ordinary page navigation, 302 and 307 behave the same for SEO. Search engines treat both as temporary. Client-side alternatives such as a meta refresh or a JavaScript redirect are interpreted less reliably, so server-side redirects remain the preferred method.
When to use a 302 redirect
A 302 redirect should be used only when the original URL is expected to return within a foreseeable period. If there is no plan to restore it, the move is permanent in practice and deserves a 301.
| Situation | Recommended code | Reason |
|---|---|---|
| Short product stock-out with substitute page | 302 | Original page returns when stock arrives |
| A/B test of a page variant | 302 | Keeps the original URL canonical |
| Seasonal campaign landing page | 302 | Temporary destination for a fixed period |
| Geolocation or language routing | 302 | Target depends on the visitor |
| Domain or HTTPS migration | 301 or 308 | Move is permanent |
| Short site-wide maintenance | 503, not a redirect | Signals temporary unavailability directly |
Automatic routing by location or language needs care. Crawlers mostly come from a few regions, so a forced geo-redirect can hide other versions; hreflang annotations and visible language choices are safer than redirecting every visitor.
Common 302 redirect mistakes
Most problems with 302 redirects come from using them by default because a framework or plugin issues 302 unless told otherwise. Many site audits find permanent moves implemented as temporary ones for years.
- Permanent moves set as 302. Rankings may stay on the old URL and the new one indexes slowly.
- Redirect chains. Several hops in a row slow users and can stop crawlers before the target.
- Forgotten temporary redirects. A campaign redirect left for years confuses canonical signals.
- Redirecting to irrelevant pages. Sending every removed URL to the homepage is often treated as a soft 404.
- Mixing signals. A 302 to a page whose canonical tag points back creates conflicting instructions.
A regular redirect audit prevents these issues. Crawling the site with a status code checker, filtering for 302 responses and asking for each one whether the original URL will really return quickly separates legitimate temporary redirects from permanent moves that need a 301.
In simple terms
A 302 redirect is a temporary detour sign for a web page. When someone visits the old address, the website quietly sends them somewhere else for now, while making it clear that the original address will be back.
It works like a note on a shop door saying the counter has moved to the side entrance during renovation. Visitors still find what they need, and everyone knows the main door will open again soon. If the shop moves for good, it needs a permanent change of address instead, which is the job of a 301 redirect.
A practical example
An outdoor equipment retailer runs out of its most popular tent for about three weeks during a supply delay. Instead of leaving an empty product page, the team sets a 302 redirect from the tent URL to a page of comparable tents, so shoppers still find alternatives.
Because the redirect is temporary, search engines keep the original tent URL in the index along with its reviews and links. When stock arrives, the team removes the redirect and the page is immediately live again, with its search position intact. A permanent 301 in the same situation would have encouraged search engines to replace the product page with the category page.