A website redesign can improve how customers understand your business, but replacing the layout is only part of the project. Existing pages, documents, forms and contact routes also need a plan.
Before commissioning a website redesign in Kenya, identify the problem you want solved. Visitors may struggle to find a service, content may be outdated, or the enquiry process may fail on a phone. Each problem needs an observable improvement.
This checklist helps a business owner agree what should be kept, changed and tested before the replacement site goes live.
Decide whether the problem needs a redesign
An isolated broken form or an outdated paragraph may need a repair. A confusing page structure, unsuitable templates or a business model that has changed may justify broader work.
Ask for a short assessment before committing to a full rebuild. Record the affected pages and the actions visitors cannot complete.
Define success in practical terms: customers can find delivery information, a service page answers the main buying questions, or an enquiry reaches the correct team. A fresh appearance alone does not establish that those problems are solved.
Inventory the existing website
List published pages, articles, product categories, downloadable documents and important images. Record their current addresses and whether each item will stay, change, merge or be removed.
Ask the owner of each service to check its content. Identify outdated details without discarding useful explanations simply because the design is old.
Where authorised analytics or Search Console data exists, review it alongside the inventory. If those sources are unavailable, state the limitation; do not present guesses as evidence of which pages bring customers.
Map any changed page addresses
Keeping an appropriate existing address can simplify continuity. When an address must change, record the old URL and its relevant new destination.
Google’s site-move guidance recommends URL mapping, appropriate redirects and monitoring. It also warns against sending many unrelated old pages to the homepage.
For example, an old office-cleaning service page should lead to its equivalent replacement if one exists. Ask the developer to test important old links directly, including links to documents still used in emails or proposals.
Agree the content and feature scope
A redesign quotation should distinguish layout work from copywriting, content migration, product entry and new functionality.
Identify forms, appointment requests, payment integrations, search tools and downloads that must continue working. Do not assume they will be included because they appear on the current site.
If the project includes a shop, define how products, stock and recent orders will be handled during the move. Decide who can edit content near launch so changes are not lost between copies.
Review a test version before launch
Use a separate review version where practical. Ask the developer how it is protected from public access or unwanted search indexing.
Review real content in the proposed templates. A demonstration page with short placeholder text may conceal problems with long service names, detailed product descriptions or portrait photographs.
Check the navigation on a phone and try the important customer journeys. Record feedback by page and issue, then confirm which changes are complete before approval.
Test enquiries and business transactions
Submit controlled form tests and confirm receipt at the intended destination. Test telephone and WhatsApp links, file downloads and any confirmation messages.
For a shop, agree how payment tests will be performed and check the resulting order record as well as the customer’s screen. Include collection and delivery options that are part of the scope.
Make a named person responsible for accepting each important workflow. The designer can verify the implementation, while your team confirms that the information and business process are correct.
Plan the launch and recovery arrangements
Agree who authorises launch, when it happens and who will be available afterwards. Keep a recoverable copy of the existing site and ask how it would be restored if the move fails.
Where transactions continue during launch, recovery needs particular care: restoring an earlier copy may affect records created after that copy was taken. The technical plan should address those changes explicitly.
If hosting or domain settings are changing, identify whether business email is affected. A website redesign does not automatically require moving email, and any such move needs its own scope.
Check search settings and links after launch
Ask the developer to verify redirects, internal links, page titles, preferred page addresses and the public sitemap. Confirm that restrictions intended only for the test site have not been carried into the live version.
Google notes that significant site changes can produce temporary search fluctuations. A careful migration reduces avoidable mistakes; it cannot guarantee unchanged rankings.
Review important pages and old links again after launch. Keep a record of problems, the person responsible and the outcome of each fix.
Include ownership, training and ongoing care
Confirm that the business retains access to its domain, hosting and website administration. Record licences, renewals and the support arrangement.
Ask for training on the actual tasks your staff will perform. Distinguish fixing an agreed launch fault from requesting an additional feature later.
Our website maintenance guide explains the care questions to ask after handover.
Discuss your redesign requirements
Top Web Design can review your existing website and discuss a redesign around its content, customer journeys and technical requirements. Explore our website design and redesign services in Kenya.
Send your website address, the main problems you want solved and the functions that must continue working. Request a redesign discussion, call 0721 985 722 or email mail@topwebdesign.co.ke.