Website revamp in Singapore without losing your Google rankings

When does a Singapore company website need a revamp?

When it is slow on phones, hard to update, no longer describes what you sell, or leaks enquiries through broken forms and dead ends. Age alone is not the trigger; a ten-year-old site that loads fast and converts may only need a tidy-up.

The signs we see most often on Singapore SME sites are practical ones. The site was built by someone who has since left, so nobody can change a price without breaking the layout. A page builder theme takes several seconds to show anything on a mobile connection. Service pages still list products the company stopped selling years ago. The contact form emails a mailbox nobody reads. The footer still shows an old address from before the move to a new business park. The privacy notice predates the company's current use of analytics and marketing tools.

Business changes are the other trigger. New services, a merger, a rebrand or a shift from B2C to B2B selling all make the old structure wrong, not just the old look. A website revamp in Singapore is worth doing when those changes mean your best prospects cannot find the page that answers their question.

• Mobile pages take several seconds to show the main content
• Staff avoid editing the site because things break
• Services, prices or addresses are out of date
• Enquiries have dropped while traffic has not
• The platform limits what you can do, such as on an old Wix plan
• Forms and privacy wording no longer match how you use data

Website revamp, redesign or rebuild: what is the difference?

A redesign changes how the site looks, a rebuild changes what it is built on, and a revamp is the broader job that can include both plus content, structure and SEO protection. In Singapore the word “revamp” is often used for all three, so it pays to be clear about which one you are buying.

A redesign keeps the platform and most of the content and gives it a new visual layer. It is quicker and cheaper, and the SEO risk is low as long as URLs stay the same. A rebuild moves the site to new technology, say from Wix to WordPress or from an old WordPress theme to a custom static site. It fixes speed and ownership problems but changes code and often URLs, which is where rankings get lost if nobody maps redirects.

A full website revamp combines the rebuild or redesign with a content audit, a new page structure where the business has changed, updated forms and privacy wording, and a migration plan. That is what this page describes. If your only problem is appearance and the site is otherwise fast and well organised, tell us; a lighter redesign may serve you better, and we will quote that instead.

How do you build a URL inventory before a website revamp?

Collect every URL the old site has from four sources, merge them into one sheet and record traffic, links and enquiries against each. The inventory is the single most important document in a website revamp, because any URL missing from it will not get a redirect.

The first source is a full crawl of the live site, which finds everything currently linked. The second is Search Console, which shows pages Google knows about and the queries each one earns, including old pages no longer linked from your menus. The third is your analytics, which reveals landing pages that still receive visitors from bookmarks, emails or ads. The fourth is backlink data, because an old event page or press release linked from a news site or directory still passes value even if nobody on your team remembers it exists.

Singapore company sites often have surprises in that merged list: promotion pages from past Great Singapore Sale campaigns, PDF brochures indexed individually, old job postings, and duplicate URLs with and without “www” or trailing slashes. Each gets a row. For every row we record clicks, impressions, sessions, form submissions and linking domains, which tells us what matters and what can safely retire.

• Crawl of the live site, including PDFs and images that rank
• Search Console performance and indexing exports
• Analytics landing page report for the last 12 to 16 months
• Backlink list showing which old URLs other sites point to
• Any URLs used in printed brochures, QR codes or email signatures

How should 301 redirects be mapped in a website revamp?

Map each old URL to the single new page that best replaces it, use permanent server-side redirects, and keep them in place for at least a year. Sending everything to the home page throws away the relevance each old page earned.

Google's guide to site moves with URL changes recommends permanent HTTP redirects such as 301 or 308, advises keeping redirects for as long as possible and generally at least one year, and warns against long chains of redirects. It also notes that for medium-sized sites it can take a few weeks or more for Google to show the new URLs in place of the old ones. Those are the rules our redirect map follows.

In practice the map has three kinds of rows. Direct matches, where an old service page becomes the new version of that service page. Merges, where three thin articles combine into one stronger guide and all three old URLs point to it. And retirements, where a page has no modern equivalent; if it had links or traffic, it redirects to the closest relevant section, and if it had neither, it can return a proper 404 or 410 rather than a misleading redirect. Before launch we run the whole map against the staging site; after launch we test every row on the live domain.

What does a content audit decide during a website revamp?

It decides what happens to every page: keep, rewrite, merge or retire, based on evidence rather than taste. The audit stops a revamp from deleting the pages that quietly bring in your best enquiries.

We score pages on four questions. Does it earn search traffic, and for which queries? Does it lead to enquiries, calls or WhatsApp clicks? Does it describe something you still sell, accurately? And is it the only page on its topic, or one of several competing with each other? A page that ranks and converts is kept, with light edits and the same URL where possible. A page that ranks but misleads, such as one quoting an old service scope, is rewritten while keeping its focus. Several weak pages on the same topic are merged. Pages with no traffic, no links and no business purpose are retired.

This is where many website revamps in Singapore go wrong. A new designer shortens every page to fit a clean template, and the detailed paragraphs that answered buyers' questions disappear, along with the rankings they earned. We keep the substance and fix the presentation: better headings, answer-first openings, tables for comparisons, and clearer calls to action, which also makes pages easier for AI search features to quote, a topic covered on our AI SEO services page.

