By KYN AI Advisory Team — AI implementation specialists, Singapore
A website redesign is the most common way a Singapore business loses search traffic it took years to earn. The design is rarely the cause. The cause is what changes underneath it: URLs, page titles, headings, internal links and the content Google already ranks. All of it can be kept. It has to be decided before the first screen is drawn.
What breaks rankings in a redesign?
Google ranks pages, not websites. Each page has a URL, a title, a set of headings and a body that it has already matched to queries. A redesign breaks that match in five ways.
- The URL changes and no redirect points the old one to the new one. The old page returns a 404 and its ranking goes with it.
- The title or H1 is rewritten for style. The page no longer matches the query it ranked for.
- Content is trimmed. A page that answered a question in 900 words now answers it in 200, and a competitor's longer page takes the spot.
- Internal links disappear. A page nobody links to loses the signal that it matters.
- Old pages are deleted because the new navigation has no place for them. The traffic they carried is deleted with them.
From our own builds: when 51 articles on one site were archived in a cleanup, the blog's impressions fell by nearly half within two weeks. All 51 were republished and the traffic returned. Nothing about the new design had been wrong. The pages had simply gone.
Which URLs and titles must stay the same?
Every URL that receives traffic or has a backlink must stay exactly as it is, or redirect. Start with a full list.
- Export every URL from Google Search Console (Performance, last 16 months) with its clicks and impressions.
- Export every URL from the sitemap and from a crawl of the live site.
- Merge the lists. Mark each URL as keep, redirect or retire. Retire only pages with zero impressions, zero backlinks and no business purpose.
Titles and H1s follow the same rule. A page with impressions keeps its title unless the new one targets the same query more precisely. Changing "Will writing in Singapore" to "Plan your legacy" is a rewrite for style, and it costs the ranking.
From our own builds: a site moved from a site builder to Next.js kept all 13 of its URLs unchanged. The redesign changed every pixel and no rankings moved.
How do you map redirects before launch?
A redirect map is a two-column list: old URL, new URL. Build it before any page is built, not on launch day.
- Each retired or renamed URL gets a 301 to the page closest to the same intent. Never redirect everything to the home page; Google treats that as a soft 404.
- Keep the map in the repository, not in a hosting dashboard. It should survive a change of host.
- Include URLs that were already dead. From our own builds: 83 URLs removed in an earlier cleanup were still indexed as 404s months later. A redirect map that covered them cleared the errors in one deploy.
How do you test the new site before it goes live?
Test on a staging domain that is blocked from indexing, then compare it to the live site page by page.
- Crawl both and diff the URL lists. Any URL on the old site that is missing on the new one needs a redirect entry or a reason.
- Diff titles, meta descriptions and H1s. Each change should be deliberate.
- Check that schema (Organization, Article, FAQ, Breadcrumb) renders on the new pages.
- Run Lighthouse on the five most visited pages. A redesign that is slower than the old site will lose Core Web Vitals ground even if everything else is kept.
- Load each redirect in a browser and confirm it lands on a real page with a 200 status, not a chain of redirects.
What should the build fail on?
The strongest protection is a check that runs on every deploy, not a checklist someone reads once. From our own builds: the site has a step in its build pipeline that compares every URL and page title against a committed list and fails the build if one has changed without the list being updated. A developer cannot rename a page by accident. They have to change the list, which shows up in code review.
The same step can check that every redirect in the map still resolves, that the sitemap contains every indexable page, and that no page has an empty title. Each of these takes a few lines and catches a class of error that would otherwise surface weeks later as a traffic drop.
A redesign that follows this order, inventory, redirect map, build guard, staging diff, is a design project with no SEO risk. If you want the rebuild done by one team that handles the design, the migration and the guard together, see website upgrade that keeps your SEO.
Frequently asked questions
Does a redesign always cause a temporary drop?
No. A drop follows changed URLs, titles or content. When all three are kept and redirects cover the rest, traffic is typically flat through the launch. Google recrawls the new pages and finds the same signals it already ranked.
Should I redesign and change the domain at the same time?
Do them separately. A domain change is its own migration with its own risks. Combining it with a redesign makes it impossible to tell which change caused a drop.
How long should the old redirects stay in place?
Permanently. Backlinks and bookmarks never expire, and the cost of keeping a redirect is zero.
Checked October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.