The 307 status code, also known as the 307 Temporary Redirect, is an HTTP response that tells browsers and search engines that a requested URL has been temporarily moved to another location — without changing the original HTTP request method.
In simple terms, if a user sends a POST request, it will remain a POST request after the redirect. This is what makes the HTTP 307 status code different from other 3xx redirects.
What Does a 307 Temporary Redirect Mean?
A 307 redirect indicates that:
- The redirect is temporary
- The original URL may be used again in the future
- The browser must preserve the request method (GET stays GET, POST stays POST)
This behavior was introduced to fix ambiguity in older redirects like 302, which could unintentionally change POST requests into GET requests.
HTTP 307 Status Code Explained
Think of a 307 redirect like this:
“This page has moved for now. Please go to the new location — but send the request exactly the same way.”
This is especially important for:
- Form submissions
- Payment gateways
- APIs
- Authentication flows
How 307 Redirect Works
Here’s how the 307 redirect works step by step:
- A user or browser requests URL A
- The server responds with a 307 Temporary Redirect
- The response includes a new Location URL
- The browser redirects the request without changing the HTTP method
Example HTTP Response
HTTP/1.1 307 Temporary Redirect
Location: https://example.com/new-pageIf the original request was a POST, the redirected request will also be a POST.
307 Redirect vs Other 3xx Status Codes
Understanding the differences between redirects is crucial — especially for SEO and application behavior.
Difference Between 307 and 302
| Feature | 302 Redirect | 307 Redirect |
|---|---|---|
| Redirect Type | Temporary | Temporary |
| Method Preservation | Not guaranteed | Guaranteed |
| Introduced For | Legacy behavior | HTTP/1.1 clarity |
| Recommended Today | Sometimes ambiguous | Yes |
Key takeaway:
If request method consistency matters, 307 is the safer choice.307 vs 301 vs 308 (Quick Overview)
| Status Code | Permanent | Preserves Method | SEO Signal |
|---|---|---|---|
| 301 | Yes | Yes | Passes link equity |
| 307 | No | Yes | Temporary, no ranking transfer |
| 308 | Yes | Yes | Passes link equity |
Is 307 Redirect Bad for SEO?
No — 307 redirects are not bad for SEO, but they are not meant for ranking transfers.
SEO implications of 307:
- Google treats it as temporary
- The original URL remains indexed
- No long-term link equity is passed
- Not suitable for permanent URL changes
If the redirect is permanent, use 301 or 308 instead.
When Should You Use a 307 Redirect?
Use a 307 temporary redirect when:
- A page is under temporary maintenance
- Running A/B tests
- Redirecting users during form processing
- Handling login or authentication flows
- Managing temporary API endpoints
These scenarios rely heavily on method preservation, which is where 307 shines.
When You Should NOT Use a 307 Redirect
Avoid using 307 when:
- Migrating a website permanently
- Changing domain names
- Updating URL structures for SEO
- Consolidating duplicate pages
In these cases, Google expects a permanent redirect, not a temporary one.
How to Implement a 307 Redirect
Below are common ways to implement a 307 redirect.
Apache (.htaccess)
Redirect 307 /old-page https://example.com/new-pageNginx
return 307 https://example.com/new-page;JavaScript
window.location.replace("https://example.com/new-page");Always test redirects using browser dev tools or tools like HTTP status checkers.
Common Mistakes With 307 Redirects
- Using 307 instead of 301 for SEO migrations
- Leaving temporary redirects active for months
- Redirecting critical landing pages unnecessarily
- Creating redirect chains involving multiple 3xx responses
The 307 status code is a powerful redirect type when used correctly. It’s designed for temporary URL changes where maintaining the original HTTP request method is critical.
For SEO:
- Use it cautiously
- Don’t use it for permanent changes
- Combine it with clear intent and proper testing
When used properly, the HTTP 307 status code helps maintain application stability without harming user experience or search visibility.
Frequently Asked Questions
Is 307 status code temporary?
Yes. A 307 redirect is always temporary and tells search engines not to replace the original URL in their index.
Does 307 redirect pass SEO value?
No. Since it’s temporary, link equity is not transferred.
Is 307 better than 302?
For modern applications — yes. 307 is clearer and safer because it preserves the request method.
Can Google index a 307 redirect?
Google may keep the original URL indexed if the redirect remains temporary.
