302 redirect

A 302 redirect is a temporary redirect from one URL to another, signalling to browsers and search engines that the original address will soon return. The HTTP 302 status code ('Found') indicates a transitional change, so search engines keep the old address in their index and do not transfer the hard-won SEO value to the new one.

How a 302 redirect works

When a server responds with a 302 code, it directs the user to the given address while communicating that this is a temporary arrangement. That is the fundamental difference from a 301 redirect, which signals a permanent change. The key characteristics of a 302 redirect are:

• Temporariness — a message that the original address is still the intended destination URL.
• Preserved SEO value — link equity stays with the original address, not the target.
• No index update — search engines keep the old URL in the results.
• Flexibility — ideal for transitional situations and tests.

302 redirects in practice

A 302 redirect fits wherever the change is momentary:

1. Maintenance work — temporarily routing users to an informational page.
2. A/B tests — directing part of the traffic to a test variant of a page.
3. Offers and promotions — temporary campaigns and seasonal pages.

The most common mistake is using a 302 instead of a 301 for a permanent move — this means the new address does not take over the ranking and link equity. On Apache servers both redirect types are configured in the .htaccess file, so before deploying it is worth making sure the chosen status code matches the real intent.