Can you move a Singapore website off Wix during a revamp?

Yes, but it is a rebuild rather than an export. Wix's own help centre says that since Wix is a SaaS solution, a site must run on Wix's servers, so the content, images and structure have to be recreated on the new platform.

Many Singapore SMEs start on Wix because it is quick, then outgrow it: they want faster pages, more control over SEO details, integrations with booking or accounting systems, or simply to stop paying for a platform they cannot take with them. When we move a site off Wix, we copy every page's text and media, rebuild the design on WordPress or a lean custom site depending on how often you edit, and recreate the URL structure where it makes sense.

The part people miss is redirects. Once the domain points to the new host, Wix's own redirect settings stop applying, so every old Wix URL, including its blog and product paths, must be redirected on the new server. Email is the other trap: if your domain's email is set up through the same provider, we map the DNS records before switching so staff mailboxes keep working. The domain itself stays registered in your name throughout, and if it is currently registered through Wix, we walk you through transferring it to a registrar account you control.

How do you fix a slow WordPress site as part of a revamp?

Usually by replacing the heavy theme and page builder, removing plugins that do little, and serving pages from good hosting with proper caching. Keeping WordPress is often right; keeping the bloat around it rarely is.

Slow WordPress sites in Singapore tend to share a pattern. A multipurpose theme bought years ago loads sliders, animation libraries and several font families on every page. A page builder wraps each paragraph in layers of markup. Twenty or thirty plugins overlap, some abandoned by their authors. Images are uploaded straight from a camera. Hosting is a cheap shared plan in a distant data centre.

In a revamp we move content into a lean theme or a custom block theme, keep only the plugins you actually use, compress and resize images at upload, and set up caching. We also look at where the server sits: for a Singapore audience, hosting in or near the region usually helps response times, and major cloud providers operate data centres in Singapore. If the site is mainly brochure content that rarely changes, we may suggest a static build instead, which is faster and has fewer parts to maintain. Our WordPress website design page covers new WordPress builds in more detail.

What Core Web Vitals targets should a website revamp meet?

Aim for Google's “good” thresholds on your main templates: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. Those figures come from Google's Core Web Vitals documentation.

We measure the old site first, template by template: home page, a service page, a blog post, a contact page and, for stores, a category and a product page. That gives a baseline you can compare against after launch. During the build, each template is tested on a mid-range phone profile, because desktop scores flatter almost every site.

The usual fixes are unglamorous. Serve images in modern formats at the size they are shown. Reserve space for images, banners and embedded maps so the layout does not jump. Load chat widgets, review carousels and tracking scripts after the main content, or only after cookie consent. Replace heavy sliders with a single strong image. Field data in Search Console takes weeks to reflect real visitors on the new site, so we check lab results at launch and review the field report once enough data has built up.

Should a website revamp update the PDPA notice and forms?

Yes. A revamp is the cheapest moment to fix forms and privacy wording, because every form is being rebuilt anyway. Singapore's Personal Data Protection Act includes obligations on notification, consent and protection of personal data, and old forms often collect more than they need.

Typical findings on older Singapore sites: an enquiry form asking for NRIC numbers or dates of birth it never uses, marketing consent bundled into a required checkbox, analytics and advertising pixels firing before any choice is offered, and a privacy notice written before the company started using its current tools. During the revamp we remove unneeded fields, separate marketing consent into its own unticked box, record what each person agreed to, and place analytics and ad scripts behind a cookie preference panel.

We do the technical work; the wording is not ours to decide. Your lawyer or data protection officer approves the privacy notice and consent text, and we publish exactly what they sign off. For a deeper look at privacy features, see our PDPA compliant website guide. Whether your organisation meets its PDPA obligations overall is a question for your own counsel, not something a website build can certify.

How much does a website revamp cost in Singapore?

With BtechWaleTech, a website revamp starts at US$150 for a company site of up to 100 pages, US$300 for large content sites and US$750 for online stores. Quotes from other providers vary widely, and the gap usually comes from how much of the migration work is actually included.

Five things move the price. Page count and how many templates the site needs. Whether content is carried over, rewritten or newly written. The platform change: moving off Wix means rebuilding everything, while staying on WordPress may keep much of the content in place. Integrations such as booking systems, CRMs or accounting tools. And the size of the redirect map, since a store with thousands of product URLs needs far more mapping and testing than a twenty-page service site.

Quotes are in USD. You pay by Wise, including from an SGD balance, or by bank wire, and you see every line before anything is billed. When comparing quotes from Singapore providers, check whether each one includes the URL inventory, the redirect map, post-launch monitoring and PDPA form updates; a cheaper quote without them can cost more in lost enquiries. Our website design cost guide for Singapore covers new builds.

How long does a website revamp take?

A company site of up to 100 pages typically takes two to three weeks from approved content to launch; content-heavy sites take three to five weeks and online stores four to eight. The inventory and content decisions at the start often take as long as the build itself.

