A 307 Temporary Redirect tells a browser or crawler that a resource is at a different URL for now, and that future requests should keep using the original address. The HTTP standard adds one strict rule: when following the redirect automatically, the client must not change the request method. For search, Google groups 307 with the other temporary redirects, so the original URL usually keeps its place in results.
Need help with SEO?
Comppound runs SEO and AI search for SaaS companies. We plan what to publish, produce it with AI, and every page passes automated checks, and a person reviews samples and anything high-risk.
- Published to your site and tracked in Search Console
- One person answers for your account
- Plans from $400 a month, terms from 3 months
How 307 differs from 302
Both codes mean temporary, and Google treats both as temporary. The difference is at the HTTP level. RFC 9110 says a client following a 307 must not change the request method, which makes it the safer choice when a form submission or API call has to arrive intact at the new location.
For an ordinary page requested with GET, the two codes behave the same way for a visitor. Choosing between them rarely matters for SEO.
What Google does with a 307
Google lists HTTP 307 among its temporary redirects, alongside 302 and 303. Googlebot follows the redirect, but the redirect is not treated as a canonical signal. The source URL can stay in search results, and the target may still be indexed if other canonicalization signals point to it.
Google's documentation on HTTP status codes describes 302, 303 and 307 as a weak signal that the target should be processed, compared with a strong signal for 301 and 308.
When a 307 is the right choice
Use one when the move really will be undone and the method needs to survive the trip. If the page has moved for good, use a permanent redirect instead, because a temporary code leaves search engines holding on to the old URL.
- A checkout or signup endpoint moved briefly during maintenance
- An API route temporarily served from another host
- A short test that sends POST requests to a different handler
HTTP/1.1 307 Temporary Redirect
Location: https://example.com/signup-tempExample
A signup form during a short migration
Hypothetical scheduling SaaS Calendrift moved its signup handler to a new service for a weekend while the main app was upgraded. A 302 risked some clients resending the form as GET and losing the data, so the team used a 307 for the POST route.
On Monday the handler moved back and the redirect came out. The public /signup URL stayed in search results throughout, because nothing had told Google the move was permanent.
Common mistakes
Leaving a 307 in place for a permanent move
A temporary code does not tell Google to treat the target as canonical. If the move is final, switch to a 301 or 308.
Assuming every 307 came from the server
Browser developer tools can show a 307 generated by the browser itself, for example when it upgrades a request to HTTPS under an HSTS policy. Test the raw server response with a command line tool before changing any configuration.
Frequently Asked Questions
Google treats it as a temporary redirect, so it is not a canonical signal for the target. If you want the target to replace the source in results, use a permanent redirect.
Only when keeping the request method matters, such as a POST request. For a normal page view the two behave the same way for visitors and for Google.
Keep reading
- 302 Redirect: A 302 redirect sends visitors to another URL temporarily, signaling search engines to keep the original URL in their index.
- 308 Redirect: A 308 redirect is a permanent redirect that keeps the original HTTP method. Google treats it like a 301, as a signal that the target should become the canonical URL.
- 301 Redirect: A 301 redirect is an HTTP response telling browsers and search engines a URL has moved permanently to a new address.
- HTTP Status Codes: HTTP status codes are three-digit server responses that tell browsers and crawlers whether a request succeeded, moved, or failed.
- AMP: AMP is a web framework for building fast-loading pages under strict rules on JavaScript and CSS. Google no longer requires it for the Top Stories carousel.
- Cache-Control: Cache-Control is an HTTP header that tells browsers and CDNs whether and how long to store a response. Good caching makes repeat loads and crawls faster.
- Canonical URL: A canonical URL is the version of a page search engines treat as the main one when several URLs show the same or very similar content.
- Canonicalization: Canonicalization is the process of choosing one preferred URL when several pages have duplicate or very similar content, so search engines know which version to show.
