The Website Redesign Checklist for Singapore Businesses (2026)

Last updated: 13 August 2026. Written by Adrian Tan, Singapore Digital Marketing (SDM).

The most expensive week in a Singapore SME’s marketing year is often the week after a website relaunch. The new site looks sharper, the team is pleased, and then the enquiries go quiet. Nothing dramatic broke. What happened is that a hundred small decisions — a tidier URL structure, a page that “wasn’t getting traffic anyway”, a form that now posts somewhere else — each shaved a little off, and together they took out the channel.

A redesign does not have to work that way. Handled properly it is one of the few marketing projects where you can lift conversion and rankings at the same time. Handled casually it is a self-inflicted traffic loss you then pay an agency to recover. This checklist is the sequence we run: what to decide before you start, what to capture before anything changes, what to do on staging, the redirect work that carries most of the risk, launch day, and the thirty days after.

It sits under our guide to web design in Singapore, and pairs with the deeper technical treatment in website migration and SEO.

First question: do you actually need a redesign?

“The site looks dated” is a reason to change the design. It is not, on its own, a reason to rebuild the site. Rebuilding replaces the URLs, the templates, the content and the tracking all at once, which is why it carries the risk it does. Before committing, work out which of three things you actually need.

Five diagnostics settle it quickly:

1. Does it pass Core Web Vitals? Check real-user data in Search Console. The “good” bands are 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint and 0.1 or less for Cumulative Layout Shift, at the 75th percentile. Failing these is usually a fix, not a rebuild.
2. Is it losing people on mobile specifically? Compare mobile and desktop conversion rates in GA4. A large gap is a layout and speed problem.
3. Can you add a page without asking a developer? If not, the platform is the problem and a rebuild may genuinely be justified.
4. Does the structure match what people search for? One “Services” page covering six services will keep underperforming no matter how it looks.
5. Has the business changed? New markets, new audience, a repositioning — that is a content and structure problem, and it is the strongest case for a rebuild.

If your honest answers point at one or two of these, buy the fix. It is cheaper, faster, and it does not put your existing rankings on the table.

Phase 0: capture the baseline before anything changes

This is the step teams skip, and it is the one that makes every later decision arguable instead of provable. Before a single page is touched, capture:

• A full crawl of the current site — every URL, its title, meta description, H1, status code and word count. This becomes the source list for your redirect map.
• Search Console exports — queries, pages, clicks and impressions for the last 12 months. Sort by clicks; the top 20–50 pages are the ones you must not break. If Search Console is not set up, fix that first: see Google Search Console setup.
• GA4 benchmarks — sessions, conversions, conversion rate and top landing pages, by month, so you can tell a redesign dip from normal seasonality. Our list of the GA4 reports worth checking covers the ones that matter.
• Your current rankings for the keywords that matter commercially.
• An inventory of everything that is not a page: PDFs, images that earn traffic, the sitemap, robots.txt rules, tracking tags, third-party embeds, booking widgets and any form integrations.

Print the top-pages list and pin it up. Every proposal to delete a page gets checked against it.

Phase 1: decide the structure before the design

Sitemap first, wireframes second, visual design third. Reversing that order is how sites end up with beautiful pages that nobody searches for.

Take the crawl and sort every existing URL into one of four buckets: keep the URL as is, keep the content at a new URL, merge into another page, or retire. The default should be to keep URLs unchanged. Changing a URL buys you a tidier address and costs you a redirect, a small amount of signal and a chunk of risk — only do it where the structure is genuinely wrong.

Two traps to avoid at this stage. First, merging several ranking pages into one “better” page is a real strategy but it must be deliberate, because you are consolidating on purpose rather than creating duplicate content problems. Second, retiring old blog posts because they look dated destroys accumulated ranking value; update them instead, or merge them into a stronger page and redirect.

Phase 2: build on staging, and keep staging out of the index

Build on a staging environment protected by HTTP authentication. Password protection is the reliable method; a noindex tag or a robots.txt disallow is easy to leave switched on at launch, and that mistake removes your entire new site from Google. Add “remove staging protections, confirm production is indexable” to launch day as an explicit, ticked step.

While on staging, get these right:

