You just moved a page on your website. Maybe you renamed a product URL, merged two blog posts, or migrated your whole site to a new domain. Now you are staring at a dropdown menu that asks you to pick between a 301 and a 302 redirect, and you have no idea which one actually matters.
Pick the wrong one, and you could lose rankings you spent months building. Pick the right one and Google barely notices the change happened at all.
At Ovitech, we review redirect setups on client sites almost every week, and the 301 vs 302 redirect mix-up is one of the most common technical SEO mistakes we find. It sounds like a small detail. It is not. The type of redirect you choose tells Google whether a page change is permanent or temporary, and that single signal shapes how your rankings, link authority, and search visibility behave going forward.
This guide breaks down exactly what each redirect does, when to use one over the other, and how to avoid the mistakes that quietly cost businesses their search rankings.
What Is a Redirect and Why Does the Type Matter?
A redirect is a server instruction that sends visitors and search engines from one URL to another. When someone types in an old URL or clicks a link to a page that has moved, the redirect automatically sends them to the new location instead of showing an error.
Redirects exist for a simple reason: URLs change all the time. You rebrand. You restructure your site. You delete outdated content. Without a redirect, every one of those changes would break links, frustrate visitors, and waste the SEO value you built on that page.
But not all redirects send the same message. A redirect carries a status code, a three-digit number the server sends to browsers and search engines. That code tells them exactly what kind of change happened. This is where the 301 vs 302 redirect decision comes in, and it is the whole reason this topic deserves more attention than it usually gets.
What Is a 301 Redirect?
A 301 redirect tells browsers and search engines that a page has moved permanently. The old URL is gone for good, and the new URL is now the correct destination.
When Google sees a 301 redirect, it does something important: it transfers the SEO value, also called link equity, from the old URL to the new one. Rankings, backlink authority, and indexing signals all pass through. Over time, Google drops the old URL from its index entirely and treats the new URL as the one that matters.
Here is what a 301 redirect looks like in an .htaccess file on an Apache server:
Redirect 301 /old-page/ /new-page/
And here is the same permanent redirect set up in Nginx:
location /old-page/ {
return 301 /new-page/;
}
Use a 301 redirect any time a page change is final. If you are not planning to bring the old URL back, a 301 redirect is almost always the right call.
What Is a 302 Redirect?
A 302 redirect tells browsers and search engines that a page has moved temporarily. The implication is clear: the old URL still matters and will be used again soon.
Because a 302 redirect signals a temporary change, Google generally keeps the original URL indexed and does not transfer ranking authority to the new destination. The old page stays in the search results, keeps its rankings, and Google continues treating it as the canonical version even while visitors are being redirected elsewhere.
Here is a temporary redirect in Apache:
Redirect 302 /sale-page/ /sale-page-live/
And in Nginx:
location /sale-page/ {
return 302 /sale-page-live/;
}
A 302 redirect is the right tool when a change is short-term. Think seasonal promotions, A/B tests, or maintenance pages that will disappear once the underlying issue is fixed.
301 vs 302 Redirects: The Core Difference
The technical difference comes down to one word: permanence. A 301 redirect says "this change is final." A 302 redirect says "this is temporary, come back to the original soon."
That single distinction shapes everything else, from how search engines treat your rankings to how browsers cache the redirect.
Here is a side-by-side comparison to make the 301 vs 302 redirect SEO impact clear:
| Factor | 301 Redirect (Permanent) | 302 Redirect (Temporary) |
|---|---|---|
| Signal to search engines | Page has moved for good | Page will return, this is short term |
| Link equity transfer | Passes to new URL | Stays with original URL |
| Indexing behavior | Old URL is dropped, new URL is indexed | Old URL stays indexed |
| Browser caching | Cached long term by browsers | Not cached, checked on every visit |
| Best used for | Permanent URL changes, site migrations, page merges | A/B tests, seasonal pages, maintenance windows |
| Recovery difficulty if wrong | Hard to reverse once Google fully processes it | Easy to reverse, no lasting SEO impact |
| Typical use case | Redesigns, domain changes, deleted pages | Flash sales, geo-based redirects, server maintenance |
Keep this table nearby the next time you decide between a permanent and a temporary redirect. Most decisions come down to one honest question: is this change going to stay, or is it going to be undone in a few days or weeks?
When to Use a 301 Redirect
A 301 redirect is your default choice in the vast majority of real-world situations. Here is when it applies.
You Deleted or Merged a Page
If you combined two blog posts into one comprehensive guide, redirect the old URLs to the new consolidated page using a 301. This keeps the ranking signals from both original pages working in your favor.
You Changed Your URL Structure
Switching from /blog/post-name to /resources/post-name, or removing dates from your URLs, is a permanent structural change. Every affected URL needs a 301 redirect mapped to its new address.
You Migrated to a New Domain
Rebranding and moving from oldbrand.com to newbrand.com is one of the highest-stakes uses of a 301 redirect. Every single URL on the old domain needs an individual redirect to its corresponding new URL, not a blanket redirect to the homepage.
You Switched from HTTP to HTTPS
If your site moved from HTTP to HTTPS, every HTTP URL should 301 redirect to its HTTPS version. This is standard practice now, and Google expects to see it.
You Renamed a Product or Category
Ecommerce sites rename products and categories often. Any time a product URL changes and is not coming back to its old address, a 301 redirect protects the rankings and reviews tied to that page.
When to Use a 302 Redirect
A 302 redirect is far less common, but it has specific situations where it is genuinely the correct tool.
Seasonal Sales or Promotions
If you run a Black Friday sale page for two weeks and then remove it, a 302 redirect to your main shop page during that window keeps the original sale URL intact for reuse next year.
A/B Testing
When testing two versions of a landing page, a 302 redirect sends a portion of traffic to the variant while keeping the original page as the one Google indexes and ranks.
Site Maintenance
While performing updates or fixing a broken page, a temporary redirect to a maintenance notice or a related page keeps visitors informed without telling Google the original page is gone.
Geo-Based or Device-Based Redirects
Sending mobile users to a mobile-optimized version of a page, or redirecting visitors based on their country, often uses a 302 because the redirect logic depends on real-time conditions rather than a permanent URL change.
Limited-Time Content
A countdown page, an event registration page that closes after the event, or any content with a clear expiration date is a good candidate for a temporary redirect once it is no longer relevant.
What Happens When You Use the Wrong Redirect
This is where things get expensive. Using the wrong redirect type does not throw an error. Your site will look and function the same to a visitor. But behind the scenes, you are sending the wrong signal to Google, and the consequences show up slowly, which makes them harder to trace back to the actual cause.
Using a 302 when you meant permanent: This is the single most common mistake we see. A business redesigns their site, sets up redirects quickly using their CMS default (which is often 302), and assumes the job is done. Weeks later, rankings for the old URLs start dropping because Google is still treating those old pages as the canonical version, while traffic is quietly being sent to new pages that have no ranking history of their own.
Using a 301 when you meant temporary: This is less common but still damaging. If you 301 redirect a page for what was supposed to be a two-week sale, Google may fully transfer the rankings and drop the original URL from its index. When you try to bring the original page back, you now have to rebuild its visibility from scratch because Google no longer treats it as the primary version.
The fix in both cases is straightforward once you catch it: correct the status code and give Google time to recrawl and adjust. But recovery takes weeks, sometimes longer, and it is time you did not need to lose.
How to Check Which Redirect Type Your Site Is Using
You do not need to guess. A handful of tools will show you exactly what status code every redirect on your site is sending.
- Screaming Frog SEO Spider: Crawl your site and filter by response codes to see every 301 and 302 redirect in one place.
- Google Search Console: The URL Inspection tool shows how Google is currently treating a specific URL, including whether it sees a redirect and what type.
- Browser developer tools: Open the Network tab, reload the page, and check the status code returned for any redirected URL.
- Redirect checker browser extensions: Several free extensions display the redirect chain and status code directly as you browse.
If you inherited a website from a previous developer or agency, running a full redirect audit with one of these tools is one of the fastest ways to catch mistakes that have been quietly hurting your rankings without anyone noticing.
Redirect Chains: A Mistake That Compounds the Problem
A redirect chain happens when URL A redirects to URL B, which then redirects to URL C, instead of URL A redirecting directly to the final destination. Each additional hop in the chain adds load time and can dilute the SEO value being passed along, regardless of whether you used a permanent redirect or a temporary redirect at each step.
Redirect chains build up naturally over years of site changes if nobody audits them. A page that has been redirected three or four times through separate updates is a common finding in older websites. The fix is simple: identify the final destination URL and redirect the original URL directly to it, skipping every intermediate step.
Best Practices for Managing Redirects Long Term
Getting the redirect type right at the moment you create it is only half the job. Keeping your redirects organized over time matters just as much.
Keep a redirect map. Every time you create a redirect, log it in a spreadsheet with the old URL, new URL, redirect type, and date created. This becomes essential during future site redesigns or migrations.
Audit redirects annually. Run a crawl of your site once a year to catch redirect chains, broken redirects, or any 302 redirects that should have been converted to permanent redirects by now.
Avoid redirecting everything to the homepage. When a page is deleted and there is no direct replacement, redirect it to the closest relevant category or resource page instead of the homepage. This preserves more relevance for both users and search engines.
Test after every migration. Before and after any redesign or domain change, manually test a sample of your redirects to confirm they return the correct status code and land on the intended page.
Default to a permanent redirect unless you have a specific reason not to. If you are unsure whether a change is temporary or final, ask yourself honestly whether the old URL is coming back. If the answer is no, use a 301 redirect.
Real-World Example: Getting It Right
A mid-sized ecommerce client came to Ovitech after a site migration that used 302 redirects across the board, set up by default through their new platform's migration tool. Three weeks after launch, organic traffic had dropped by nearly a third, and their previously ranking product pages had disappeared from page one.
The fix involved auditing every redirect, converting the ones tied to permanently moved or renamed URLs to 301 redirects, and resubmitting an updated sitemap to Google Search Console. Within five weeks, most of the affected pages recovered their previous rankings, because the correct signal was finally being sent for a change that was always meant to be permanent.
This is a textbook example of why the 301 vs 302 redirects decision is not a minor technical detail. It directly determines whether your SEO equity survives a site change or gets left behind.
FAQs About 301 vs 302 Redirects
Q1: Can I use a 302 redirect and later change it to a 301?
Yes, and this is common practice. If you started with a 302 redirect because you were unsure how permanent the change would be, and it turns out to be a lasting change, update it to a 301 redirect. Google will pick up the new status code the next time it crawls the page and adjust its indexing accordingly.
Q2: Do 301 redirects hurt my SEO in any way?
A properly implemented 301 redirect does not hurt your SEO. There may be a very small, temporary dip in ranking signal during the transition as Google reprocesses the change, but this is minor and recovers quickly. The bigger risk is not using a redirect at all, which leaves visitors and search engines hitting a dead page.
Q3: How long does it take Google to process a 301 redirect?
Google typically recognizes and starts processing a 301 redirect within a few days to a couple of weeks, depending on how often the URL is crawled. Full ranking transfer, especially for high-authority pages, can take four to eight weeks to fully stabilize.
Q4: What is the default redirect type most website platforms use?
This varies by platform. Many CMS tools and page builders default to 302 redirects because it is the safer, non-destructive option from a technical standpoint. This is exactly why so many businesses end up with the wrong redirect type without realizing it. Always check and manually set the redirect type rather than trusting the default.
Q5: Should I use a 301 or 302 redirect for a website under maintenance?
Use a 302 redirect for maintenance pages. The downtime is temporary, and you want Google to keep the original URL indexed and ranking once the maintenance period ends, rather than treating the maintenance page as the new permanent destination.
Q6: Can too many redirects slow down my website?
Yes. Each redirect adds a small amount of load time because the browser has to make an additional request before reaching the final page content. This effect is minor for a single redirect but becomes noticeable with redirect chains. Keeping redirects direct, with no unnecessary hops, keeps your site fast and avoids diluting SEO value.
Q7: Do 301 and 302 redirects affect Core Web Vitals?
Redirects can impact Largest Contentful Paint (LCP) because each redirect hop delays when the browser reaches the final page content. A single, direct redirect has a negligible effect. A chain of multiple redirects can add meaningful delay, which is one more reason to keep redirect paths clean and direct.
Q8: Is a 301 redirect the same as a canonical tag?
No, though they serve related purposes. A 301 redirect physically sends visitors and search engines to a new URL, and the old URL stops being accessible as a live page. A canonical tag, by contrast, keeps both URLs accessible but tells Google which version is the preferred one for indexing. Use a 301 redirect when a page is truly moved, and a canonical tag when you want multiple accessible versions of similar content to be treated as one for ranking purposes.
