Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

302 Redirect: When to Use a Temporary Redirect

Updated · 6 min read

Short answer Use a 302 only when the original page is coming back: a split test, a seasonal page, a service paused for a few weeks. Google keeps showing the original address while a 302 is in place. If the page has moved for good, use a 301. If the whole site is down for a day or two, Google advises a 503.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

When is a 302 redirect the right choice?

When you know the original page will be back. A 302 says "look over there for now", and Google acts on that: it keeps the original address in search results instead of swapping in the new one.

"Temporary redirects: Show the source page in search results." (Google Search Central: Redirects and Google Search)

So the test is one question: on a set date or event, will this redirect come off and the old page work again? Yes means 302. No, or "probably not", means 301.

SituationRight answerWhy
Testing a new version of a page against the old one302Google's testing guide asks for it by name
A service you've paused for a few weeks (a closed location, a sold-out offer)302 to a page explaining whyGoogle's own example of a temporary redirect
A seasonal page you disable each off-season302 to your main pageIt returns next season at the same address
A page down while you rewrite it302 to a "coming soon" pageSame address goes live again
You renamed or moved a page301The old address isn't coming back
You merged pages, dropped a service or changed domain301Same
Your whole site is down for 1–2 days503, not a redirectGoogle's advice for a short shutdown
Sending visitors to a language version based on a guessNo automatic redirectGoogle advises against it

What does Google do with a 302?

It follows the visitor to the new page but treats the redirect as a hint, not an instruction. Google's crawler documentation calls a 302 a "weak signal" that the target page should be processed, and a 301 a "strong signal" (Google: How HTTP status codes affect Google's crawlers).

In practice:

  • The original page keeps its place. Google says a temporary redirect "may help keep the old URL in its Search results" (Google Search Central: Redirects and Google Search). That's the whole point.
  • The new page might still get indexed. Google says the target "might still be indexed if other canonicalization signals are present", such as your own links and sitemap pointing at it (same page). A canonical is the one address Google picks to show when several lead to the same content.
  • Link value stays with the original address. Google doesn't publish a rule on how much link credit a 302 passes. What it documents is that the redirect isn't used to make the target the main address, so the old address remains the one in the index. MDN, the web developer reference, says search engines won't credit links to the original page to the new one (MDN Web Docs: 302 Found).

That last point is why a 302 used for a permanent move hurts. Your new page waits for Google to decide on its own, while the old address keeps showing.

Should maintenance use a 302 or a 503?

It depends on how much is down. For one page or one service, a 302 to an explanation page fits Google's example exactly. For the whole site, Google recommends a different code:

"If you need to urgently disable the site for 1-2 days, then return an informational error page with a 503 HTTP response status code instead of all content." (Google Search Central: Pausing or disabling a website)

A 503 means "service unavailable, try later". Redirecting every page to one maintenance page with a 302 tells Google all your pages now lead to the same place. For a shutdown longer than a couple of days, Google suggests keeping a normal home page live with a 200 status code (same page).

Is a 302 right for A/B testing?

Yes, when the test sends visitors from the original address to a variation at a different address. Google is direct:

"If you're running a test that redirects users from the original URL to a variation URL, use a 302 (temporary) redirect, not a 301 (permanent) redirect." (Google Search Central: Minimize A/B testing impact in Google Search)

Google adds two conditions on the same page: run the test only as long as you need for a reliable result, and remove the test redirects as soon as it ends. A 302 left in place for months isn't a test anymore.

302 vs 307: does it matter?

Not for Google. Its crawler documentation says a 307 is "equivalent to 302" (Google: How HTTP status codes affect Google's crawlers). The difference is technical: after a 302, a browser may turn a form submission into a plain page load, while a 307 forbids that (MDN Web Docs: 302 Found). If a contact form posts to an address you're redirecting, ask your developer for a 307. A 303 and a meta refresh with a delay of more than 0 seconds also count as temporary to Google (Google Search Central: Redirects and Google Search).

How do you set up or check a 302?

Most website builders let you pick. On Squarespace you add a line in the URL mappings panel ending in 302, for example `/seasonal-offerings -> /main-store-page 302`, and the original page must be disabled for it to work (Squarespace Help Center: URL mappings). On your own server, Google's redirect guide shows the Apache and NGINX settings (Google Search Central: Redirects and Google Search).

To see what your site actually sends, paste the old address into any free redirect checker, or ask your developer to run `curl -I` on it. The first line shows the code. If it says 302 for a page you moved for good, change it to 301. If the checker shows several hops in a row, point the old address straight at the final page. Google's crawlers follow up to 10 hops, but each one is a chance to break (Google: How HTTP status codes affect Google's crawlers).

Common places a 302 sneaks in by accident: a plugin's default setting, a developer's quick fix during a launch, or a redirect set "for now" that nobody removed. Check your redirects after any site change.

Example

Illustrative cases with invented numbers.

A landscaper's winter page

From December to March, the lawn care page redirects with a 302 to a snow removal page. In April the redirect comes off. Because Google kept the lawn care address in results all winter, it's ready for spring searches without waiting to be found again.

A dental office tests a new booking page

For 6 weeks, half of visitors to the new patient page go to a variation at a different address via a 302. The new version books 20% more visits, so the office puts it on the original address and deletes the redirect and the variation.

A bookkeeper's forgotten redirect

The site moved `/services.html` to `/bookkeeping/` two years ago with a 302 the developer meant as temporary. Google still shows the old address. Switching it to a 301 tells Google the move is final.

FAQ

How long can a 302 stay in place?

Google sets no deadline. The question is intent: if the original page isn't coming back, the redirect should be a 301, whatever the age.

Will a 302 hurt my rankings?

Not when the move is temporary. It's meant to keep the original page in results. It hurts when used for a permanent move, because the new page isn't treated as the replacement.

Is a 302 the same as "302 Found"?

Yes. "Found" is the code's official name, and Google's redirect guide lists it as "HTTP 302 (found)". Both mean a temporary redirect.

Can I switch a 302 to a 301 later?

Yes. Once you decide a move is permanent, change the code. Google picks up the change the next time it recrawls the old address.

Different for you?

Keep learning

Next404 Errors and SEO: Do They Hurt Your Google Rankings?Google says 404 errors alone don't hurt rankings. Which 404s cost you traffic or links, which to ignore, and the soft 404 kind that does cause trouble.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Redirects and Google Search
  2. Google Crawling Infrastructure: How HTTP status codes affect Google's crawlers
  3. Google Search Central: Minimize A/B testing impact in Google Search
  4. Google Search Central: Pausing or disabling a website
  5. Google Search Central: Managing multi-regional and multilingual sites
  6. MDN Web Docs: 302 Found
  7. Squarespace Help Center: URL mappings