Website Strategy

How to Plan a Website Redesign Without Losing Useful Content

A redesign should improve the site without accidentally throwing away the pages, URLs, information and search value that were already doing useful work.

Audit before deleting

Start with a page inventory. Record important URLs, page topics, traffic or search value when available, inbound links, useful copy and any content that supports customers after they arrive.

A visually dated page can still contain strong information. Redesigning the interface does not automatically mean discarding the underlying content.

DDPW principle: Treat the old site as evidence. Decide what deserves to survive before deciding what deserves to disappear.

Classify every important page

Most existing pages fall into a few categories: keep largely as-is, improve, merge into a stronger page, redirect to a better destination, or retire because the content no longer serves a purpose. Making that decision explicitly prevents accidental losses during the rebuild.

Preserve useful URLs where practical

If an existing URL is already established and the page topic remains substantially the same, keeping the URL can reduce unnecessary disruption. When a page must move, use a deliberate redirect to the closest relevant replacement rather than sending everything to the home page.

Map old content to the new architecture

A new navigation structure may organize information very differently. Build a migration map that shows where each important old page, section or topic will live in the new site. This is especially useful when several thin pages are being consolidated into one stronger resource.

Protect internal links

Old internal links often survive inside articles, service copy and archived material. Update them so visitors do not bounce through unnecessary redirects or land on missing pages. The new architecture should also add stronger contextual links between related content.

Redesign the hierarchy, not just the colors

A valuable redesign improves how information is understood. Review heading structure, calls to action, service grouping, page sequence and mobile layout. If the old information architecture was confusing, reproducing it with prettier typography does not solve the real problem.

Verify after launch

Once the new site is public, check the most important old and new URLs, navigation paths, metadata, indexability and forms. Monitor for unexpected 404s and pages that lost their intended destination.

See the Website Rebuild Project Playbook →

Put the idea to work

Need help applying this to a real project?

DDPW can help turn the framework into a working website, research system, project plan, workflow or defined set of deliverables.

Start a ProjectBrowse Resources

Scroll to Top