301 vs 302 Redirects Singapore: Which One Should You Use

Quick answer: The 301 vs 302 redirects Singapore decision comes down to permanence. A 301 says the page has moved for good and transfers ranking signals to the new address. A 302 says the move is temporary, so search engines keep the original URL indexed. Choosing wrongly costs traffic.

A redirect is a rule telling a browser that the page it asked for now lives somewhere else. Choosing between the two common types takes one second and the consequences last for years. One failure we see is a site rebuild where old product URLs are redirected with the wrong type, followed by months of wondering why the rankings never transferred. We also see the opposite: a seasonal campaign page made permanent by accident, wiping a perfectly good evergreen page out of search. Neither business did anything obviously reckless. Both simply accepted whatever default their plugin or developer applied. This guide sets out what each redirect type actually does, which one is correct in the scenarios Singapore businesses genuinely face, how to implement them without creating chains, and how to verify what your site is really sending. Sites with large, changing inventories feel this most, which is why our car dealer SEO work treats redirect discipline as a weekly habit rather than a migration task.

The Difference in One Sentence, Then in Detail

When a browser requests a page, your server replies with a three-digit status code before it sends anything else. Code 200 means here is the page. Code 404 means it does not exist. Codes in the 300 range mean it has moved, and the specific number tells the requester how permanent that move is.

A 301 is Moved Permanently. You are telling browsers and search engines that this address is finished and the new one replaces it. Search engines respond by transferring the accumulated ranking signals, updating their index to the new URL, and eventually dropping the old one from results. Browsers cache the instruction aggressively, often indefinitely, so a returning visitor may never request the old address again.

A 302 is Found, commonly described as a temporary redirect. You are saying the original address is still the real one, but for now send people elsewhere. Search engines respond by keeping the original URL in the index, continuing to crawl it, and generally not transferring signals to the destination.

The practical implication of the browser caching difference deserves emphasis, because it is where the real risk sits. A 301 is very hard to undo in practice. Once a visitor’s browser has cached the permanent instruction, clearing it requires the visitor to clear their own cache, which they will never do. If there is any chance you will want the original address back, a 301 is the wrong tool regardless of what any tutorial says.

There is a related code, 307, which is a stricter temporary redirect used mainly in technical contexts involving form submissions, and 308, which is the stricter permanent equivalent. For everyday website work you will use 301 and 302. The honest summary: if the old page is never coming back, use 301. If there is any doubt, use 302 and revisit it.

What Actually Happens to Your Rankings

This is where most of the confusion lives, partly because the official position has shifted over the years and partly because old blog posts never get updated.

The historical worry was that a 301 lost a portion of a page’s ranking value in transit. Google has stated for some years now that permanent redirects pass ranking signals without a deliberate haircut. In practice, the loss people observe after a migration is almost never caused by the redirect type. It is caused by the destination.

Here is what we actually see. A page ranking for a term is redirected to a destination that does not cover that term. The signals transfer, but there is nothing relevant for them to attach to, so the ranking evaporates. The redirect worked perfectly. The mapping was wrong. Redirecting a removed product to the homepage is the classic version of this, and Google frequently treats such a redirect as a soft 404 anyway, meaning you get neither the ranking nor a clean removal.

For 302s, the position is more nuanced than the folklore suggests. Google has said that a 302 left in place long enough may eventually be treated as permanent, because the observed behaviour contradicts the stated intent. That is not a reason to be careless. The interim period is where the damage happens, and the interim can run for months. During it, search engines keep the old URL indexed while serving different content from the destination, which produces unstable, unpredictable results.

There is also a timing reality worth planning around. Even a correctly implemented permanent redirect takes time to fully process. Expect meaningful movement within a few weeks and full consolidation over one to three months on a typical Singapore SME site. Anyone who tells you a migration will hold rankings steady from day one is either lucky or not measuring. Restructured sites need time to settle too: in our interior design results work, a site restructured from a flat portfolio gallery into style and flat-type pages saw its first Japandi and Scandinavian pages reach page 1 by Month 3.

The Status Code Family Compared

