Is a 307 redirect the same as a 302?

They're similar — both are temporary — but a 307 (HTTP/1.1) guarantees the request method and body are preserved (e.g. a POST stays a POST), whereas a 302 historically allowed clients to change the method. For SEO purposes both are treated as temporary; use a 301 for permanent moves.

When should I use a 302 instead of a 301?

Use a 302 only when the change is temporary and the original URL will return — A/B testing a page, showing a maintenance or coming-soon page, running a seasonal promotion, or routing users by location. For everything permanent, use a 301.

Do 301 redirects expire?

No, a 301 redirect doesn't expire on its own — it stays in effect until you remove it. Search engines cache 301s aggressively, which is part of why they transfer ranking so effectively.

301 vs 302 redirects: what's the difference?

A 301 and a 302 both send a visitor from one URL to another — but they tell search engines very different things. Choosing the wrong one can quietly cost you rankings. Here's the difference and when to use each.

What is a 301 redirect?

A 301 is a permanent redirect. It tells browsers and search engines that the page has moved for good, so they should update to the new URL. Crucially, a 301 passes the large majority of the original URL's ranking signals (link equity) to the destination — which is why it's the correct choice for site migrations, renamed pages, and any permanent move.

What is a 302 redirect?

A 302 is a temporary redirect. It tells search engines the original URL will return, so they should keep it indexed and not transfer ranking to the destination. Use a 302 only for genuinely temporary situations — an A/B test, a maintenance page, a seasonal promo, or geolocation routing.

301 vs 302: which should you use?

Permanent move (migration, renamed URL, deleted page pointing to a replacement) → use a 301.
Temporary change (A/B test, maintenance, seasonal, geo-routing) → use a 302.
SEO: a 301 transfers ranking equity to the new URL; a 302 generally does not (Google may eventually treat a long-lived 302 like a 301, but you shouldn't rely on it).
When in doubt for a change you expect to keep: use a 301.

Common redirect mistakes to avoid

Using a 302 for a permanent move — you lose the ranking transfer a 301 would have passed on.
Redirect chains (A → B → C) — each hop dilutes equity and slows the page; redirect straight to the final URL.
Redirecting every broken URL to the homepage — Google treats this as a soft 404 and it frustrates users; send them to the most relevant page instead.
Forgetting to update internal links — keep redirects as a safety net, but point your own links directly at the live URL.

Automate 404 recovery with Redirect Mapper

When Redirect Mapper rescues a broken URL, it sends the visitor to the closest live page and logs it as a permanent match — so you can export a clean 301 redirect map for your server or CMS rather than losing the URL to a 404 or a lazy homepage redirect.

Start free Try the free redirect map generator

Frequently asked questions

By default, no — a 302 signals a temporary move, so search engines keep the original URL indexed and don't transfer ranking to the destination. Google may eventually treat a long-standing 302 like a 301, but for anything permanent you should use a 301 explicitly to preserve link equity.