If you’ve ever migrated a website, consolidated pages, or switched from HTTP to HTTPS, you’ve dealt with redirects. And if you got them wrong, you probably watched your traffic drop off a cliff. Understanding the types of redirects in SEO is one of those foundational skills that separates technically competent site owners from those who accidentally torch their own rankings.
I’ve seen Singapore businesses lose 30-60% of their organic traffic overnight because someone implemented the wrong redirect type during a site migration. That’s not a hypothetical. It happened to an ecommerce client who came to us after their previous agency used 302s instead of 301s across 4,000+ product URLs.
Let me walk you through each redirect type, when to use it, and the specific implementation details that actually matter.
What Redirects Actually Do (At the HTTP Level)
When your browser requests a URL, the server responds with an HTTP status code. A redirect is simply a 3xx status code that tells the browser (and Googlebot) to go somewhere else instead. The critical distinction is what signal that status code sends to search engines about the permanence of the move.
Think of it like your favourite hawker stall. If Uncle Tan permanently moves his chicken rice from Stall 12 to Stall 25, you want a sign that says “moved permanently to Stall 25.” But if he’s just temporarily at Stall 25 because Stall 12 is being renovated, the sign should say “back at Stall 12 next week.” The information you give people changes how they update their mental map.
Search engines work the same way. The redirect type determines whether Google updates its index to the new URL or keeps the old one.
301 Redirect: The Permanent Move
A 301 redirect tells search engines that a page has permanently moved to a new location. This is the redirect you’ll use most often, and it’s the one that passes the highest proportion of link equity to the destination URL.
Google’s John Mueller confirmed in 2020 that 301 redirects pass full PageRank to the target URL. Before that, the SEO community operated under the assumption that roughly 10-15% of link equity was lost in the redirect. That old assumption is no longer accurate.
When to Use a 301
Use a 301 redirect in these situations:
- You’re migrating your site from one domain to another (e.g., moving from oldbrand.com.sg to newbrand.com.sg)
- You’re switching from HTTP to HTTPS
- You’re consolidating multiple pages into a single, stronger page
- You’ve changed your URL structure permanently (e.g., from /blog/post-title to /articles/post-title)
- You’re merging two websites after an acquisition
How to Implement a 301 in .htaccess (Apache)
For a single page redirect, add this line to your .htaccess file:
Redirect 301 /old-page https://www.yoursite.com.sg/new-page
For pattern-based redirects using mod_rewrite:
RewriteEngine On
RewriteRule ^old-directory/(.*)$ /new-directory/$1 [R=301,L]
If you’re on Nginx, the syntax differs. Add this to your server block:
rewrite ^/old-page$ /new-page permanent;
One mistake I see constantly: people implement 301s at the page level but forget to handle URL parameters. If your old URL had tracking parameters like ?utm_source=google, make sure those parameterised versions also redirect correctly. Screaming Frog can help you audit this.
302 Redirect: The Temporary Detour
A 302 redirect signals that the move is temporary. Search engines should keep the original URL in their index and not transfer link equity to the new destination.
Here’s where it gets interesting. Google has stated that if a 302 stays in place long enough, they may eventually treat it like a 301. But “long enough” is vague, and relying on Google to interpret your intent correctly is a gamble you don’t need to take.
When to Use a 302
Genuine use cases for 302 redirects are narrower than most people think:
- You’re running a temporary promotion page (like a CNY sale landing page) and want to redirect your homepage there for two weeks
- You’re A/B testing different versions of a page and need to temporarily route traffic
- A page is down for maintenance and you’re sending visitors to a temporary holding page
- You’re serving geo-specific content temporarily (e.g., redirecting Singapore users to a localised version during a campaign)
The key question to ask yourself: will the original URL come back? If yes, use a 302. If no, use a 301. It really is that simple.
The Most Common 302 Mistake in Singapore
I’ve audited over 200 Singapore websites in the past three years. The single most common redirect error is using 302s for permanent URL changes. This typically happens when a developer sets up redirects through a CMS plugin that defaults to 302, and nobody checks. WordPress plugins like Redirection default to 301, but some server configurations and CDN setups (particularly on Cloudflare) can introduce 302s if you’re not careful with your page rules.
Run a crawl with Screaming Frog or Sitebulb. Filter for 302 redirects. Ask yourself for each one: is this genuinely temporary? If you set it up more than three months ago and haven’t reverted it, it’s not temporary. Change it to a 301.
307 Redirect: The HTTP/1.1 Temporary Redirect
The 307 redirect is the modern HTTP/1.1 equivalent of the 302. From an SEO perspective, Google treats 307s identically to 302s. The difference is purely technical: a 307 guarantees that the HTTP method (GET, POST, PUT) is preserved during the redirect.
When You Actually Need a 307
You need a 307 in one specific scenario: when your application submits form data via POST, and you need to temporarily redirect that submission to a different endpoint without the browser converting it to a GET request.
If you’re running an ecommerce site and your payment processing endpoint temporarily changes, a 307 ensures the POST data (the customer’s order information) stays intact through the redirect. A 302 might cause some older browsers to convert the POST to a GET, losing the form data.
For standard SEO work, you will rarely need a 307. If you’re not dealing with form submissions or API endpoints, stick with 301s and 302s.
Meta Refresh Redirects: Avoid These
Meta refresh redirects are client-side redirects set in the HTML of a page. They look like this:
<meta http-equiv="refresh" content="5;url=https://www.yoursite.com.sg/new-page">
The “5” means the browser waits five seconds before redirecting. This creates a poor user experience and passes little to no link equity. Google’s own documentation recommends against using meta refreshes for SEO purposes.
The only scenario where I’ve seen meta refreshes used acceptably is on legacy systems where you genuinely cannot access server configuration. Even then, set the delay to 0 seconds rather than 5. A zero-second meta refresh is treated slightly more favourably by Google, though it’s still inferior to a proper server-side redirect.
How Redirects Impact Your SEO Performance
Link Equity Transfer
A properly implemented 301 redirect passes full link equity. This means if your old page had 50 referring domains pointing to it, those signals flow to the new URL. Get this wrong, and you’re essentially throwing away years of link building work.
Crawl Budget
Every redirect consumes crawl budget. For a small site with 200 pages, this is negligible. For a large ecommerce site with 50,000+ URLs, redirect chains (where URL A redirects to URL B, which redirects to URL C) can waste significant crawl budget. Google has confirmed they’ll follow up to 10 redirects in a chain, but in practice, every hop in the chain risks losing some ranking signal and slowing down indexing.
Page Speed
Each redirect adds latency. A single 301 redirect typically adds 100-300ms to page load time. Chain three redirects together, and you’ve added up to a full second. For Singapore users on mobile, where Core Web Vitals directly influence rankings, that’s significant.
Best Practices: What to Do Right Now
Audit Your Existing Redirects Today
Open Screaming Frog, crawl your site, and export all 3xx responses. Look for these specific problems:
- 302s that should be 301s: Any 302 older than 3 months that hasn’t been reverted
- Redirect chains: Any URL that redirects more than once before reaching the final destination
- Redirect loops: URLs that redirect in a circle (A → B → A)
- Redirects to 404 pages: The destination URL no longer exists
Map Redirects Before Migration
If you’re planning a site migration, create a complete redirect map in a spreadsheet before you touch anything. Column A: old URL. Column B: new URL. Column C: redirect type (almost always 301). Test every single redirect in a staging environment before going live.
I’ve managed migrations for Singapore businesses with 10,000+ URLs. The ones that go smoothly always have a complete redirect map prepared weeks in advance. The ones that lose traffic are the ones where someone said “we’ll sort out the redirects after launch.”
Flatten Your Redirect Chains
If URL A currently redirects to URL B, and URL B redirects to URL C, update URL A to redirect directly to URL C. This single step can recover crawl budget and reduce latency across your entire site.
Monitor After Implementation
Check Google Search Console’s Coverage report weekly for the first month after any redirect changes. Look for spikes in “Page with redirect” or “Not found (404)” errors. Set up alerts in your SEO monitoring tool so you catch problems before they compound.
Frequently Asked Questions
Does a 301 redirect pass 100% of link equity?
According to Google, yes. John Mueller confirmed that 301, 302, and 307 redirects all pass full PageRank. However, the practical reality is that a 301 is the clearest signal of permanence, so it’s the safest choice for preserving rankings long-term.
How long should I keep 301 redirects active?
Google recommends keeping 301 redirects in place for at least one year. In practice, I recommend keeping them indefinitely if possible. Old backlinks from external sites will continue pointing to the old URL for years, and removing the redirect turns those into 404 errors.
Can I redirect multiple old URLs to one new URL?
Yes, this is called consolidation. It’s a legitimate and effective SEO strategy when you’re merging thin content pages into a single comprehensive resource. Just make sure the destination page genuinely covers the topics of all the old pages, or you’ll see bounce rates spike.
Will too many redirects slow down my site?
Individual redirects add minimal latency. The problem arises with redirect chains (multiple hops) and excessive redirects on high-traffic pages. For most Singapore SME websites, redirect volume isn’t a performance concern. Redirect chains are.
Should I use a WordPress plugin or .htaccess for redirects?
For small numbers of redirects (under 100), a plugin like Redirection works fine. For large-scale migrations or pattern-based redirects, .htaccess or Nginx configuration is faster and more reliable because it operates at the server level before WordPress even loads.
Get Your Redirects Right the First Time
Redirects are one of those technical SEO fundamentals that quietly make or break your site’s performance. If you’re planning a migration, restructuring your URLs, or just want someone to audit what’s already in place, we can help.
At BestSEO, we’ve handled redirect strategies for Singapore businesses across ecommerce, fintech, and professional services. If you want a second pair of eyes on your redirect setup, book a strategy session and we’ll walk through it together.