Opens in a new tab
3 4 5 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

What is 302 Redirect

Definition: 302 redirect

A 302 redirect is an HTTP response indicating that the requested resource is temporarily available at another location. The server returns the `302 Found` status code and identifies the new URL in the `Location` header; the browser or another client may then request that destination.

The original address remains the intended reference while the change is temporary. For search engines, this signal helps distinguish a temporary substitution from a permanent move, although final treatment also depends on duration, consistency, and other signals observed during crawling.

How a 302 redirect works

When a client requests an address, the server does not deliver the usual content and responds with the 302 status. The `Location` header contains the destination, which may be on the same domain or a different one. The client follows that address and makes another request.

The redirect operates at the HTTP level, before the document is displayed. It is not equivalent to a link, a canonical tag, or a JavaScript update. A person will usually notice only the address change, whereas diagnostic tools can observe each response in the chain.

For a `GET` request, the practical behavior of 302 and 307 is usually similar. After certain requests such as `POST`, clients may change the method to `GET` when following a 302. A 307 is used when the original method and request body must explicitly be preserved.

When it is used

A temporary redirect is used when the source URL is expected to recover its function or remain the primary reference. Common uses include:

  • Temporary maintenance: sending visits to an available page while work is carried out on the original.
  • Controlled tests: displaying a variation during a limited experiment without communicating a permanent move.
  • Temporary availability: directing to an alternative while a product, service, or piece of content is unavailable.
  • Location or language: temporarily suggesting an adapted destination when a clear version switch remains available.
  • Transitional rules: applying a provisional route during a campaign, incident, or operational change.

Temporary status is not defined by a fixed number of days. A redirect maintained for a long period, chained with other redirects, or accompanied by conflicting signals may be interpreted differently by a search engine. If the destination is meant to replace the source permanently, a permanent signal is appropriate.

Difference from other codes

A 301 redirect communicates a permanent move. Search engines will generally select the destination as the reference and consolidate signals associated with the source over time. With a 302, the declared intention is to retain the source as the primary URL while the destination performs a temporary role.

The 303 and 307 codes are also temporary but define method handling more precisely. `303 See Other` directs the client to retrieve another resource with `GET`, while `307 Temporary Redirect` preserves the method and body. The choice is particularly relevant to forms, APIs, and operations that modify data.

A redirect does not make the old page accessible to the person requesting it: while the rule is active, that request receives the redirect response. The original content can be served again after the rule is removed, provided that it remains available on the server.

Implementation methods

The response can be generated by the web server, application, content delivery network, or redirect manager. The specific configuration depends on the infrastructure:

  • HTTP header: the application returns status 302 and a valid `Location` header.
  • Apache: an Apache directive can declare `Redirect 302 /source https://example.com/destination`.
  • Nginx: a rule can respond with `return 302 https://example.com/destination`.
  • CMS: a plugin or module stores the mapping and generates the response from the application.
  • CDN or proxy: the edge layer applies the rule before the request reaches the origin server.

The destination should be an absolute URL or a valid reference for the environment in use. Broad rules need to preserve paths and parameters correctly when required; a poorly constructed substitution may send many different addresses to an irrelevant destination.

Verification and limitations

Verification examines the returned status, the `Location` header, the final destination, and the number of hops. Browser tools, `curl`, crawlers, and server logs can reveal redirect chains, loops, failed destinations, or rules that affect only certain user agents.

Internal links, sitemaps, and canonical tags are also checked against the intended architecture. If the situation is temporary, these signals may continue to point to the source; if the move becomes permanent, they should be updated consistently with the new decision.

A 302 does not by itself guarantee preserved rankings, traffic, or link value. Search engines process the relationship between the URLs using several signals and may treat a long-running redirect as a stable change. Its technical purpose is to communicate temporary status, not to ensure a particular SEO outcome.

Related Terms