A new website is supposed to bring in more enquiries. Sometimes it does the opposite. The design launches, everyone is happy, and six weeks later the phone is quieter. Search Console shows clicks falling off a cliff on the day the new site went live.

This usually has nothing to do with the design. It happens because old addresses stopped working, pages that ranked were deleted or merged without a plan, or the new site was launched with a setting that told Google to stay away. All of these are build decisions. That is why we treat search as part of web development rather than something a separate agency "adds" after launch.

This guide is the migration runbook we use. It is written for business owners who are about to redesign, and for the person managing the project on their side. You do not need to do the technical steps yourself, but you should know they exist and ask who is doing them.

Know which kind of change you are making

"Redesign" covers very different projects, and the risk grows with each step down this table.

ChangeExampleSearch risk
Visual refresh onlyNew colours, fonts and layout. Same pages, same addresses, same textLow
Content rewriteSame addresses, but service pages are rewritten or shortenedMedium
New structurePages renamed, merged or split. /services/aircon becomes /aircond-servicingHigh
New platformMoving from Wix or an old WordPress theme to a custom build or ShopifyHigh
New domainabc-trading.com.my becomes abc.my, or a Malaysian site moves to a .sg domainHighest

Most redesigns are at least "new structure" and "new platform" at the same time. That is fine, as long as you plan for it. If you can, avoid changing the domain in the same project. Do one big change at a time so you can tell what caused any drop.

Step 1: Take an inventory before anyone deletes anything

You cannot protect pages you do not know exist. Old websites collect addresses over the years: blog posts from 2019, a promotion page someone forgot, PDFs, product pages for discontinued items, image URLs that other sites link to.

Build one spreadsheet with every URL the old site has. Pull it from three places, because each one misses something:

  1. The old sitemap. Usually at /sitemap.xml or /sitemap_index.xml. Quick, but often incomplete.
  2. A crawl. Screaming Frog's free version crawls up to 500 URLs, which covers most small business sites.
  3. Search Console. Go to Performance, set the date range to the last 16 months, open the Pages tab and export. This shows every page that has appeared in Google, including ones that are no longer linked from the menu.

Add a column for clicks from Search Console and, if you have analytics, a column for enquiries or sales. Sort by clicks. The top 20% of pages usually carry most of the search traffic. Those are the pages you protect first.

Step 2: Decide what happens to every old page

Each old URL gets one of four decisions. Write it in the spreadsheet so nothing is left to memory on launch day.

DecisionWhen to use itWhat the developer does
KeepThe page is useful and the address can stay the sameRebuild it at the identical URL
MoveThe page is useful but the address changes301 redirect from old URL to new URL
MergeTwo or three thin pages cover the same topicCombine the best content into one page, 301 all old URLs to it
RemoveNo traffic, no links, no business valueLet it return a 404 or 410, or redirect to a close match if one exists

Two common mistakes are worth calling out.

Redirecting everything to the homepage. It looks tidy, but Google treats a redirect to an unrelated page much like a missing page. A visitor who clicked "aircond chemical wash price" and lands on your homepage leaves. Redirect to the closest equivalent, or let the page go.

Cutting the text that ranked. A designer may want a service page with three short lines and a large image. If the old page ranked because it answered questions about pricing, process and coverage area, the new page needs to answer them too. Layout can change. The substance should not disappear.

Step 3: Build the redirect map

The redirect map is a simple two-column list: old URL, new URL. It becomes the instructions for whoever configures the server.

/services/aircon-servicing.html   →  /aircond-servicing
/services/aircon-installation.html →  /aircond-installation
/blog/2019/05/chemical-wash-guide  →  /blog/aircond-chemical-wash-guide
/promo-raya-2023                   →  (remove, 410)
/about-us.html                     →  /about

A few rules make it reliable:

  • Use permanent (301 or 308) redirects, set on the server or hosting platform. Google's redirect documentation explains why server-side permanent redirects are the strongest signal. JavaScript and meta refresh redirects are a last resort.
  • One hop only. If page A already redirected to B on the old site, point A straight to the new C. Chains of redirects slow visitors down and waste crawl effort.
  • Match the old variations. Old sites often answer on http://, https://, with and without www, and with and without .html or a trailing slash. All of them should end at one final address.
  • Keep the redirects for at least a year. Google's site move guide says to keep them as long as possible, generally at least a year. On a small site there is rarely a reason to ever remove them.

Step 4: Carry over what search engines already understand

Beyond the URLs, the old site carries signals that are easy to lose in a rebuild. Before launch, check each of these on the staging site:

  • Page titles and meta descriptions. Copy across the ones that earn clicks. Rewrite only with a reason.
  • Headings. The main heading of each page should still describe what the page is about.
  • Internal links. Menus, footers and links inside the text should point to the new addresses directly, not to old URLs that then redirect.
  • Structured data. If the old site had LocalBusiness, Product or FAQ markup that worked, rebuild it.
  • Images with search traffic. Product and project photos sometimes appear in Google Images. Keep their file names and alt text where you can.
  • Language versions. If the site has English, Bahasa Malaysia or Chinese versions, each one needs its own redirect map and its hreflang tags rebuilt. Our multilingual website guide explains the setup.
  • Tracking. The GA4 tag, Search Console verification, Meta pixel and any conversion events. A new site with no tracking makes it impossible to tell whether the redesign worked.

Step 5: Launch-day checks

Most migration disasters are caused by one of three settings. Check them in the first hour after the site goes live, not the next week.

  1. The staging block is off. Staging sites are normally hidden with a noindex tag, a password, or Disallow: / in robots.txt. If that setting is copied to the live site, Google drops it. Open yoursite.com/robots.txt and view the source of a few pages to check for noindex.
  2. The redirects work. Paste the old URLs from your spreadsheet into a bulk checker (Screaming Frog has a list mode) and confirm each returns a single 301 to the right destination, which then returns 200.
  3. The new sitemap is live and submitted. Submit it in Search Console. If you changed domains, also use Search Console's Change of Address tool.

Then do the human checks: send a real enquiry through the form, tap the WhatsApp button on a phone, and complete a purchase if it is a store.

The first 30 days after launch

Some movement in rankings is normal after a large change. Google needs time to recrawl the site and process the redirects. On a small site this often settles within a few weeks. What you are watching for is a drop that does not recover, or one concentrated on specific pages.

WhenWhat to checkWhere
Day 1Robots.txt, noindex, redirects, forms, tracking firingBrowser, Screaming Frog, GA4 real-time
Week 1New 404 errors appearing for old URLs you missedSearch Console › Pages › Not found
Week 1 to 2Important new URLs being indexedURL Inspection on your top 10 pages
Week 2 to 4Clicks and impressions on your top pages vs the same pages beforeSearch Console › Performance, compare date ranges
Day 30Enquiries per week vs before launchYour inbox, CRM or GA4 conversions

If a page lost most of its clicks, compare old and new side by side. The usual causes are a missing redirect, a page that now says much less, or a title that no longer matches what people searched for. These are fixable, especially if you catch them in the first month.

Questions to ask whoever builds your new site

You do not need to run a migration yourself. You do need to know it is someone's job. Before you sign, ask:

  • Who builds the URL inventory and redirect map, and will I see it before launch?
  • Will existing pages that bring in search traffic keep their content?
  • How are redirects set up on the new hosting, and who tests them?
  • What do you check on launch day, and who watches Search Console afterwards?
  • If clicks drop in the first month, what do you do and is it included?

A studio that treats these as normal parts of the project, rather than extras, is one that understands that a website you cannot find is not doing its job. If you are planning a redesign, start with our redesign checklist, and talk to us about the move before the design is final.