302 Redirect

A 302 redirect is an HTTP status code that tells browsers and search engines a page has moved temporarily to another URL. The original address is expected to return, so search engines usually keep the original URL in their index rather than the destination.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

How a 302 redirect works

When someone requests a URL, the server replies with the status code 302 Found and a Location header naming the new address. The browser follows it automatically. The key message is temporary: the move is not meant to last. Related temporary codes include 307, which keeps the request method the same, and permanent equivalents include 301 and 308. You can read more about the full family in HTTP status codes.

302 versus 301 for SEO

A 301 redirect says the move is permanent, so Google treats the destination as the URL to index. A 302 is a weaker signal that the original should stay indexed.

Google has said that all its redirects pass PageRank, so a 302 does not throw away link equity. The real difference is which URL Google chooses to show. Google has also said that if a 302 stays in place for a long time, it may start treating it like a permanent redirect, but relying on that is risky.

When to use a 302

  • Promotions or seasonal pages that will revert, such as sending a product URL to a holiday offer for a week.
  • Short maintenance or testing, such as sending a section to a temporary page while it is rebuilt.
  • A/B tests that send some visitors to a variant URL, where Google itself advises using a 302 rather than a 301.
  • Out-of-stock items temporarily pointing to a close alternative.

An example

A shop runs a summer sale and temporarily redirects /garden-furniture/ to /summer-sale/. Because the redirect is a 302, Google keeps showing the garden furniture URL in results. When the sale ends, the redirect is removed and the original page carries on as normal, with its rankings intact. Had a 301 been used, Google might have swapped in the sale page instead.

How to check redirects

  1. Use a crawler such as Screaming Frog to list every redirect and its status code.
  2. Check individual URLs with browser developer tools or an online header checker.
  3. Review the Page indexing report in Google Search Console for pages listed as having redirects.
  4. Look for chains where one redirect leads to another.

Common mistakes

  • Using 302 for permanent moves: many CMSs and plugins default to 302. During a website migration this can leave old URLs showing in results for longer.
  • Forgetting to remove it: a temporary redirect left for years confuses signals.
  • Building redirect chains: stacking temporary and permanent redirects slows pages and crawling.
  • Using JavaScript or meta refresh instead: server-side redirects are clearer for search engines.

Further reading: Google on redirects and Google Search.

Key Takeaways

  • A 302 redirect signals a temporary move to another URL.
  • Search engines usually keep the original URL indexed.
  • Google says 302s pass PageRank, so they do not waste link value.
  • Use a 301 instead whenever a move is permanent.
  • Audit redirects regularly, as many tools default to 302.

Related Terms

Curious how this applies to your website? Request a free SEO check-up, or keep learning in the SEO Encyclopedia.