Record the useful baseline before changing the site.
Collect the current URLs, sitemap and available search and analytics data. Identify pages that attract relevant enquiries, earn useful links or answer important customer questions. A page can deserve attention because of its business role even when its traffic is modest.
Also record what is wrong: outdated services, overlapping pages, weak explanations and broken customer journeys. The baseline should inform decisions rather than require every old page to survive. If historical data is unavailable, note that limitation instead of inventing a performance comparison.
Make a decision for each existing URL.
Choose whether a page remains, is improved, merges into a genuinely relevant page or is removed. When a URL changes and there is an appropriate replacement, plan a permanent redirect to that destination. Keep a mapping the team can review before launch.
Avoid sending unrelated old URLs to the homepage merely to make every request return a page. If there is no suitable replacement, an appropriate not-found response may be clearer. Update internal links to the intended final URLs rather than depending on redirects throughout the new site.
Rebuild the information, not only the layout.
Review service content against the questions a buyer needs answered. Preserve accurate, useful information and replace weak copy with clearer scope, evidence and next steps. Changing headings and colours alone will not resolve an offer that remains difficult to understand.
Plan titles, headings, descriptions, canonical URLs and structured data alongside the page content. Structured data must represent the visible information accurately. If multiple language versions exist, include their relationships and review ownership in the migration plan.
Check the live launch as a complete system.
Before publication, review crawl access, intended indexability, links, mobile rendering and the core enquiry or purchase journey. Protect staging appropriately, then verify that production has no accidental indexing block. Confirm the canonical domain and expected behaviour of alternate URLs.
After launch, inspect redirects, the sitemap, analytics events and lead handling on the actual public site. A successful form should produce a stored or routed request and an accurate confirmation, not just a visual success message. Submit the sitemap through the verified search property where available.
Observe the transition and improve deliberately.
Search engines need time to recrawl and process changed pages, and visibility can fluctuate. Watch indexing signals, relevant search queries, organic landing pages and completed enquiries. Compare like periods where possible, accounting for seasonality, campaigns and other business changes.
Fix concrete problems first: inaccessible pages, incorrect redirects, misleading content or broken conversion paths. Keep a record of the launch and major follow-up edits so later analysis can distinguish the redesign from subsequent changes. A new site is a foundation for continued improvement, not a guarantee of immediate rankings.
Your planning checklist
- Inventory important URLs and available performance evidence.
- Approve a URL-by-URL keep, merge, redirect or remove plan.
- Validate production crawl access, metadata and core journeys.
- Monitor indexing and qualified enquiries after publication.
Common questions
Does a redesign always reduce search traffic?
No. Results depend on the changes, the existing site and many other factors. A planned transition reduces avoidable errors, but neither stable traffic nor an improvement can be guaranteed. Monitor the actual outcome after launch.
Must every old page remain on the new website?
No. Keep or replace pages based on usefulness, relevance and the business’s current offer. Where a suitable replacement exists, use an intentional redirect; otherwise handle removal clearly instead of retaining weak content only for its age.
Sources & further reading
References for the planning context. No relationship with the organizations listed is implied.
