How a 302 works
The server answers a request with the code 302 and the address to go to instead. The browser follows it, and to the visitor it looks exactly like a 301. The difference is not in what happens on screen, it is in what you are telling search engines.
A 302 says: this address is still the real one, it is just unavailable at the moment, so send people over there for now. Search engines respond by keeping the original URL in their index and continuing to check back, rather than replacing it with the destination. That is the whole point of the code, and the only reason to choose it.
Left in place indefinitely, the message starts to look untrue. A redirect that has not moved for a very long time will eventually be read as a permanent one, because the evidence says the original is never coming back — but that is a search engine’s guess, not your instruction, and it takes its own time.
Why a 302 matters
Choosing correctly between temporary and permanent decides which URL search engines keep. Get it right and a genuinely temporary change costs you nothing, because the original page holds its place while the situation resolves.
Get it wrong in the other direction and it is expensive. Move a page permanently but announce it as temporary, and search engines carry on showing and crawling an address that no longer has content, while the new page struggles to take its place. Sites lose visibility during a redesign for exactly this reason, and the cause is a single word in a configuration file.
Common mistakes with 302 redirects
The most frequent one is not choosing at all. Many platforms, plugins and hosting panels create a temporary redirect by default, and the person setting it up never sees which kind it is. If you are moving a page for good, check the code afterwards rather than trusting the interface.
The second is using a 302 to manage duplicate content. Two versions of a page that both need to exist should be resolved with a canonical tag, not a redirect, because a redirect makes one of them unreachable.
The third is the forgotten holiday. A shop redirects a category during a festival, the festival ends, and the redirect stays for another year. Every temporary redirect needs a date in someone’s calendar for taking it off again.
How to act on it
Ask one question before you set any redirect: will this address ever serve its own content again? If the honest answer is no, use a permanent redirect. If it is yes — an out-of-stock product returning next month, a page behind maintenance, a variant you are testing — a 302 is the right choice and the original keeps its standing.
Then audit what you already have. Crawl the site, list every redirect with its code, and check each temporary one against that question. Most sites find at least one that should have been permanent years ago, and correcting it is ordinary technical SEO maintenance rather than a project.
