A 307 redirect (Temporary Redirect) is an HTTP status code that sends a client to another URL for a limited time. The client has to repeat the request with the same method and body, so a POST stays a POST.
At a glance
- Status code
- 307
- Class
- 3xx (redirection)
- Duration
- temporary
- In Google
- same as 302: weak signal that the target should be processed
- Request method
- kept (POST stays POST)
- Specification
- RFC 9110, Section 15.4.8
Last checked:
How does a 307 redirect work?
RFC 9110 says the target resource temporarily resides under a different URI and the user agent must not change the request method. The new address comes in the Location header.
The difference from a 302 is the method. Older clients changed a POST to a GET after a 302. A 307 rules that out. For plain GET requests, which is what crawlers send, both codes behave the same. If the method should switch to GET, MDN points to 303 See Other.
Google handles 307 like 302. In its documentation, a 302 is a weak signal that the redirect target should be canonical, and 307 is treated equivalently.
| Type | Permanent or temporary? | Request method | Effect in Google | How reliably Google detects it |
|---|---|---|---|---|
| 301 Moved Permanently | permanent | POST may become GET when followed | Signal that the target should become canonical | most reliable (server-side) |
| 308 Permanent Redirect | permanent | preserved | same as 301 | most reliable (server-side) |
| 302 Found | temporary | POST may become GET when followed | not used as a canonical signal for the target; other signals can still get it indexed | most reliable (server-side) |
| 307 Temporary Redirect (this term) | temporary | preserved | same as 302 | most reliable (server-side) |
| Meta refresh, instant (0 s) | permanent | – (redirect inside the HTML, no 3xx status code) | same as 301 | after server-side redirects |
| Meta refresh, delayed (> 0 s) | temporary | – (redirect inside the HTML, no 3xx status code) | same as 302 | after server-side redirects |
| JavaScript (location) | permanent | – (redirect in the browser) | same as 301, but only if Google renders the page | least reliable: if rendering fails, Google may never see it |
Google orders redirect types by how likely it is to interpret them correctly: server-side redirects first, JavaScript last. Request-method behaviour is defined in RFC 9110 (section 15.4). Sources: Google Search Central: Redirects and Google Search (last updated 2026-04-14); Google Search Central: How to specify a canonical URL (redirects as canonical signal); RFC 9110: HTTP Semantics, 15.4 Redirection 3xx. Last checked: .
Example
HTTP/1.1 307 Temporary Redirect
Location: https://www.example.com/maintenance/
Common mistakes
- A temporary redirect stays in place for months although the move is permanent. A 301 or 308 fits that case.
- A switch from HTTP to HTTPS or to a new domain runs with 307.
FAQ
What is the difference between 302 and 307? A 307 forbids changing the request method. A 302 allows older clients to switch to GET.
Does a 307 pass ranking signals? Google treats 307 like a 302, a weak signal for the redirect target. For permanent moves, use a permanent redirect.
Sources
- RFC 9110, Section 15.4.8: 307 Temporary Redirectrfc-editor.org
- 307 Temporary Redirect – MDNdeveloper.mozilla.org
- How HTTP status codes, and network and DNS errors affect Google Search – Google Search Centraldevelopers.google.com
Last updated: