A 302 redirect is a temporary redirect. It tells browsers and search engines that a page has moved for now, but the original URL is expected to come back. In SEO, that matters because a 302 usually signals that the original page should keep its indexing signals, while users are sent to a different destination in the meantime.
Why a 302 redirect matters for SEO
Redirects affect crawling, indexing, link equity, and user experience. If you use a 302 when a move is truly temporary, search engines are more likely to keep the original URL in their index. That can be useful during short-term site changes such as maintenance, limited-time campaigns, or A/B testing.
If you use a 302 by mistake for a permanent move, you can create mixed signals. Search engines may continue treating the old URL as the main version longer than you want. That can slow consolidation of rankings and confuse reporting in analytics and SEO tools.
302 vs 301: when to use each
Use a 302 redirect when the change is temporary
Choose a 302 if the original page will return. Common cases include seasonal landing pages, short-term product substitutions, location-based testing, and temporary stock issues where a product page may come back soon.
Use a 301 redirect when the change is permanent
Choose a 301 if a page has been permanently replaced, deleted, or merged into another page. A 301 is the standard option for site migrations, URL changes, and content consolidation because it clearly tells search engines to transfer signals to the new destination.
Practical example of a 302 redirect
Imagine an online store has a product page for a popular jacket. The jacket is temporarily unavailable for two weeks because of a supplier delay. Instead of deleting the page, the store sets a 302 redirect from the jacket URL to a closely related category page or a waitlist page. Users still find a useful destination, and search engines understand the original product URL may return.
When the jacket is back in stock, the 302 can be removed so the original product page becomes active again. This is usually better than using a permanent redirect, which could make it harder to preserve the original page’s role in search.
Best practices for using 302 redirects
Use a 302 only when you have a clear temporary reason. Redirect to the closest relevant page, not just the homepage. Avoid redirect chains, where one redirect leads to another, because they waste crawl budget and slow down users. Update internal links if the temporary destination will be used for more than a brief period. Finally, test the server response to confirm it returns a true 302 status code, not a meta refresh or JavaScript-only redirect.
For growing teams, the simplest rule is this: if the old URL is coming back, use a 302. If it is not, use a 301.