302 Found
The resource is temporarily at a different URL.
What it means
HTTP 302 Found is a temporary redirect. It tells clients the resource lives at the Location URL for now, but the original URL should still be used in future because the move is not permanent.
When it happens
It happens for temporary situations: A/B tests, geo or device redirects, sending users to a login page, or a maintenance redirect that will be reverted.
How to fix it
- Use 302 only for genuinely temporary redirects; use 301 when the move is permanent.
- If a page has permanently moved but returns 302, switch it to 301 so signals transfer.
- Make sure the destination is correct and does not itself redirect again.
SEO impact
Mixed. Search engines generally keep the original URL indexed for a 302 and may not transfer ranking signals. Using 302 where you meant 301 is a common SEO mistake that can stall a migration.
Find out which of your URLs return 302
Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.
Related codes
A temporary redirect that preserves the original request method.
301 Moved PermanentlyThe resource has permanently moved to a new URL.
303 See OtherThe response to the request can be found at another URL using a GET request.
304 Not ModifiedThe cached version of the resource is still valid, so no body is sent.
305 Use ProxyA deprecated code telling the client it must reach the resource through a specified proxy.
306 Switch ProxyA reserved, unused status code that no longer carries any meaning.
Related guides
The difference between 301 and 302 redirects, when to use each, how they affect SEO and link equity, and how to verify a redirect is doing what you intended.
HTTP status codes explained: a practical primer for SEOsA plain-English primer on HTTP status codes for SEOs: what the 2xx, 3xx, 4xx, and 5xx families mean, which ones affect rankings, and the codes worth knowing.