• Titles, meta descriptions and H1s carried across for every kept page — do not let a new CMS auto-generate them.
• Structured data rebuilt, not lost in the move; see schema markup for Singapore businesses.
• Images compressed and correctly sized before launch, with dimensions set so nothing shifts as the page loads.
• Analytics and conversion tracking installed and tested on staging, not added afterwards — see GA4 setup and conversion tracking.
• Every form submitted end to end, with a real submission arriving in a real inbox and CRM. Test the autoresponder too.

Phase 3: the redirect map (where most redesigns are won or lost)

If you do only one thing from this article properly, make it this. Google’s own site move documentation is explicit: use server-side permanent redirects (301 or 308) where technically possible, avoid chaining redirects beyond a few hops, update internal links to point at the new URLs rather than relying on the redirects, submit a sitemap of the new URLs, and keep the redirects in place for at least a year — indefinitely is better.

The mechanics, in order:

1. One row per old URL. Old URL, new URL, why. No blanks.
2. Map to the closest equivalent page, never to the homepage in bulk. A mass redirect of retired pages to the homepage is treated as a soft 404 and throws away the signal you were trying to keep.
3. 301, server-side. Configure at the server or CDN where you can. A CMS plugin will work but adds a hop and latency.
4. No chains. If old A once pointed to B and B is now C, point A straight at C.
5. Cover the non-HTML assets too — PDFs, and any image URLs that earn traffic.
6. Test every row against the staging or live environment before launch, and again in the hour after go-live. Every row, not a sample.

Phase 4: launch day

Do it on a Tuesday or Wednesday morning, when the people who can fix things are awake and available — not late on a Friday. Work through this in the first hour:

• Remove staging password protection; confirm the live site is indexable (no stray noindex, robots.txt not disallowing everything).
• Spot-check status codes: key pages return 200, old URLs return 301 to the right destination, a genuinely missing page returns 404.
• Confirm HTTPS everywhere and no mixed-content warnings.
• Submit the new XML sitemap in Search Console, and use the Change of Address tool if the domain itself changed.
• Fire a test conversion on each form and check it arrives.
• Confirm GA4 is recording real-time traffic and that conversion events fire.
• Check the pages on an actual phone, on mobile data, not office wifi.
• Confirm your Google Business Profile links to a live page, not a retired one — see local SEO in Singapore.

Phase 5: the first 30 days

Expect movement, and know what normal looks like. Google states plainly that temporary fluctuation is expected during a move and that a medium-sized site can take a few weeks for most pages to be reindexed. So a modest dip that recovers over two to four weeks is the system working. A steep, sustained drop is a defect, and almost always a redirect, an indexability setting or a lost page.

Watch weekly, not hourly:

• Search Console coverage — indexed count on the new sitemap rising, old URLs falling. Fix any spike in 404s or “excluded” pages immediately.
• Top-page comparison — your printed pre-launch top-20 list against current clicks. Any page that lost most of its traffic gets investigated individually.
• Core Web Vitals — field data takes 28 days to fully reflect the new site, so judge speed at the end of the month, not on day two.
• Conversion rate, not just sessions. A redesign that trades 10% of traffic for a better conversion rate can still be a win; you can only see that if you tracked both.

The Singapore-specific items

Four things belong on a local checklist that generic redesign advice will not mention:

• PDPA housekeeping. Carry across your privacy policy, keep it linked from the footer and from every form, and make sure your Data Protection Officer’s business contact stays publicly findable. A redesign that quietly drops the DPO contact creates a compliance problem, not just a missing link. The tracking-side detail is in PDPA and marketing tracking.
• Consent that matches your new tag stack. If the rebuild adds advertising or cross-site tracking pixels, the consent mechanism has to cover them.
• The NRIC authentication deadline. In February 2026 the PDPC set out that private organisations must stop using NRIC numbers for authentication by 31 December 2026. If your old site had a portal or booking flow that verified users by NRIC, the rebuild is the moment to replace it. Check the primary PDPC source for the final wording before scoping.
• Local trust signals. Keep your UEN, physical address and phone number consistent with your Google Business Profile and directory listings. Address and phone mismatches introduced during a redesign quietly undermine local rankings.

Add one more item to that Singapore list, because a redesign is exactly where it goes missing: the footer. Rewriting a footer is how a registered company name, a UEN, a data protection contact and a GST statement quietly disappear from a site that had them. We set out which of those are actually required, and by whom, in what Singapore law actually requires on your website — run it as a launch-day check.

What a redesign costs

