A 307 Temporary Redirect is an HTTP status code that tells browsers and search engines that a requested URL has been temporarily moved to another URL, while preserving the original HTTP request method. A 307 redirect explicitly instructs clients to repeat the request using the same method, such as POST or PUT, rather than converting it to a GET request.
307 redirects tell search engines that the redirect is temporary and is not permanent. The original URL remains the canonical location, and indexing signals are expected to stay with the source URL rather than being consolidated at the temporary destination served by the redirect.
What Is the HTTP 307 Temporary Redirect
The HTTP 307 Temporary Redirect is an HTTP status code that indicates a temporary URL change while preserving the original request method. The primary purpose of a 307 redirect is method preservation. If a user submits a POST request to a URL that returns a 307, the browser resends the POST request to the destination URL exactly as it was sent to the original URL.
In this way, a 307 redirect serves to resolve the issue older temporary redirects have created. Earlier status codes, such as 302, were inconsistently handled by browsers and often converted non-GET requests into GET requests. The 307 redirect removes ambiguity by enforcing strict request behavior.
Regarding protocols, a 307 redirect is explicit, reversible, and non-authoritative. It signals that the original URL is still valid, but there is a truly temporary redirect in place.
When To Use a 307 Temporary Redirect
A 307 Temporary Redirect should be used when a URL change is temporary and the original HTTP request method must be preserved. This commonly applies to application-level routing, maintenance windows, testing scenarios, or any other time where traffic is temporarily rerouted but the original endpoint will be restored.
HTTP 307 Temporary Redirects and SEO
From an SEO perspective, a 307 redirect is treated as temporary and non-consolidating. Google generally keeps the original URL indexed and does not transfer long-term ranking signals to the destination URL in the same way it would with a 301 redirect.
Due to this, a 307 does not imply a canonical change. Meaning, search engines expect the original URL to return in the future, so they continue to associate relevance, links, and historical signals with the original URL.
How 307 Temporary Redirects Can Hurt SEO If Not Used Properly
307 redirects are meant to be used in strictly temporary situations. They are not meant to be used indefinitely. In fact, using 307 redirects for long periods can slow re-ranking and create ambiguity. If a redirect remains in place indefinitely, Google may eventually reinterpret intent, but this happens slowly and inconsistently. Temporary redirects are evaluated conservatively by design.
A 307 redirect does not cause a penalty, but it can prevent desired consolidation. Pages that should inherit authority will not do so reliably if they are only reachable through a 307 redirect.
When You Should Use a 301 Instead of a 307
A 301 redirect should be used when a URL change is permanent and intended to consolidate indexing and ranking signals. If a page has been replaced, removed, or merged, a 301 redirect communicates finality and allows search engines to transfer relevance and authority to the destination URL.
Site migrations & Permanent Redirection
A 307 redirect should not be used for site migrations, canonical cleanup, URL normalization, or long-term structural changes. In these cases, a 307 sends the wrong signal and can delay or prevent proper index updates.
Using the correct redirect type reduces ambiguity for crawlers, accelerates reprocessing, and prevents mixed signals during indexing.
How This Applies to Ongoing SEO Work
Temporary redirects should only be used when a URL change is genuinely short-term. For pages that represent active services or long-term offerings, permanent redirects provide clearer signals and allow authority to accumulate correctly. Matching redirect intent to business intent helps avoid unnecessary indexing delays and keeps technical SEO aligned with growth goals.
If you’re unsure which redirect type fits your current goals or technical setup, working with an experienced SEO team can help clarify intent, clean up legacy redirects, and ensure your site’s technical foundation supports long-term growth.