The last two rows deserve a note because they still appear on Singapore sites built on older page builders. A meta refresh, which is an HTML instruction that reloads the page to a new address after a delay, is a poor substitute for a server redirect. Search engines may interpret it as permanent, temporary or as a poor user experience depending on the delay. A JavaScript redirect is worse still, because it requires the page to be rendered before the instruction is even discovered. Where a server level rule is available, use it.

Eight Real Scenarios and the Right Choice for Each

Rules in the abstract are hard to apply. Here are the situations Singapore businesses actually bring to us.

You rebuilt your website and the URLs changed. Use 301. Map every old URL to its closest genuine equivalent, one by one. This is the single highest stakes redirect job most businesses ever do.

You merged two similar service pages into one stronger page. Use 301 from the retired page to the survivor.

You are running a two-week Great Singapore Sale landing page and pointing an old campaign URL at it. Use 302. The old URL is coming back.

Your site is down for scheduled maintenance. Use neither. Use a 503 status with a retry header, which tells search engines the outage is temporary and to come back later. A redirect to a maintenance page is the wrong signal entirely.

A product is permanently discontinued and you have a direct replacement. Use 301 to the replacement product. If there is no genuine replacement, do not redirect. Let the URL return 404 or 410 and make sure the category page is easy to reach.

A product is out of stock but returning next month. Do not redirect at all. Keep the page live, state the availability clearly, and offer alternatives. Redirecting temporarily unavailable stock throws away the page’s accumulated value every season.

You are split testing two versions of a landing page. Use 302. The original is still the canonical destination and you will pick a winner later.

You moved from http to https, or consolidated www and non-www. Use 301. This is a permanent infrastructure decision and anything else leaves duplicate versions competing.

The thread running through all eight is the same test. Ask whether the original address will ever again be the correct destination. If yes, temporary. If no, permanent. Businesses with rotating promotions and treatment menus hit the seasonal cases constantly, which is why our beauty and wellness SEO engagements include a standing rule about campaign URLs.

Chains, Loops and the Hidden Cost

A redirect chain is what happens when address A redirects to B, which redirects to C. Each hop is an extra round trip before the visitor sees anything, and on a mobile connection in a lift lobby or an underground MRT station that delay is noticeable.

Chains accumulate invisibly over years. A site restructures in one year, again two years later, adds https at some point, and switches from www to non-www. Nobody ever revisits the old rules, so a single legacy URL can pass through four hops before landing. We have found chains of five and six hops on Singapore sites that have simply been in business a long time.

Three specific costs. Speed, since every hop is a full request and response cycle. Crawl efficiency, since crawlers follow a limited number of hops and may give up, and Google has indicated it follows only a handful before treating the chain as an error. Signal reliability, since long chains make it less certain that ranking signals reach the final destination intact.

A redirect loop is the pathological version: A points to B and B points back to A. The browser gives up with an error and the page is completely unreachable. Loops are usually created by two systems both trying to manage redirects, typically a plugin and a server configuration file fighting each other, or a trailing slash rule contradicting a canonical rule.

The fix for chains is flattening. Every rule should point directly at the final live destination, not at the next intermediate address. When you add a new redirect, check whether any existing rule points at the URL you are now retiring, and update those older rules to point at the new endpoint. This takes five minutes at the time and hours if left for three years. Contractor and trade sites that add and retire project pages continuously are the clearest example, and the discipline is covered in our contractor SEO work.

Implementing Redirects Without Breaking Things

WordPress. A redirect plugin is the practical route for most SMEs, and the better ones default to 301 with a dropdown to change the type. Two cautions. First, plugin redirects are processed by PHP, which is slower than a server level rule, so on sites with thousands of rules performance suffers. Second, never run two redirect plugins at once. For larger rule sets, put them in the server configuration instead.

Shopify. URL redirects are built into the admin under navigation settings and Shopify issues 301s. There is no option for a 302 through the interface, which is worth knowing before you plan a temporary campaign around it.

Wix and Squarespace. Both offer a redirect manager in settings, typically issuing permanent redirects, with bulk import available on at least one of them.