The first week goes to the inventory, content audit and structure. Design follows, usually one round of layout for key templates, then revisions. The build runs in parallel with content edits, on a staging site you can review from Singapore at any hour. The final week covers redirect testing, form testing, speed checks and your sign-off.

What slows projects down is almost always content and approvals: missing photos, service descriptions waiting on a department head, legal review of the privacy notice. We flag those dependencies in the first week so they do not block launch. For a company with a trade show or product launch date, we plan backwards from that date and say plainly if it is not realistic.

What should happen in the eight weeks after a website revamp launches?

Close monitoring: redirect checks, Search Console coverage and performance, form deliveries and speed. Most problems after a revamp are small and fixable if spotted in the first days, and expensive if found a month later.

On launch day we switch DNS, confirm HTTPS, test every redirect in the map on the live domain, submit the new sitemap in Search Console and check that robots.txt is not still blocking the site from the staging phase, a mistake that is more common than anyone admits. Forms are tested end to end, including confirmation emails and WhatsApp buttons.

Over the next weeks we watch Search Console for 404 errors on old URLs we missed, pages dropping out of the index, and changes in clicks for the queries that mattered in the inventory. Google's site move guidance explains that temporary ranking changes are normal while it processes new URLs, so the goal is to spot anything that is not temporary. Any missed URL gets a redirect the same day. The two months of free maintenance that follow launch cover these fixes, and ongoing care is described on our website maintenance page.

Working on a website revamp with a team in India from Singapore

India is two and a half hours behind Singapore, so our working day covers your afternoon and evening: 9:30 am in India is noon in Singapore. Staging links let you review progress whenever suits you, and WhatsApp replies come seven days a week in IST hours.

The first two weeks of a revamp look like this. In week one we collect access to your current site, Search Console, analytics, domain and hosting, run the crawl and build the URL inventory. A 45-minute video call in your afternoon walks through the content audit and the proposed page structure. In week two you approve the structure and the first design, and we start building on staging while your team finalises any new copy.

Everything stays yours. The domain remains registered in your name, hosting sits in your account, and you receive all code and logins at handover. We do not visit your office; photography and anything physical are handled on your side. Quotes are in USD and invoices come from India, payable by Wise or bank wire, with nothing billed before you approve the written quote. Contract terms are set out in that quote and our terms.

What are the biggest risks in a website revamp?

Lost redirects, lost content, a staging block left in place, and broken forms. Each can cost months of rankings or weeks of enquiries, and each is preventable with a checklist and a few hours of testing.

Other risks are commercial. A revamp that changes your service names to match a new brand can quietly abandon the words customers actually search for. A new design that hides phone numbers and WhatsApp buttons behind menus can cut enquiries even while traffic holds. Moving hosts without mapping email DNS can take staff mailboxes offline on launch day. And a provider who keeps the new site on their own hosting account can make you dependent on them for every future change.

• No URL inventory or redirect map in the proposal
• Plans to redirect every old page to the home page
• Robots.txt or noindex from staging left on the live site
• Content shortened to fit a template, losing the text that ranked
• Domain or hosting registered in the provider's name
• No post-launch monitoring period included

If a previous revamp already caused a drop, the inventory can still help: old URLs in Search Console and backlink data can be redirected after the fact, and some lost ground often returns once they resolve properly.

Website revamp Singapore checklist

Keep this list beside any website revamp proposal you receive in Singapore. If a provider cannot say how they handle each item, ask before signing.

• Full URL inventory from crawl, Search Console, analytics and backlinks
• One-to-one 301 redirect map, tested on staging and on launch
• Content audit with keep, rewrite, merge or retire decisions
• Baseline Core Web Vitals measured before the build
• Forms rebuilt with only necessary fields and separate marketing consent
• Privacy notice updated and approved by your counsel
• Analytics and ad tags behind a cookie preference panel
• Domain, hosting and all accounts in your company's name
• Email DNS records mapped before the switch
• New sitemap submitted and robots.txt checked on launch day
• Eight weeks of monitoring for 404s, index changes and form delivery

Worked example: revamping a Wix site for a Singapore logistics firm

Imagine a freight forwarding company in the Paya Lebar area with a Wix site built eight years ago. This is a hypothetical example to show how a website revamp in Singapore is sequenced, not a real client.

The inventory finds 140 URLs: 25 service and industry pages, 60 blog posts, a set of old promotion pages, PDF rate cards and a careers section. Search Console shows most enquiries come from a handful of service pages about sea freight and customs clearance, plus a few blog posts answering import questions. The rest earn almost nothing.

The revamp keeps and improves the service pages, merges 60 blog posts into about 15 thorough guides, retires the promotion pages with redirects to the matching services, and replaces the PDF rate cards with a quote request form. Because Wix cannot be exported, the site is rebuilt on WordPress with a lean theme. Every Wix URL, including the unusual blog paths, is mapped to its new page. The enquiry form drops fields the sales team never used and gains a separate marketing opt-in. The whole job falls in the US$300 range because of the page count. After launch, Search Console is watched for eight weeks; a handful of missed old URLs are redirected in the first days, and the company's team now updates rates themselves without calling anyone.