Web Development

Website Redesign Checklist: 15 Things to Fix Before You Launch

The pre-launch checks that stop a redesign from quietly destroying the traffic you already had.

Nepal Digital Labs5 min read

The most expensive redesign mistake is not an ugly homepage. It is launching a beautiful new site that loses the search traffic the old one had taken years to earn.

Work through this before you go live.

Before you touch anything

1. Record where you are now

You cannot tell whether the redesign helped if you never wrote down the starting point. Capture:

  • Monthly traffic and where it comes from
  • Your top 20 pages by traffic
  • Current rankings for the keywords you care about
  • Monthly enquiries, calls and form submissions
  • Core Web Vitals

Screenshot it. Memory is unreliable and optimistic.

2. List every existing URL

Export the full list from Search Console or crawl the old site. You need this for redirects, and nobody can reconstruct it after the old site is gone.

3. Identify the pages that earn

Some old pages bring traffic and enquiries. Those pages are assets. Know which they are before someone decides to delete one for being ugly.

Content and structure

4. Do not lose content that ranks

If an old page ranks, the new version needs to cover the same ground at least as well. Redesigns often cut text for visual cleanliness and lose the rankings with it.

5. Keep URLs where you can

The safest redirect is the one you do not need. If a URL works and ranks, keep it. Change structure only when there is a real reason.

6. Map every redirect

Build the mapping as a spreadsheet: old URL, new URL, done. Then test every row after launch.

7. Check the heading structure

One h1 per page. Logical h2 and h3 beneath. Do not pick a heading level for its size — pick it for its place in the hierarchy and style it separately.

8. Metadata on every page

Unique title under 60 characters, unique description under 155. A redesign that ships with "Home | Home" on every page undoes a lot of work quietly.

Technical

9. Test on real devices

Not a resized browser window. An actual phone, over actual mobile data. Borrow an older Android if you can — it is what a large share of your visitors use.

10. Check loading speed

Run Lighthouse on mobile. Image-heavy redesigns regularly ship slower than the site they replaced. Compress everything, use modern formats, lazy-load below the fold.

11. Verify every form

Submit each one yourself, from a phone, and confirm the message actually arrives. Then check the spam folder.

Also test what happens on failure — a form that silently swallows an enquiry loses you work you will never know about.

12. Confirm analytics and tracking

Analytics, Search Console, conversion events, any pixels. Redesigns routinely ship without the tracking code, and the gap in your data is permanent.

13. Generate and submit the sitemap

A fresh sitemap.xml, a robots.txt that does not accidentally block the whole site, and both submitted to Search Console on launch day.

Content accuracy

14. Check every fact on the site

Phone number, address, hours, prices, team members, services you no longer offer. Redesigns copy content forward, including the parts that went out of date two years ago.

Internal and external. Check nothing points at a staging URL, and nothing 404s.

Launch day

  • Launch early in the week, not Friday afternoon
  • Verify SSL is working on the new site
  • Confirm www and non-www both resolve to one canonical version
  • Test the redirects, every one
  • Submit the sitemap
  • Watch Search Console for crawl errors over the following days

The two weeks after

Rankings often wobble for a week or two after a significant redesign. That is normal. What is not normal:

  • Traffic dropping and staying down after three weeks
  • Pages disappearing from the index
  • Crawl errors climbing

Check Search Console every few days for the first fortnight. Most redesign disasters are redirect problems, and they are cheap to fix if you catch them early.

Key takeaways

  • Record traffic, rankings and enquiries before you start, or you cannot judge the result
  • Every changed URL needs a 301 to its real equivalent, not the homepage
  • Check robots.txt is not still blocking the site from staging
  • Submit every form yourself, from a phone, and confirm it arrives
  • Expect a short ranking wobble; investigate if it lasts past three weeks

If a redesign feels risky

It should. There is real value in an existing site, and a careless rebuild destroys it.

We handle redesigns and migrations with the redirect mapping and tracking continuity built into the process rather than remembered at the end.

Tell us about your current site and we will tell you honestly whether it needs a rebuild or just repair.

Want this done properly, without the guesswork?

Tell us what you are trying to achieve and you will get an itemised quote — no obligation, no follow-up pressure.

Nepal Digital Labs

Websites, hotel presence and business data, from Kathmandu.

Have a question this did not answer?

Ask us directly. We reply in plain language — the same way we write.