307 Redirect
In one line
A 307 redirect is the HTTP/1.1 temporary redirect — unlike 302, it preserves the original request method (GET, POST, etc.) instead of silently switching to GET.
Going deeper
A 307 carries the same 'this resource has temporarily moved' meaning as a 302, but with one important guarantee: the client must keep the original HTTP method. 302 ended up ambiguous because browsers historically downgraded POST to GET; 307 was introduced to remove that ambiguity.
From an SEO standpoint the effect is essentially the same as a 302. Search engines treat it as temporary and keep the original URL as the indexed canonical, so anything that is genuinely a permanent move should use 301 or 308 instead.
In practice 307 most often shows up automatically — HSTS-driven HTTPS upgrades and some load balancer defaults emit them. So when an audit flags a 307, the question is usually 'is this intentional or just an infra default?'.
Related terms
302 Redirect
A 302 redirect tells engines that a URL is temporarily redirected — search engines keep indexing the original URL rather than transferring signals to the destination.
SEO308 Redirect
A 308 redirect is the modern permanent redirect — same long-term meaning as 301, but it preserves the original request method instead of forcing GET.
SEO301 Redirect
A 301 redirect is the HTTP status code that says a URL has moved permanently — passing essentially all of the original page's link equity to the new URL.
SEOHTTP Status Codes
HTTP status codes are the standard server responses (200, 301, 404, 500 and so on) that tell crawlers how to treat a request — and in SEO they directly steer indexing decisions.
SEORedirect Chain
A redirect chain is when a URL has to pass through two or more redirect hops before reaching its final destination — costing crawl budget, page speed and a slice of link equity along the way.