Choosing between a 301 vs 302 redirect seems like a small technical decision. But get it wrong, and you could quietly bleed rankings for months without realising it. I’ve seen Singapore businesses lose 30-40% of their organic traffic simply because someone set up a 302 when they meant to use a 301 during a site migration.
This guide goes deep into how each redirect type works at the server and search engine level, when to use which, and how to audit your existing redirects so nothing slips through the cracks.
How HTTP Redirects Actually Work Under the Hood
Before we compare the two, you need to understand what happens technically when a redirect fires. It’s not magic. It’s a conversation between your server and the requesting client (browser or Googlebot).
When someone requests a URL, your server sends back an HTTP status code. A 200 means “here’s the page.” A 301 or 302 means “this page lives somewhere else now, go there instead.” The server includes a Location header that specifies the destination URL.
The critical difference is in what that status code tells the client to do next, and more importantly, what Google does with the information.
What Happens at the Crawl Level
When Googlebot encounters a 301, it records that the old URL is permanently replaced. Over subsequent crawls, it consolidates all signals (backlinks, anchor text, PageRank) to the destination URL. The old URL eventually drops out of the index entirely.
With a 302, Googlebot keeps the original URL in the index. It follows the redirect to discover the content, but it treats the original URL as the canonical version. Link equity stays parked at the old URL. The destination page doesn’t inherit ranking signals in the same way.
This distinction matters enormously. If you’ve permanently moved a page but used a 302, Google is essentially holding your SEO value hostage at a URL that no longer serves content.
301 Redirect: The Permanent Signal
A 301 redirect tells search engines: “This page has moved permanently. Update your records.” It’s the redirect you’ll use 90% of the time in real-world SEO work.
How Link Equity Transfers with a 301
Google has confirmed that 301 redirects pass PageRank. In the early days, there was a widely cited claim that 301s lost about 15% of link equity. Google’s Gary Illyes later clarified that 301, 302, and 307 redirects no longer lose PageRank. However, there’s a practical caveat.
While Google says no equity is lost in the redirect itself, the consolidation process isn’t instant. I’ve tracked migrations where it took 8-12 weeks for rankings to fully stabilise after implementing 301s. During that window, you might see fluctuations. This is normal.
For a Singapore e-commerce site we worked with that was migrating from a subdomain structure to subfolders, we mapped 2,400 URLs with 301 redirects. Rankings dipped by about 12% in weeks two and three, then recovered to 103% of pre-migration levels by week ten. The key was clean, one-to-one URL mapping with zero chains.
When You Must Use a 301
- Domain migrations: Moving from yourbrand.com to yourbrand.com.sg, or consolidating multiple domains.
- HTTP to HTTPS migration: Every HTTP URL should 301 to its HTTPS equivalent.
- URL structure changes: Switching from
/products?id=123to/products/widget-name. - Merging duplicate content: Two pages targeting the same keyword should be consolidated with a 301 from the weaker page to the stronger one.
- Deleting old pages: If you remove a service page but have a relevant replacement, 301 the old URL there rather than letting it 404.
How to Implement a 301 in .htaccess
If you’re on Apache (which many Singapore shared hosting plans use), add this to your .htaccess file:
Redirect 301 /old-page https://www.yoursite.com/new-page
For Nginx servers, the syntax goes in your server block:
rewrite ^/old-page$ https://www.yoursite.com/new-page permanent;
If you’re on WordPress, plugins like Redirection or Rank Math’s redirect manager work fine for smaller sites. But for migrations involving hundreds of URLs, I’d recommend handling it at the server level for performance reasons. Every plugin-based redirect adds a database query before the redirect fires.
302 Redirect: The Temporary Signal
A 302 tells search engines: “This page has temporarily moved. The original URL will come back.” Google keeps the original URL indexed and doesn’t consolidate ranking signals to the destination.
When a 302 Is the Right Choice
Genuine use cases for 302 redirects are narrower than most people think:
- Site maintenance: You’re redesigning a page and want to send visitors to a temporary holding page for a few days.
- Geo-targeting tests: Redirecting Singapore-based visitors to a localised version of a page while you test conversion rates, with plans to revert.
- Seasonal promotions: Your
/cny-salepage redirects to a “coming soon” page outside of Chinese New Year season, then you bring the original page back. - A/B testing: Sending a portion of traffic to a variant page temporarily. Though for proper A/B tests, Google recommends using
rel="canonical"alongside the test rather than relying on 302s alone.
The common thread: you fully intend to bring the original URL back. If there’s any doubt, use a 301.
The Real Danger of Misusing 302s
Here’s where it gets painful. I audited a Singapore F&B chain’s website last year. They had migrated to a new site structure 14 months earlier. Every single redirect was a 302. Over 180 URLs, all temporarily redirected.
The result? Google was still indexing the old URLs. The new pages had almost no authority. Their organic traffic had dropped by 38% post-migration and never recovered. Switching those 302s to 301s and resubmitting the sitemap brought them back to pre-migration traffic within six weeks.
That’s 14 months of lost revenue because of a one-digit difference in a status code.
301 vs 302 Redirect: Side-by-Side Comparison for SEO Impact
Let me break this down clearly so you can reference it quickly:
Permanence: 301 is permanent. 302 is temporary.
Index behaviour: With a 301, Google replaces the old URL with the new one in its index. With a 302, Google keeps the old URL indexed.
Link equity: A 301 consolidates all link signals to the destination URL. A 302 keeps link equity at the original URL.
Canonical signal: A 301 acts as a strong canonical signal. A 302 does not.
Crawl budget: After processing a 301, Google eventually stops crawling the old URL. With a 302, Google continues crawling both URLs, which eats into your crawl budget.
How to Audit Your Existing Redirects
If you’ve never audited your redirects, there’s a good chance you have problems you don’t know about. Here’s a practical process you can follow today.
Step 1: Crawl Your Site
Use Screaming Frog (free for up to 500 URLs) to crawl your site. Filter by status code to see all 3xx responses. Export the list and sort by redirect type. Flag any 302s and ask yourself: “Is this genuinely temporary?”
Step 2: Check for Redirect Chains
A redirect chain is when URL A redirects to URL B, which redirects to URL C. Each hop adds latency and can dilute signals. Screaming Frog flags these automatically under the “Redirect Chains” report.
I recommend keeping every redirect to a single hop. If you find chains, update the first redirect to point directly to the final destination.
Step 3: Identify Redirect Loops
A loop is when URL A redirects to URL B, and URL B redirects back to URL A. This makes the page completely inaccessible. Your browser will show an “ERR_TOO_MANY_REDIRECTS” error. Google Search Console will also flag these under the Coverage report.
Step 4: Update Internal Links
This is the step most people skip. After setting up redirects, go through your site and update all internal links to point directly to the new URLs. Every internal link that hits a redirect is an unnecessary server round trip. It slows down your site and wastes crawl budget.
For WordPress sites, a search-and-replace plugin like Better Search Replace can handle this in minutes. Just back up your database first.
Step 5: Monitor in Google Search Console
After making changes, check the Pages report in Google Search Console weekly for at least a month. Look for spikes in “Page with redirect” entries or new crawl errors. If Google is still indexing old URLs after you’ve set up 301s, request indexing of the new URLs manually to speed things up.
A Quick Note on 307 and 308 Redirects
You might encounter these less common redirect types. A 307 is the HTTP/1.1 equivalent of a 302 (temporary). A 308 is the equivalent of a 301 (permanent). The difference is that 307 and 308 preserve the HTTP method (GET, POST), which matters for form submissions and API calls.
For standard SEO purposes, 301 and 302 cover virtually every scenario you’ll face. But if your Singapore site handles payment forms or API integrations, talk to your developer about whether 307/308 is more appropriate for those specific endpoints.
Frequently Asked Questions
Does Google treat 301 and 302 redirects the same for PageRank?
Google has said that all redirect types pass PageRank. However, in practice, a 302 doesn’t trigger URL consolidation in the index. So while the equity theoretically passes, the old URL remains the indexed version, which can cause ranking confusion.
How long should I keep 301 redirects in place?
At least one year, ideally indefinitely. Google needs time to recrawl and reprocess. Removing a 301 too early means anyone following the old URL (including backlinks from other sites) hits a 404.
Can I change a 302 to a 301 after the fact?
Yes, and you should if the move turned out to be permanent. Update the status code on your server, then resubmit your sitemap in Google Search Console. Expect a few weeks for Google to reprocess.
Will redirect chains hurt my rankings?
Google can follow up to 10 hops in a chain, but each hop adds latency and risks losing crawl efficiency. In practice, I’ve seen chains of just three hops cause pages to drop out of the index temporarily. Keep it to one hop.
How do I test what type of redirect is on a URL?
Use the “Network” tab in Chrome DevTools (F12, then reload the page). Look at the status code column. You can also use free tools like httpstatus.io to check multiple URLs at once.
Get Your Redirects Right the First Time
Redirects are one of those technical SEO fundamentals that either work silently in your favour or quietly erode your rankings. If you’re planning a site migration, restructuring your URLs, or just cleaning up years of accumulated technical debt, getting your 301 and 302 redirects right is non-negotiable.
If you’d like a second pair of eyes on your redirect setup, or you’re planning a migration and want to make sure nothing falls through the cracks, grab a free strategy session with us. We’ll walk through your current setup and flag anything that needs attention before it costs you traffic.