302 Redirect

A 302 redirect is an HTTP status code that temporarily sends one URL to another. It tells browsers and search engines that a page has moved for now but will return to its original location. Because the move is temporary, search engines keep the original URL indexed instead of replacing it with the destination.

The “302” is the status code a server returns in its response header. In HTTP/1.1 the official label is “302 Found.” In the older HTTP/1.0 spec it was “302 Moved Temporarily.”

HTTP/1.1 302 Found
Location: https://example.com/temporary-page

How a 302 Redirect Works

A 302 redirect runs at the server level before any page content loads. When a browser requests the old URL, the server responds with a 302 status and a Location header pointing to the new URL. The browser then loads that new URL automatically.

The process happens in three steps:

1. A user or bot requests the original URL. The request reaches the server.
2. The server returns a 302 status and the new location. No content loads at the original address.
3. The browser follows the Location header. It loads the destination URL, usually without the user noticing.

Unlike a 301, a 302 is not cached aggressively by default. Browsers re-check the original URL on future visits, which is correct behavior for a move meant to be undone.

302 vs 301 Redirect

A 302 is temporary and a 301 is permanent. That single difference changes how search engines treat each one.

• 302 (temporary). Signals the original URL will return. Search engines keep the old URL indexed and direct ranking signals at it, not the destination.
• 301 (permanent). Signals the move is final. Search engines transfer ranking signals to the new URL and eventually drop the old one from the index.

Use a 301 when content moves for good, such as a URL change, domain migration, or HTTP-to-HTTPS switch. Use a 302 only for short-lived moves. For the permanent case and how to set it up, see the 301 redirect glossary entry.

Google’s Gary Illyes confirmed in 2016 that all 30x redirects pass full PageRank, so a 302 does not “lose” link equity. The risk is different: a 302 keeps the wrong URL indexed when the move was actually permanent.

When to Use a 302 Redirect

Use a 302 when the original URL needs to come back. Common cases include:

• A/B testing. Send a portion of traffic to a variant page without removing the original from search results.
• Temporary promotions. Point a product URL to a seasonal sale page, then revert when the sale ends.
• Maintenance pages. Route visitors to a “back soon” page while the real page is offline.
• Geo or device routing. Send users to a region- or device-specific page while keeping the canonical URL indexed.

Do not use a 302 for a permanent move. If a 302 stays in place long enough, Google’s John Mueller has said the search engine may eventually treat it like a 301, but relying on that is slow and unpredictable. Set a 301 from the start when the change is final.

307 vs 302

A 307 Temporary Redirect is the stricter HTTP/1.1 version of a 302. The key difference is method handling. A 307 forces the browser to repeat the original request method, so a POST stays a POST. A 302 historically allowed browsers to switch a POST to a GET. For temporary redirects on forms or API endpoints, a 307 is the safer choice.

After setting any redirect, confirm it returns the status code you intended. linkutm’s redirect checker shows the exact code and the full redirect path for any URL.

Frequently Asked Questions

What is a 302 redirect?

A 302 redirect is a server response that temporarily points one URL to another. It tells browsers and search engines the page has moved for now but will return. Search engines keep the original URL indexed rather than the destination.

What is the difference between a 302 and a 301 redirect?

A 302 is temporary and a 301 is permanent. A 302 keeps the original URL indexed because the move is expected to reverse. A 301 transfers ranking signals to the new URL and removes the old one from search results over time.

When should you use a 302 redirect?

Use a 302 for short-lived moves: A/B tests, temporary promotions, maintenance pages, or geo routing. The original URL must be the one you want to keep ranking. For any permanent move, use a 301 instead.

Does a 302 redirect hurt SEO?

A 302 used correctly does not hurt SEO, since Google confirmed 30x redirects pass full PageRank. The problem is using a 302 for a permanent move. That keeps the old URL indexed and delays the new URL from ranking.

To confirm a redirect returns the right status code and avoids chains, run the free redirect checker at linkutm.