307 Temporary Redirect
A temporary redirect that preserves the original request method.
What it means
HTTP 307 Temporary Redirect is like 302 but with a strict guarantee: the client must repeat the request to the new URL using the exact same method and body. A POST stays a POST. The move is temporary, so the original URL should still be used in future.
When it happens
It happens with temporary redirects where the method must be preserved — for example, HSTS upgrading HTTP to HTTPS, or temporarily routing a POST to a different endpoint.
How to fix it
- Use 307 for temporary redirects that must keep the request method intact.
- If the move is permanent, use 308 (preserves method) or 301 instead.
- Confirm the destination handles the same method the client originally used.
SEO impact
Treated as temporary, like a 302. The original URL stays indexed and signals are generally not transferred, so do not use 307 for permanent moves.
Find out which of your URLs return 307
Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.
Related codes
The resource is temporarily at a different URL.
308 Permanent RedirectA permanent 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.
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.