Website Redesign and Migration Checklist for Nepal Businesses

A website redesign or migration should preserve valuable pages, content, images, forms, visit history, and business-account ownership. Test the replacement before it takes over the live domain. Match each important old page to its new destination, keep a working backup, and check the site after launch.

This checklist applies whether you are changing the design, editing system, hosting company, or domain name.

First decide what is changing

Different changes create different risks:

Change	Main risk
Visual redesign	Content, forms, headings, or customer actions change by mistake
Hosting change	The site, security certificate, forms, or email stops working
Editing-system change	Page addresses, search listings, images, or staff editing access is lost
Domain change	The team must plan each URL and external reference
Content consolidation	Removed pages lose relevant destinations
E-commerce or membership move	Accounts, orders, payments, and transactional email require data planning

Avoid changing the domain, editing system, content, and page-address structure in one launch when the project allows separate stages. Google’s official site-move documentation recommends preparation, testing, page mapping, permanent forwarding, and monitoring.

Before the redesign: list what the business must keep

Record the current:

• pages that receive search visits, referrals, or customer use;
• current search listings for important services;
• links between pages and links from other websites;
• images, documents, downloads, and their current addresses;
• contact, booking, application, donation, and payment forms;
• visit, call, form, booking, and purchase measurement;
• domain, hosting, business email, payment, map, and booking accounts;
• old page addresses that already forward elsewhere;
• current mobile speed and customer complaints;
• editing access, customer records, and verified backups.

Do not rely on the navigation alone. Search data, visit records, incoming links, staff bookmarks, and customer emails may reveal useful pages that no menu shows.

Decide what each current page should become

For each current page, choose one action:

1. Keep: same purpose and same URL.
2. Improve: same URL, updated content.
3. Consolidate: move useful content into one stronger destination.
4. Redirect: send an old URL to the closest relevant replacement.
5. Remove: return a genuine 404 or 410 when no useful replacement exists.

Do not send every removed page to the homepage. Choose a destination that answers the same customer need.

Match each changed page address to one destination

Create a spreadsheet or configuration table with:

• old page address;
• new destination;
• reason for the change;
• content owner;
• test result.

Use a permanent redirect when a page has moved for good. Google recommends 301 or 308 redirects for permanent moves; see its redirect guidance.

Avoid sending visitors through several redirects. Update menus and page links to point to the final destination.

Keep important image and document links working

Images and documents may receive traffic or backlinks even when they are not visible in the main navigation.

Before launch:

• identify media that customers or other websites still use;
• preserve their existing paths where practical;
• move the required public files;
• exclude old software files, logs, backups, and private uploads;
• open each important file from its public link;
• add redirects when a media URL must change;
• keep descriptive filenames and useful alt text in the new content.

Copying the entire old hosting account can expose private or obsolete files. Copying none of it can break years of useful links.

Keep visit and inquiry measurement

Record the current website visit and search accounts before the move. The new site should retain or replace measurement for:

• website visits and search performance;
• form submissions, phone taps, email taps, bookings, and purchases;
• cross-domain settings where required;
• consent behavior;
• campaign links;
• staff visits and referral sources.

Complete safe test actions on the live domain and confirm that the business can see them in its measurement account.

Test every form and its email delivery

For each form, verify:

• the visible fields and validation;
• the final recipient;
• spam protection;
• success and error messages;
• email authentication and deliverability;
• whether submissions are stored and who can access them;
• privacy and retention requirements;
• inquiry measurement without copying personal form details into reports.

Also confirm that changing DNS or hosting will not disrupt business email. A DNS provider may manage website and email records in the same zone even when each record points to a different service.

Review a private test version

Review the replacement without taking down the current site. Before launch, confirm:

• one intended H1 per page;
• correct page titles and search descriptions;
• readable content and working links;
• all important public pages are included;
• changed page addresses reach the right destination;
• responsive layouts without horizontal overflow;
• images with useful dimensions;
• working navigation and custom 404 handling;
• no placeholder text, test accounts, private details, or test-site links;
• a recorded version that matches the pages the client approved.

Keep the private test version behind access control so customers and search engines do not mistake it for the live site.

Create rollback before launch

Before changing production:

1. back up website files and customer or content records;
2. confirm the backup location and size;
3. preserve the current hosting and domain settings;
4. record the source commit or release archive;
5. define the rollback trigger and person responsible;
6. test restoration when the site is business-critical.

Verify the backup file and test restoration for a business-critical site.

Launch checklist

• Publish the exact version the client approved.
• Change the hosting or domain through the agreed launch plan.
• Confirm the secure website address works.
• Test the homepage, key services, conversion pages, articles, and top landing pages.
• Test old URLs and confirm one-hop redirects.
• Use test details to check forms and confirmation email.
• Confirm visits and customer actions appear in the business measurement account.
• Confirm search engines can access the intended public pages.
• Check custom 404 behavior with a random missing URL.
• Verify important media and downloadable files.
• Check mobile navigation and high-value journeys.
• Keep the rollback available.

Monitor errors and search data after launch

For the first days and weeks, review:

• hosting errors;
• missing pages and links that pass through several destinations;
• Google Search Console page reports;
• organic landing pages and query changes;
• website visits and customer actions;
• form delivery and support reports;
• performance and field data when enough data becomes available;
• unexpected requests for old images, documents, or connected services.

Ranking and traffic can fluctuate while search engines recrawl a changed site. Do not claim recovery or improvement until comparable evidence exists.

What we preserve during a Jasuda Tech migration

Our migration plan covers valuable page addresses, images, documents, visit measurement, forms, missing-page handling, protected subdirectories, and rollback. We test them with the new pages before replacing the live site.

We define that continuity work before uploading the replacement.

Frequently asked questions

Will a website redesign hurt SEO?

Losing useful content, page addresses, links, search listings, or contact paths can hurt search performance. Measure the result after launch before claiming an improvement.

How long should redirects remain?

Keep permanent redirects for as long as users, search engines, or external links may request the old URLs. Removing them early can recreate broken links and split signals.

Should we keep all old pages?

No. Keep or improve pages that serve a real audience. Consolidate overlapping content, redirect pages with a relevant replacement, and return a genuine missing status when no equivalent exists.

Will old links keep working?

They should. Each valuable old address should either remain available or send the visitor to one relevant replacement page.

Can Jasuda Tech preserve existing URLs during a WordPress migration?

Yes. Preserving useful paths is often the safest option. When a URL must change, we map and test the permanent redirect before launch.

Review WordPress migrations and rebuilds, website development pricing, or request a migration review.