A 307 redirect is a temporary redirect that strictly preserves the HTTP method of the original request. Unlike a 302, which historically allowed method changes, a 307 guarantees that a POST request remains a POST after redirection.
The 307 Temporary Redirect status code was introduced in HTTP/1.1 to address ambiguity in how browsers handled 302 redirects. When a server returns a 307, the client must use the exact same HTTP method (GET, POST, PUT, etc.) when following the redirect. The original URL remains the canonical version for search engine indexing purposes.
For SEO, 307 redirects behave similarly to 302s — search engines treat the move as temporary and keep the original URL indexed. The key distinction matters for web applications that handle form submissions or API calls, where changing the request method during a redirect could cause data loss or errors.
The server responds with a 307 status code and a Location header pointing to the temporary destination. The browser follows the redirect using the same HTTP method it originally used. This is configured in server settings or application code, and is particularly important for HTTPS upgrades and form processing workflows.
Want to learn more? Explore our SEO Glossary or check out our expert guides on SEO strategies.