Server level, meaning Apache or Nginx. Fastest and most reliable, and the correct home for large rule sets and pattern-based rules. Requires care, because a badly written pattern rule can redirect the entire site in one line. Always test on staging.

A pattern worth using: where an entire folder structure moved, one regular expression rule is far better than 300 individual rules. Where the mapping is genuinely one to one and irregular, individual rules are clearer and safer.

Two operational rules we apply on every client project. Never deploy redirects on a Friday afternoon, because if something breaks you will discover it on Monday with two days of lost traffic behind you. And always keep a spreadsheet of every rule with the date and reason, because in three years the person maintaining the site will not be you, and an undocumented redirect is a rule nobody dares delete.

Migrations: Where the Real Money Is Lost

Site migrations are where redirect decisions stop being academic. The sequence below is the one we follow, and the order matters.

Before launch, crawl the old site completely. Export every URL that returns a 200 status. This list is your obligation.

Prioritise by value, not by position in the list. Cross reference against analytics and Search Console for the last twelve months. Any URL with organic traffic, external links or conversions is a must-map. Everything else is best effort.

Map one to one wherever a genuine equivalent exists. Where it does not, map to the closest category or parent page, never by default to the homepage.

Test on staging before launch, then again immediately after. Check a sample from each template type, not just the homepage.

Keep the rules live for a long time. Google recommends maintaining migration redirects for at least a year. Our practice is to keep them indefinitely unless there is a performance reason not to, because external links to old URLs never fully disappear.

Watch Search Console for four to eight weeks. Rising 404s or redirect errors after launch tell you which mappings were missed.

Here is the contrarian observation, and it runs against widely repeated advice. Most agencies treat the permanent redirect as the safe default and reach for it automatically. It is not safe, it is irreversible. The permanent redirect is the more dangerous of the two precisely because browsers cache it and because undoing it in the field is effectively impossible. Where the future is genuinely uncertain, a temporary redirect costs you very little in the short term and preserves your options. Reserve the permanent redirect for decisions you are certain about. Insurance and financial pages, where product content is subject to regulatory change, illustrate why these decisions need care; in our insurance results work, 6 product pages were rebuilt to a MAS-compliant educational standard in Months 1-2.

How to Check What Your Site Is Actually Sending

Assumptions are the enemy here, because the interface label and the actual status code frequently disagree.

Browser developer tools. Open the network tab, load the old URL, and look at the status column for the first request. It will show 301 or 302 explicitly.

A free redirect checker. Paste a URL and it reports every hop and every status code in the chain. This is the fastest way to spot chains.

A desktop crawler. Crawl the site and filter by 3xx status codes. This gives you the whole picture at once, including chains and loops, and is the only sensible approach above a few hundred URLs.

Search Console. The URL Inspection tool reports the final indexed URL and whether Google followed a redirect to reach it.

Run this check quarterly rather than only after a migration. Redirect rules accumulate silently through ordinary operations: a page renamed, a campaign retired, a plugin update, a developer solving a problem at speed. Multi-service and multi-brand businesses carry the largest rule sets and see the most drift over time, which is why our industry SEO work builds a redirect review into the standing quarterly checklist.

Field notes: In our ecommerce case study, a WooCommerce store carried 200+ redirect chains created by two prior platform migrations, silently leaking PageRank. Resolving them was part of the Month 1-2 technical repair, alongside a rewritten robots.txt and a clean XML sitemap, during which product indexation moved from 34% to 79%. Sites that have been through several platform changes almost always carry legacy chains worth flattening. Technical clean-up was also part of the first phase for the Sentosa property in our hotel results work, where 28 crawl errors were resolved and hotel schema deployed in Months 1-2.

Our Take

The choice between the two redirect types is not really a technical question. It is a question about whether a decision is final, and it should be answered by the person who knows the business rather than the person configuring the server. Use a permanent redirect when the old address is genuinely finished, map every URL to a destination that actually covers the same subject, and flatten your chains whenever you add a rule. Use a temporary redirect for campaigns, tests and anything you might reverse, and accept that leaving it in place for years is its own kind of mistake. Above all, resist the habit of reaching for the permanent option by default simply because it is the one everybody recommends, because it is the harder of the two to take back. If you are planning a rebuild or you suspect your redirect rules have drifted, talk to us before you launch rather than after.

