The 302 status code, also known as “Found,” is an HTTP response that indicates the requested resource has been temporarily moved to a different URI. When a server returns a 302 response, it usually includes a Location header that points to the new URI, instructing the client to make another request to that address. Although the resource has moved, the original URI should still be used for future requests, as the change is only temporary.
The Location header in the response allows user agents (like browsers) to automatically redirect to the new URL. Often, the server also includes a simple HTML message with a link to the updated location for human users.
Note: Due to legacy behavior, some user agents may change the request method from POST to GET during the redirect. If preserving the request method is important, it’s better to use the 307 Temporary Redirect status code instead.
In this article we will learn what a 302 status code means in HTTP, how temporary redirection works, and how to handle it correctly—whether you’re a developer, website owner, or SEO specialist.
From an SEO perspective, it’s important to understand how a 302 status code can impact your ranking and when you should use it. Checked out Youtube video from ClickMinded
Rails: :found
Go: http.StatusFound
Symfony: Response::HTTP_FOUND
Python 2: httplib.FOUND
Python 3+: http.client.FOUND
Python 3.5+: http.HTTPStatus.FOUND
.NET: HttpStatusCode.Found
Rust: http::StatusCode::FOUND
Java: java.net.HttpURLConnection.HTTP_MOVED_TEMP
Apache HttpComponents Core:
org.apache.hc.core5.http.HttpStatus.SC_MOVED_TEMPORARILY
Angular: @angular/common/http/HttpStatusCode.Found
Example of a 302 status code:
Request:
GET /example HTTP/1.1
Host: www.example.com
Response:
HTTP/1.1 302 Found
Location: https://www.example.com/new-location
This indicates that the requested resource has been temporarily moved to a new location.
By following these measures, you can resolve a 302 status code and ensure optimal website performance for users and search engines alike.
A 302 status code signifies that the requested resource has been temporarily relocated to a different location. It’s commonly employed for redirects when a resource is temporarily inaccessible or has been shifted to another location. Conversely, a 200 status code indicates that the request has been successful, with the server delivering the requested resource.
In essence, a 302 status code serves for temporary redirects, while a 200 status code indicates successful requests that provide the requested content.
The impact of a 302 status code on SEO can vary based on its usage.
When a 302 redirect is employed to temporarily redirect a page to another URL, search engines typically update their index to reflect the new URL. However, improper configuration or non-temporary redirection can lead to duplicate content, broken links, or other issues detrimental to SEO.
In general practice, it’s advisable to utilize a 301 permanent redirect instead of a 302 temporary redirect when redirecting a page to a new URL.
This signals to search engines that the redirection is permanent, ensuring that any SEO value associated with the original page is transferred to the new URL. If a 302 redirect is unavoidable, it should be used cautiously to prevent adverse effects on the website’s SEO.

Pinal Bhalodia is a multi-faceted professional with a diverse skill set spanning creative website design, Google Adwords, Search Engine Optimzation , IT expertise, and sales acumen. With a passion for blending technology with artistic flair, Pinal has carved a niche for himself in the dynamic intersection of these fields.