Technical SEO
301 vs 302 Redirects: Which One to Use and When
By Shayan Ahmad · · 6 min read

A redirect sends someone, and a search engine, from one URL to another. The status code you choose tells them whether that move is permanent or temporary. In practice, most site owners need a simple rule: use a 301 when the old address is gone for good, and a 302 when you honestly expect to use it again. Getting that wrong, especially by leaving a temporary redirect in place for months, is one of the more common technical mistakes I see after a redesign or a campaign.
This guide is for site owners who need to choose the right redirect without getting lost in edge cases. It covers what 301 and 302 mean, when to use each, and how to check that the live site is doing what you think it is.
What 301 and 302 Actually Mean
A 301 is a permanent redirect. It says the resource has moved for good, and that the new URL should be treated as the replacement. Browsers cache it, and search engines treat the new address as the one to index and to associate with the old URL's signals, in the usual case.
A 302 is a temporary redirect. It says the move is for now, and that the original URL may come back. Search engines are more likely to keep the original address in the index, or at least to treat the destination as a stand-in rather than the new permanent home. Browsers may also cache a 302 less aggressively than a 301, depending on the headers that come with it.
There is also 307 and 308, which are similar in intent, with stricter rules about the HTTP method. For most site-owner decisions, the useful split is still permanent versus temporary. If your platform only offers "permanent" and "temporary", think 301 and 302.
Use a 301 When the Move Is Permanent
Choose a 301 when you do not intend to bring the old URL back as the main address. Typical cases include:
- A page or product has been replaced, and shoppers should land on the new URL from now on.
- You have changed a slug, a folder, or the whole site structure.
- You have moved to a new domain, or consolidated HTTP and HTTPS, or www and non-www.
- You have merged two pages, and the weaker one should not remain in the index.
Once the 301 is in place, update your internal links, canonical tags and sitemap so they point at the new URL. The redirect is a safety net for old bookmarks and backlinks, not a substitute for a tidy site. This is standard work in our technical SEO service, especially after a relaunch.
Do not 301 everything to the homepage because it is quicker. A permanent redirect should go to the closest useful replacement. A homepage dump is confusing for people and is often treated poorly by Google, sometimes as a soft error rather than a genuine relocation.
Use a 302 When the Change Really Is Temporary
A 302 is the right tool when you will need the original URL again, or when you are not ready to declare a permanent move. Sensible uses include:
- A short test, such as sending some traffic to an alternate layout while you compare it.
- A page that is briefly unavailable, with a clear plan to restore it, if you cannot keep a holding page at the original URL.
- A seasonal or promotional path that should not replace the evergreen page in the index.
- A temporary maintenance or geolocation stand-in, used with care and not as a disguise.
The important word is temporary. If a "campaign" redirect has been sitting there for a year, it is a 301 in all but name, and you should probably convert it. Leaving a long-lived 302 in place can delay or confuse the transfer of signals, so the new URL struggles to settle in the index. I would rather see a 301 you meant, than a 302 you forgot about.
How to Choose When You Are Unsure
Ask one question: if someone bookmarks the destination, should that bookmark still make sense in a year? If yes, and the old URL is retired, use a 301. If the original address is the one you want people and Google to keep using, keep that page live, or use a 302 only for a short, dated period.
A few extra checks help:
- Look at the URL in Search Console. If you want the new one to be the indexed page, a 301 is the usual choice.
- Check what your server or platform is actually sending. Some tools label a redirect "permanent" in the admin and still serve a 302. Confirm with a header check, not only with the settings screen.
- Avoid chains. If you need a 301 to a new path, point the old URL there directly, not through an intermediate address that is itself a 302.
- Keep a simple record of what you redirected, when, and why, so the next person does not treat a temporary rule as sacred.
If you are in the middle of a redesign or a domain change, decide the code as part of the URL map, not as an afterthought on launch day. Our SEO audit work often finds the wrong code still in place months later, and it is one of the practical points we raise when comparing technical SEO approaches to migrations. When the move includes a new front end, it should also be in the web design and development plan, not left to a last-minute plugin setting.
What About Visitors, Caching and Ads?
People hitting an old link should reach the right page quickly, with one hop. A 301 is usually cached, which is helpful once the move is permanent, and inconvenient if you picked it too soon and then need to reverse it. That is another reason not to use a 301 for a two-day test.
If you run ads or email campaigns to a URL, make sure the address in the campaign is the one you want to keep, and that any redirect in front of it is deliberate. Campaign short links can hide a 302 you never meant to leave in front of a landing page.
FAQs
Will a 301 always transfer rankings to the new URL?
A 301 is the standard way to say the new URL is the replacement, and in most cases the signals move across. The closer and more useful the destination, the more reliable the result. It is not a way to rescue a weak page by pointing it at an unrelated one.
Can I change a 302 to a 301 later?
Yes, and you should if the move has become permanent. After you change it, update internal links and give Search Console time to see the new signal.
Is a meta refresh or JavaScript redirect as good as a 301?
No. Use an HTTP redirect wherever you can. Page-level refresh techniques are slower, less reliable for search engines, and harder to maintain.
Should I use a 301 for HTTP to HTTPS?
Yes. A protocol change is a permanent move. Every HTTP address should 301 to its HTTPS equivalent in one hop, and your internal links should already use HTTPS.
Not Sure Which Redirect Your Site Is Using?
If pages moved months ago and you still see the old URLs in Search Console, or you suspect a temporary redirect was left in place, a header check and a short map will settle it. Start with a free SEO audit and we will tell you which redirects should be permanent, and which ones should not be there at all.
- redirects
- 301
- 302
- technical seo
- migrations
Have a question about this for your own site?
A 15-minute call is usually enough to tell whether it applies to you and what to do first.


