Plan a website redesign around the pages and enquiry routes that already help customers. Keep useful URLs where possible and map changed ones to relevant destinations. Spout’s website packages start from K4,500, confirmed in your written quote; a redesign’s migration work must be scoped separately against the existing site and the changes you need.
What should you record before replacing the site?
Make an inventory of public pages, important documents, contact forms and accounts. Include the URLs linked from your business profile, advertisements, social accounts and customer emails. The pages people still use may include older links that are absent from the current navigation.
Ask for the search and enquiry evidence available to the business. Which pages get visits, which queries lead to the site and which contact routes produce useful conversations? A new design should make those journeys easier to use, rather than erase them because they are visually old.
Keep the source content and an appropriate backup. Record who owns the domain, hosting, email and reporting accounts before any service changes. A website handover can become difficult when an important account belongs to an unavailable person or the wrong organisation.
Should you change the domain and every page address?
Make URL changes for a concrete reason. A new visual design does not automatically require a new address for each service. Keeping a useful existing URL can reduce the number of moving parts in the project and preserve the link customers already recognise.
Where addresses do change, Google’s site-move guidance recommends planning the old-to-new mapping and redirects. It warns against redirecting many old pages to an irrelevant destination. Source checked 19 October 2026.
For your business, the question is whether the new destination answers the same customer need. A former booking page should not silently become a generic home page merely because someone wanted an easy redirect rule. Give the migration map a business review as well as a technical check.
What belongs in a migration checklist?
Our suggested checklist follows things a customer might already have saved. It makes the acceptance conversation more specific than asking whether the new home page looks finished.
| Existing item | Decision before launch | Evidence after launch |
|---|---|---|
| Service URL | Keep it or name its relevant replacement | Original link reaches the intended page |
| Contact form | Confirm the receiving address and required fields | A labelled enquiry reaches the authorised receiver |
| Download | Retain it or replace it deliberately | The public link opens the correct file |
| Payment or booking journey | Agree how existing records and new requests are handled | The agreed safe test completes |
| Search metadata | Preserve accurate titles, descriptions and preferred URLs | The live source reflects the approved page |
| Business email | Confirm whether it is affected by hosting or domain work | Sending and receiving still work |
This is an editorial planning framework. It does not promise that a redesign will retain every ranking or eliminate all disruption. It gives the owner and implementer a shared definition of what must be checked.
How should you review the new copy?
Check it against what the business actually offers. A polished new page can still introduce wrong prices, old phone numbers, unsupported claims or a service area the team does not cover. Those errors matter to the buyer before any ranking discussion begins.
Preserve useful detail from the original site, but review whether it remains accurate. Do not replace a specific service explanation with generic phrases simply to shorten the layout. Ask whether a first-time customer can work out what you do, where you work and what the next step is.
For package costs, use the current approved offer. Spout packages start from K4,500, confirmed in your written quote. Our pricing page explains the starting point; it does not establish that every redesign or data transfer is included at that figure. Scope the existing site’s condition and the content work explicitly.
What should be tested on a phone?
Open the pages a customer is most likely to use, follow the menu and try the main enquiry route. Check the phone and WhatsApp links and make sure a customer can read the service details without a layout obstruction. Use real content rather than placeholders during the review.
Test the journey from an existing external link as well as from the home page. Someone arriving from a business profile or old quotation may never see the new navigation. Their destination should still make sense and offer a clear route forward.
Have the receiver confirm that the test enquiry arrived. A visible success banner proves only what the page displayed. The acceptance record should show the business outcome the form exists to produce. Our business-email service covers the related delivery conversation.
What should you monitor after launch?
Keep a list of changed pages and review search reports, broken-link reports and enquiries against that list. Investigate a fall in useful contacts rather than assuming it is an unavoidable effect of redesign. The cause could be a missing form, an irrelevant redirect or a changed message.
Google notes that search visibility can fluctuate while a move is processed. No provider should turn that into a promise of an exact recovery date. Agree monitoring responsibility and the route for fixing defects instead. Keep access to the old content and the agreed recovery options until the handover is accepted.
Our web-development service and SEO service cover the two sides of this project. Bring your current URL, the reason for redesigning and the journeys you need to protect when you request a redesign brief. That gives the new site a business purpose and a verifiable handover.
Spout Team. Prepared with AI assistance; sources checked on 19 October 2026.