302 Found
The requested resource has been temporarily moved to a different URL, and future requests should continue to the original URL.
Use Cases
- null
How does 302 Found affect Search Engine Optimization (SEO)?
How does Google treat Redirection 3xx HTTP response status codes?
Googlebot follows up to 10 redirect hops. If the crawler doesn't receive content within 10 hops, Search Console will show a redirect error in the site's Page Indexing report. The number of hops Googlebot follows is user agent dependent; for example, Googlebot Smartphone may have a different value than Googlebot Image. In case of robots.txt, Googlebot follows at least five redirect hops as defined by RFC 1945 and then stops and treats it as a 404 for the robots.txt file. Any content Googlebot received from the redirecting URL is ignored, and the final target URL's content is considered for indexing.
Specific information from Google on HTTP response status code 302:
Googlebot follows the redirect, and the indexing pipeline uses the redirect as a weak signal that the redirect target should be canonical.
Information from Internet Standards from IEFT
The 302 (Found) status code indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the target URI for future requests. The server SHOULD generate a Location header field in the response containing a URI reference for the different URI. The user agent MAY use the Location field value for automatic redirection. The server's response content usually contains a short hypertext note with a hyperlink to the different URI(s). Note: For historical reasons, a user agent MAY change the request method from POST to GET for the subsequent request. If this behavior is undesired, the 307 (Temporary Redirect) status code can be used instead.
Source: 302 FoundGooglebot follows the redirect, and the indexing pipeline uses the redirect as a weak signal that the redirect target should be canonical.