A 307 redirect is a temporary redirect that tells the browser and search engines that the requested page has temporarily moved to a new URL. This type of redirect differs from a 301 redirect, which is permanent, by preserving the original HTTP method (either GET or POST) when redirecting.
When you use a 307 redirect, it means that the original page is expected to return at some point, so it is important to tell both users and search engines that this move is only temporary. Because it is a temporary move, search engines will typically not update their index with the new URL, which is a key difference from a 301 redirect that permanently changes the URL in search results.
When is a 307 redirect used?
A 307 redirect is used when you want to redirect traffic temporarily, but without changing the way the data is sent. Here are some typical scenarios:
- During temporary maintenance: If a page needs to be updated or maintained, but you plan to bring it back soon, you can use a 307 redirect to send users to a temporary page.
- Server overload: If a server is overloaded, a 307 redirect can be used to send traffic to another server temporarily.
- Content testing: If you are testing new content on a different URL, but want to keep the old page active for later, you can use a 307 redirect to ensure users can still access the temporary content.
How does a 307 redirect affect SEO?
Because a 307 redirect is temporary, it usually does not pass “link juice” (SEO value) from the original URL to the new URL. This means that a 307 redirect should not be used for permanent changes, as it can negatively affect your SEO. Search engines will likely treat the temporary page differently than the original, as they do not see the redirect as a permanent change.
When you want to move a page permanently and transfer its SEO value, you should instead use a 301 redirect. This ensures that both users and search engines know the move is permanent, and it also transfers the SEO value to the new page.