What is a 302 redirect?

A 302 redirect is an HTTP response that temporarily directs a request to a different URL. The response normally identifies that destination in its Location header.

The status name is 302 Found. A browser receiving this response can request the destination and display its page. The source URL remains the address intended for future requests; the redirect does not mean that the source has permanently moved. RFC 9110 defines this temporary behavior.

What a 302 tells Google

For Google, a temporary redirect is not the same canonicalization signal as a permanent move. Googlebot follows it, but the redirect itself does not designate the destination as canonical. Other signals can still lead Google to index that destination. Google’s redirect documentation explains this distinction.

A 302 therefore cannot guarantee that a URL keeps its rankings or that every ranking signal remains attached to it. Diagnose the actual response and Google-selected canonical URL before attributing a search change to a redirect.

How the HTTP response works

This illustrative response sends someone opening a registration page to a temporary information page. The domain and paths are examples, not a production configuration.

HTTP/1.1 302 Found
Location: https://example.com/registration-paused/

The destination should explain the situation and give the visitor a useful next step. A functioning redirect to an irrelevant page can still fail the visitor’s task. If the destination redirects again, inspect the entire redirect chain.

302, 301, 307 and 308 compared

Redirect meaning and request-method behavior
StatusMoveRequest-method consideration
302 FoundTemporaryA client may change POST to GET.
307 Temporary RedirectTemporaryAn automatic redirect must preserve the method.
301 Moved PermanentlyPermanentA client may change POST to GET.
308 Permanent RedirectPermanentPreserves the method on automatic redirection.

These are protocol distinctions, not percentages of SEO value. RFC 9110’s redirect definitions describe method handling. Test the application’s behavior before redirecting requests that submit or modify data.

Illustrative temporary redirect examples

A booking service could temporarily send its appointment page to a notice while it changes scheduling providers, then restore the original page. A campaign URL could direct visitors to an active offer during the campaign, with an agreed plan for what happens afterward.

An experiment may also need temporary routing, but a 302 does not decide the experiment’s canonical tags, indexing rules or traffic allocation. Those are separate choices. None of these examples establishes a recommended duration or an observed business result.

Ask whether the source is expected to return to normal service. If an article has permanently moved to a replacement URL, use a permanent redirect such as a 301 redirect. If the original location is still intended to serve the page after a temporary event, a 302 may fit.

Avoid choosing “temporary” simply because a permanent decision feels uncomfortable. Record the intended state, responsible owner and event that ends the redirect. For a site migration, map retired URLs to relevant destinations rather than routing everything to the homepage.

Check the redirect before relying on it

  • Inspect the actual HTTP response, not just what the browser displays.
  • Confirm the Location value resolves to the intended page and does not loop.
  • Test GET requests and any application methods affected by the rule.
  • Document why the redirect exists and when the business will review it.
  • After the temporary event, test both the restored source and the destination.

For a browser-style GET check, use curl -sS -D - -o /dev/null https://example.com/source/ with your actual URL. Add -L to follow the chain. curl -I sends a HEAD request, which a server can handle differently from GET.

Common mistakes

Do not infer a permanent move from how many months a 302 has existed. The documentation cited here gives no universal conversion deadline. Change the code when the intended move changes, then check the implementation.

Another mistake is treating a successful final page as proof that the first response is correct. A browser can hide the intermediate responses from casual inspection. Check each hop and remove accidental routing rules.

Additional questions

Can a 302 guarantee that my original URL stays indexed?

No. Google follows temporary redirects, and other canonicalization signals can affect which URL is indexed. The status code is not an indexing or ranking guarantee.

Should a form redirect always use 307?

Choose by the intended application behavior. A 307 preserves the request method; a 302 can allow POST to become GET. Preserving a submitted request is different from intentionally sending someone to a confirmation page.

Does a long-running 302 automatically become permanent?

Do not rely on a fixed elapsed-time rule. Use a permanent redirect when the business decision is permanent, rather than waiting for a presumed search-engine deadline.

Sources

Primary documentation accessed on 12 October 2026. Example scenarios are illustrative, not customer results.