A redesign is usually priced like a new build, because it largely is one, plus migration work. Singapore market ranges in 2026 run roughly S$1,500–S$5,000 for a standard SME site, S$4,500–S$15,000 for a professional build with discovery, custom design and copy, and S$8,000–S$20,000 for e-commerce. Add the redirect mapping and testing, which is real work rather than a free extra on a site of any size. The full breakdown is in how much a website costs in Singapore.

If the build is bought as a pre-approved PSG solution and your company is eligible, support of up to 50% of qualifying cost applies within the S$30,000 per company per financial year cap — applied for by you, through the Business Grants Portal, before any deposit is paid. Ad spend and ongoing retainers are generally not claimable.

The one-page checklist

1. Crawl the current site and export every URL.
2. Export 12 months of Search Console queries and pages.
3. Record GA4 sessions, conversions and conversion rate by month.
4. Record current rankings for commercial keywords.
5. Print the top 20 pages by clicks. Protect them.
6. Decide: refresh, targeted fix, or rebuild.
7. Agree the sitemap before any design work starts.
8. Bucket every URL: keep, move, merge, retire.
9. Default to keeping URLs unchanged.
10. Build on password-protected staging.
11. Carry titles, meta descriptions, H1s and schema across.
12. Compress and size images; set dimensions to prevent layout shift.
13. Install and test GA4 and conversion tracking on staging.
14. Submit and receive a real test submission from every form.
15. Build the redirect map: one row per old URL, no blanks.
16. 301, server-side, no chains, no mass homepage redirects.
17. Update internal links to point at final URLs.
18. Launch mid-week, in the morning.
19. Unblock indexing; verify status codes, HTTPS and forms live.
20. Submit the new sitemap; watch coverage, top pages and conversion rate for 30 days.

Where to go next

• Web design in Singapore: the full guide — the hub for this cluster.
• How much a website costs in Singapore — budget bands and cost drivers.
• Website migration and SEO — the deeper technical treatment of URL moves.
• Technical SEO basics — crawlability, indexation and speed.
• Case studies — results from other Singapore businesses.

The bottom line

A redesign is a migration wearing a nicer outfit. The design work is the visible part; the value is protected or destroyed in the unglamorous parts — the baseline you captured, the URLs you chose not to change, the redirect map you tested row by row, and the thirty days you spent watching afterwards. Do those four things and a redesign is one of the highest-return projects available to a Singapore SME. Skip them and you will spend next quarter buying back traffic you already had.

Planning a redesign? We will audit what your current site earns before anything is touched, protect it through the move, and build the new one to convert. See our web design services, or get a proposal.

Frequently asked questions

Will a website redesign hurt my SEO?

It can, and the usual cause is URL changes without a complete, tested 301 redirect map. Google expects temporary fluctuation during a move and says a medium-sized site can take a few weeks for most pages to be reindexed, so a modest dip that recovers within a few weeks is normal. A steep, sustained drop signals a technical fault.

How often should a business website be redesigned?

There is no fixed interval. Rebuild when the platform blocks you from publishing, the structure no longer matches what people search for, or the business itself has changed. If the complaint is only that it looks dated, a visual refresh costs less and risks nothing.

How long should I keep the old redirects?

Google’s guidance is to keep them for at least one year, and it recommends keeping them indefinitely from a user’s point of view. Old links on other websites and in old emails keep sending people to the original URLs long after the launch.

Should I redirect retired pages to the homepage?

No. Redirect each retired page to its closest equivalent. Mass redirects to the homepage are treated as soft 404s, which discards the value you were trying to preserve.

What should I measure before launching a redesign?

A full crawl of existing URLs, 12 months of Search Console queries and pages, GA4 sessions and conversions by month, current rankings for commercial keywords, and an inventory of forms, PDFs, tags and integrations. Without that baseline you cannot tell a redesign problem from normal seasonality.

Can PSG help pay for a website redesign?

If the build is purchased as a pre-approved PSG solution and your company meets the eligibility conditions, support of up to 50% of qualifying cost applies within the S$30,000 per company per financial year cap. You apply through the Business Grants Portal yourself, before paying any deposit. Ad spend and ongoing retainers are generally not claimable.

Related reading: once the relaunch is safely live, the next two jobs are usually performance and conversion — see Core Web Vitals in Singapore and, if you sell online, e-commerce CRO in Singapore.