A website redesign should preserve what already works while improving specific weaknesses. Before replacing pages, record URLs, content, analytics and enquiry flows so visual improvements do not accidentally remove search or operational value.
Inventory the existing site
List public pages, metadata, incoming links where known and the tasks visitors complete. Note which content is important to customers and which routes are used by integrations. Save a complete backup. A new navigation plan should account for those facts rather than starting from an empty sitemap.
Change based on a diagnosed problem
Distinguish readability, mobile navigation, content clarity, performance and conversion issues. Each requires different work. A site can be visually dated yet operationally sound, or polished but difficult to use. Set acceptance criteria for the specific problems being fixed and preserve useful content instead of shortening it indiscriminately.
Map necessary URL changes
Keep established URLs where possible. If a route must change, map it directly to the most relevant replacement with a permanent redirect. Avoid chains and sending every removed article to the homepage. Verify canonicals, internal links and sitemap entries against the final routes before deployment.
Rehearse the launch
Build and test on staging, check representative mobile devices and exercise every enquiry and download flow. Confirm rollback access and publish during a time when someone can monitor failures. After release, inspect indexability, error responses and actual leads. The launch is a controlled migration, not just a new visual file upload.