Website redesign: preserve what already works

Inventory the existing site

Collect the current URLs, useful content, important inbound links and functioning integrations. A redesign should not discard a valuable route simply because the navigation is changing.

Design around customer tasks

Prioritize the information people need to compare the offer and take the next step. Establish the hierarchy and content before treating visual styling as the whole project.

Plan the launch as a migration

Test redirects, canonical URLs, forms, mobile layouts and tracking in staging. Keep a restorable backup and agree the production cutover and rollback process before deployment.

Prepare a release checklist

List the current valuable routes, the new destination for each changed route and the integrations that must work after release. Test one inquiry from each major service journey. Verify canonical URLs and the organic sitemap on the intended production origin, then confirm the rollback backup. Schedule the cutover only when another migration cannot replace those files.

Turn the redesign into a controlled release

Use the following as a working brief. It is a planning example, not a client result, a quotation or a forecast.

1. Inventory current URLs, important content and connected systems before designing replacements. Include historical routes that receive links or inquiries when that evidence is available.
2. Map each changed URL to a relevant destination and retain useful routes when possible. Do not redirect every retired page to the homepage without considering its original purpose.
3. Test the protected new origin with the intended hostname, correct certificate and fresh database. Confirm another migration cannot overwrite its files or data.
4. After an approved cutover, verify pages, media, canonicals, indexing, redirects and actual inquiry receipt through public routing. Retain recoverable backups and reconcile new leads before rollback.

A worksheet to bring to the conversation

Preserve

Files, matching database, metadata and URL inventory

Map

Relevant destinations and attribution-preserving redirects

Preflight

Protected new origin, TLS and real form tests

Release and recover

Approved records, monitoring and lead-safe rollback

Discuss the next step

Bring the question to a project conversation. We can review the current setup, explain the tradeoffs and define a useful scope.

Planning guidance by Social Saturation. Reviewed November 7, 2026. Decisions depend on your actual scope and available evidence.