Begin with what already works
A redesign should improve the experience without accidentally discarding useful pages. Before changing layouts, collect the current page list and identify which pages attract enquiries, answer customer questions or receive links. This gives the new site a foundation beyond visual preference.
Use your analytics and Search Console data where available. If you do not have a reliable baseline, document that limitation and start measuring before the release. A screenshot of the old homepage cannot tell you which service page generates the most useful leads.
Make a page-by-page decision
Assign each existing page a destination: retain it, improve it, combine it with a closely related page or retire it. Record the reason. Useful information may live deep in the old site, such as delivery coverage, service exclusions or an answer a customer regularly asks.
When URLs change, map each old URL to its relevant replacement and implement permanent redirects. Avoid sending every old page to the homepage. Google’s site-move guidance explains URL mapping and migration checks.
Agree a release checklist
- Check that important pages return the intended status and have a canonical URL.
- Update navigation, internal links and the sitemap to use the final destinations.
- Confirm that development-only indexing restrictions are removed from public pages.
- Keep private or preview material under the appropriate access and indexing controls.
- Check page titles, descriptions and visible content on the release version.
Test a few old URLs by opening them directly, including deeper service and article pages. A working menu does not prove the old links still work.
Test the enquiry journey as a customer
Read the site on a phone. Can a visitor understand the service, find supporting work and reach the correct enquiry form? Check required fields, validation messages and the selected service. Arrange an authorized delivery test with the team rather than assuming that a success message means the inbox received it.
Assign the first week of ownership
Name the person who reviews errors, enquiry delivery and search coverage after launch. Keep the previous deployment available for recovery where practical. Log unexpected changes so the team can distinguish release problems from unrelated demand changes.
What a redesign cannot promise
A careful migration reduces avoidable mistakes; it does not guarantee unchanged rankings or an immediate increase in leads. Compare results over time and consider changes in campaigns and demand. Our web development service includes defining the migration and launch scope before building.