We have seen the wrong choice quietly hold back a site’s authority for months after a rebrand, because someone defaulted to a temporary redirect out of caution and never revisited it. Our clients who get this right treat the redirect map as a deliverable in its own right, reviewed before launch rather than patched after. In our experience, the single biggest driver of a bad migration is not the redirect type at all, it is skipping the audit of what is being redirected from in the first place.

Frequently Asked Questions

Does a 301 redirect lose any of my ranking power?

Google has stated that permanent redirects pass ranking signals without a deliberate reduction. In practice, when a business loses traffic after redirecting, the cause is almost always a poor destination choice rather than the redirect itself. Redirecting a page that ranked for a specific term to a page that does not cover that term means the signals arrive with nothing relevant to support. Map redirects to genuine topical equivalents and the transfer generally holds.

How long should I keep redirects in place after a site migration?

At minimum a year, which is the widely cited guidance, and in our practice indefinitely unless there is a clear performance reason to remove them. External links, directory listings, old email campaigns, printed materials and bookmarks continue to point at retired URLs for many years. The cost of keeping a rule is negligible. The cost of removing one that still receives traffic is a broken experience for a real visitor.

Can I redirect all my old pages to the homepage?

You can, and you should not. Google commonly treats a mass redirect of unrelated URLs to the homepage as a soft 404 and excludes them, so you gain no ranking transfer and you lose the clean signal that a page is gone. You also deliver a poor experience, because a visitor expecting a specific product lands on a generic page and leaves. Map to the closest genuine equivalent, or let the URL return 404.

What should I use when my site is down for maintenance?

A 503 status code with a retry-after header, not a redirect. The 503 tells search engines the unavailability is temporary and that they should return later without reassessing the page. Redirecting visitors to a maintenance page with a 302 is less harmful than a 301 but still signals something you do not mean. Keep planned maintenance windows short and outside peak Singapore business hours where possible.

Are redirect chains really that damaging?

They are rarely catastrophic and they are consistently wasteful. Each hop adds a full request cycle before anything renders, which is noticeable on a degraded mobile connection. Crawlers follow only a limited number of hops before giving up, so long chains risk your destination never being reached. Since flattening a chain takes minutes and the cost accrues every single visit, there is no good argument for leaving them in place.

My plugin only offers 301. Does that matter?

For most permanent changes, no. It matters when you need a genuinely temporary redirect, such as a seasonal campaign or a split test, because a permanent redirect is cached by browsers and is difficult to reverse for visitors who have already hit it. If your platform does not expose the option, the workarounds are a server level rule or restructuring the campaign so no redirect is needed at all, for example by using a fresh URL.

Do redirects slow my website down?

Each redirect adds a round trip, which typically costs somewhere in the range of a fraction of a second per hop depending on connection quality and server response time. A single hop is rarely a problem. Chains are, and so are plugin-based redirects processed by PHP on sites with thousands of rules. For large rule sets, moving redirects to the server configuration is measurably faster than handling them at application level.

Should I redirect an out-of-stock product page?

Generally no, if the product is returning. Keep the page live, state availability clearly, and surface alternatives and related items. Redirecting throws away the page’s accumulated ranking value and you have to rebuild it when stock returns. Redirect only when the product is permanently discontinued and a genuine replacement exists. If nothing equivalent exists, let the URL return a proper 404 and make navigation to the category obvious.

What is the difference between a redirect and a canonical tag?

A redirect physically sends both visitors and search engines to a different address, so the original is no longer reachable. A canonical tag leaves the page fully working for visitors while telling search engines which version should rank. Use a redirect when the page should be gone for everyone. Use a canonical when the page still needs to function, such as a filtered product view, but should not compete in search.

How do I find every redirect currently active on my site?

Run a desktop crawler across the domain and filter for 3xx status codes, which gives you every rule, chain and loop in one export. Supplement that with your platform’s own redirect manager list and, if you have server access, the configuration file. Compare the three, because rules frequently exist in one place and not the others. Do this quarterly and keep a dated log of what each rule is for.