Is there an SEO difference between 302 and 307?

Effectively no. Both are temporary redirects, so search engines treat them the same way: the original URL stays indexed and ranking signals are not passed to the destination. The difference is purely about preserving the request method.

When does the 302 vs 307 difference actually matter?

When a non-GET request is redirected. A 302 may change a POST to a GET and lose the body; a 307 guarantees the method and body survive. For plain GET page redirects the two are interchangeable.

Which should I use for a maintenance redirect?

Either works for redirecting normal page views during maintenance. If forms or API writes might be redirected too, a 307 is the safer choice because it preserves the original request.

302 vs 307

302 vs 307 redirect

A 302 and a 307 are both temporary redirects, and for an ordinary page they behave the same way in search. The split shows up under the hood, in what happens to the request method when the redirect is followed.

If you only ever redirect GET requests, the choice rarely matters. The moment a POST is involved, the difference becomes real.

At a glance

Aspect	302	307
Meaning	Found (temporary)	Temporary Redirect
Permanence	Temporary	Temporary
Preserves HTTP method	Not guaranteed; may change POST to GET	Guaranteed; method is preserved
Passes ranking signals	No	No
Typical use	Simple temporary page redirects	Temporary redirects that must keep POST data

When to use a 302

A 302 is fine for the everyday temporary redirect of a normal page, where the request is a GET and nobody is submitting a form. Browsers have followed 302s for decades, so it is the safe default for routine cases.

Because a 302 may quietly turn a POST into a GET, avoid it on endpoints that receive form submissions or API writes you do not want to lose.

When to use a 307

Use a 307 when a temporary redirect has to keep the request method and body intact, such as redirecting a POST to a form handler or an API endpoint without dropping the payload.

A 307 removes the ambiguity: the method is preserved by specification, so a POST stays a POST no matter which client follows it.

Frequently asked questions

Is there an SEO difference between 302 and 307?: Effectively no. Both are temporary redirects, so search engines treat them the same way: the original URL stays indexed and ranking signals are not passed to the destination. The difference is purely about preserving the request method.
When does the 302 vs 307 difference actually matter?: When a non-GET request is redirected. A 302 may change a POST to a GET and lose the body; a 307 guarantees the method and body survive. For plain GET page redirects the two are interchangeable.
Which should I use for a maintenance redirect?: Either works for redirecting normal page views during maintenance. If forms or API writes might be redirected too, a 307 is the safer choice because it preserves the original request.