Website redesign checklist: before you rebuild
The most common way a redesign fails is not ugly design. It is launching a better-looking site that quietly loses the search traffic the old one earned.
Before redesigning, establish a baseline of current traffic and rankings, inventory every existing URL, identify your best-performing pages, and plan redirects from old URLs to new ones. Then decide what the redesign is actually for — a measurable business goal, not just a fresher look. Skipping the audit is how organisations lose years of accumulated search equity in a single weekend.
A redesign is a good moment to fix structural problems. It is also the single most common moment for a site to lose rankings, break links and confuse returning visitors. The difference between those outcomes is preparation.
Published 26 July 2026 · Last updated 26 July 2026 · Written by the WebsiteDesigner.com.my project consultancy team, Kuala Lumpur
Before you start
1. Define why
“It looks dated” is a symptom, not a goal. Write down what should measurably improve: more qualified enquiries, lower bounce on key pages, ability to update content without a developer, better mobile experience. This is what you will judge the project against.
2. Record your baseline
- Traffic by month for the past year, and by landing page.
- Which pages bring the most organic visits and conversions.
- Current keyword positions for terms that matter.
- Conversion rates on key pages and forms.
- Core Web Vitals and page speed.
Without this you cannot prove the redesign helped — or notice quickly if it hurt.
3. Inventory every URL
Crawl the existing site and export the full list of URLs. You need this to build the redirect map. Include PDFs and any landing pages used in advertising.
4. Identify what must not break
- Pages with inbound links from other websites.
- Pages ranking well in search.
- URLs used in printed material, email campaigns or ads.
- Integrations and forms feeding your CRM.
Planning the new site
5. Decide the content strategy
For each existing page: keep as is, rewrite, merge with another, or remove. Removing thin pages is usually good; removing a page that ranks well is usually not. Decide deliberately rather than by omission.
6. Plan the structure
Design navigation around what visitors are looking for, not your internal departments. Keep important pages within a couple of clicks of the homepage.
7. Keep URLs where you can
If a URL works and ranks, there is rarely a good reason to change it. Change URLs only for a real structural improvement — and redirect properly when you do.
8. Build the redirect map
Every changed URL needs a 301 redirect to its closest equivalent. Not the homepage — the closest equivalent page. A homepage-wide redirect is treated as a soft error and loses the value you were trying to keep.
9. Agree who manages content afterwards
If your team will maintain it, you need a CMS and training. Decide this before the build, not after.
Before launch
- Test every redirect from the old URL list.
- Check titles, meta descriptions and headings on key pages.
- Confirm analytics and conversion tracking fire on the new site.
- Test all forms end to end, including the notification email.
- Check the site on real phones, not just a resized browser.
- Run accessibility checks — keyboard navigation, contrast, alt text, labels.
- Verify page speed and Core Web Vitals against your baseline.
- Confirm the staging site is not indexable and the live one is.
- Update the XML sitemap and submit it.
- Check SSL, canonical tags and the www/non-www preference.
After launch
- Watch search console for crawl errors and 404s daily for the first fortnight.
- Compare traffic and rankings against your baseline weekly for the first two months.
- Expect a short dip as search engines reprocess the site; investigate if it persists beyond a few weeks.
- Fix 404s as they appear by adding redirects.
- Review against the goals you set in step one.
If you would rather not manage this yourself, redesigns and migrations are routine work for us — including redirect mapping and content migration. See website design and CMS development.
Frequently asked
It can, if URLs change without redirects, content is removed, or the new site is slower. Done carefully — with a redirect map and preserved content — rankings usually hold and often improve. A brief dip while search engines reprocess the site is normal.
Where they work, yes. Changing URLs for cosmetic reasons creates risk for no benefit. Change them only for a genuine structural improvement, and redirect every old URL to its closest new equivalent.
Prioritise pages that attract traffic or drive enquiries. Rewriting everything at once is expensive and delays launch. Improve your most important pages first, then work through the rest after go-live.
Usually yes. Content can generally be migrated, though the effort depends on the structure and quality of the existing data. This should be scoped explicitly rather than assumed.
Related
Ready to scope your project?
Send us your requirements and a Kuala Lumpur consultant will come back with a clear scope, timeline and estimate.