SEO

302

Also called 302 Found, temporary redirect

A temporary redirect: the visitor is sent elsewhere for now, but the original address is coming back.

Quick facts: 302

Category
SEO
Also called
302 Found, temporary redirect
Level
Beginner
Affects
Which URL is indexed, crawling, rankings after a move
Where to see it
Screaming Frog, Search Console URL Inspection, browser developer tools
In this article4
  1. How a 302 works
  2. Why a 302 matters
  3. Common mistakes with 302 redirects
  4. How to act on it

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.

Do and do not

Do

  • Ask whether the address will serve content again
  • Check the code your plugin or host actually set
  • Diary a date to remove every temporary redirect

Do not

  • Use a temporary redirect for a permanent move
  • Resolve duplicate pages with a redirect instead of a canonical
  • Assume the interface set the code you intended

Questions people ask about this

Is a 302 bad for SEO?

Not in itself. It is the correct code for a genuinely temporary change, such as a product that will return to stock or a page under maintenance. It becomes a problem only when it is used for a permanent move, because search engines then keep the old address in the index instead of transferring its standing to the new page.

When should I use a 302 instead of a 301?

When the original address will serve its own content again. Typical cases are a page under maintenance, a product temporarily unavailable, a seasonal landing page, or a variant you are testing against the original. In each of those you want search engines to keep the original URL, which is exactly what a temporary redirect asks them to do.

How do I check whether my redirect is a 301 or a 302?

A browser will not tell you, because it follows the redirect silently and shows the destination. Use a crawler, the URL Inspection tool in Search Console, or the network tab in your browser's developer tools, where each hop appears with its own code. Check after any plugin or platform sets a redirect for you.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.