Use a 301 redirect when a page has moved for good and a 302 when the move is temporary and the original URL will come back.
Use a 301 redirect when a page has moved for good, and a 302 redirect when the move is temporary and the original URL will come back. A 301 tells Google to replace the old URL with the new one in search results. A 302 tells Google to keep showing the original URL.
Getting this wrong is one of the most common technical SEO mistakes we see on site migrations. A permanent move set up as a 302 can leave the old URLs in Google’s index for months, while the new pages struggle to take their place.
The good news is that redirects are simple once you know which signal each one sends. Most sites need 301s almost all the time, and 302s only for short-term situations.
The difference between 301 and 302 redirects
Both send visitors and search engines from one URL to another. The difference is what they tell search engines about the future.
| 301 redirect | 302 redirect | |
|---|---|---|
| Status meaning | Moved Permanently | Found (moved temporarily) |
| Signal to Google | Strong signal the new URL should be canonical | Weak signal: the original URL usually stays canonical |
| URL shown in search | The new URL, once processed | Usually the original URL |
| Browser caching | Browsers can cache it, sometimes for a long time | Not cached by default |
| Use for | Migrations, merged pages, changed URLs, HTTPS and domain moves | Short promotions, maintenance, A/B tests, stock temporarily out |
Google’s documentation describes permanent redirects as a strong signal that the redirect target should be the canonical URL, and temporary redirects as a weak signal. In plain terms: a 301 says “use this new page instead”, a 302 says “send people over there for now, but keep the old page in mind”.
When to use a 301 redirect
Use a 301 whenever the old URL isn’t coming back:
- Moving a site to a new domain, or from HTTP to HTTPS
- Changing URL structure during a redesign or platform move
- Merging two pages that compete for the same topic
- Retiring a product or service page and pointing it at the closest replacement
- Moving content from a subdomain into a subfolder
A 301 consolidates signals such as links onto the new URL. Google has said that 3xx redirects don’t lose PageRank, so you don’t need to worry about a set percentage leaking away with each redirect. Our guide to PageRank explains how link value flows between pages.
When to use a 302 redirect
Use a 302 only when you genuinely want the original URL to return:
- A seasonal or time-limited campaign page that temporarily replaces a standard page
- A page under maintenance for a short period
- Sending some users to a test version of a page during an experiment
- Geo or language routing where the main URL must stay indexable
If a “temporary” redirect stays in place for months, Google may start treating it as permanent anyway. That’s not a reason to rely on 302s for permanent moves. Pick the code that matches your intent and you won’t have to wait for Google to guess.
307 and 308 redirects
These are newer equivalents. A 307 is temporary like a 302, and a 308 is permanent like a 301. The difference is technical: 307 and 308 require the browser to repeat the request with the same method, so a form submission stays a form submission. Google treats 308 like 301 and 307 like 302 for indexing.
You’ll also see 307 in browser tools when a site uses HSTS to force HTTPS. That’s the browser upgrading the request itself, not a redirect sent by your server, so it isn’t something to fix.
Common redirect mistakes
Most redirect problems we find in audits fall into a few patterns:
- 302s used for permanent moves. Often the default setting in a CMS plugin or server rule.
- Redirect chains. A redirects to B, which redirects to C. Each hop adds load time, and Googlebot stops following after a number of hops. Point every old URL straight at the final destination.
- Redirect loops. Two URLs pointing at each other, so the page never loads.
- Everything redirected to the homepage. Google can treat these as soft 404s. Redirect each old page to its closest equivalent instead.
- Internal links still pointing at old URLs. Update them to the final URL so users and crawlers skip the redirect.
- Redirects removed too soon. Keep migration redirects in place for at least a year, and longer if old URLs still get links or traffic.
How to check your redirects
Run a site crawl to list every redirect, its status code and its final destination. Filter for 302s and ask whether each one is really temporary. Then check chains, loops and redirects to the homepage.
For individual URLs, browser developer tools or any HTTP header checker will show the status code. In Search Console, the Page indexing report lists “Page with redirect” URLs, which helps confirm Google has picked up a migration. Our guide to indexability covers what those statuses mean.
If you’re planning a migration or suspect your redirects are holding pages back, our technical SEO agency can map and check them for you. Book a free strategy session to talk it through.
Related reading: our guides to log file analysis, technical SEO and SEO redirects.
Common questions
Is a 301 or 302 redirect better for SEO?
Neither is better in general. A 301 is right for permanent moves because it passes signals to the new URL and replaces the old one in search. A 302 is right for temporary moves where the original URL should stay in search.
Do 301 redirects lose link value?
Google has said that 3xx redirects don’t lose PageRank. The new URL receives the signals from the old one, as long as the redirect points to a relevant equivalent page.
How long should I keep a 301 redirect in place?
Keep it for at least a year, and longer if the old URL still has backlinks or gets visits. There’s little cost in leaving redirects in place permanently.
What happens if I use a 302 for a permanent move?
Google will usually keep the old URL in search results for longer. It may eventually treat a long-standing 302 as permanent, but using a 301 from the start avoids the delay.
