307 Redirect: A Temporary Redirect That Keeps the Method
A 307 redirect is a temporary redirect that keeps the request method, ideal for maintenance windows and short-lived moves.
307 Redirect is a temporary redirect that keeps the request method.
What It Is
A 307 redirect signals a temporary move of a URL.
It preserves the HTTP method of the original request.
Browsers and bots keep the new URL only for now.
Why It Matters
- It is honest about temporary moves.
- Search engines keep the old URL indexed.
- It preserves POST and other methods safely.
- It avoids leaking link signals on a short move.
- Clear status codes build crawl trust.
How to Do It
- Use it for maintenance and A/B windows.
- Point it at the intended temporary target.
- Send it from the server config or app layer.
- Verify it in a redirect checker.
- Recheck the URL when the window ends.
What to Avoid
- Using it for permanent moves.
- Looping redirects between URLs.
- Leaving it live for months.
- Forgetting to revert after maintenance.
- Confusing it with the older 302 behavior.
Common Mistakes
- Using 307 when 301 is correct.
- Creating redirect chains.
- Not testing with a real request method.
- Leaving seasonal redirects up forever.
- Ignoring it in logs.
Before: a checkout page goes into maintenance.
After: the team sends a 307 to a status page.
The result: the move stays temporary and reversible.
The lesson: the right code matches the real intent.
Quick Tip
Reserve 307 for genuinely temporary moves and revert it as soon as the reason is gone.
Frequently Asked Questions
307 Redirect, in Short
Temporary moves deserve a temporary status.
Let the code match how long the move will last.
Keep 301 for permanent, 307 for temporary.