Website Redesign Planning: How to Protect Content, Links and Conversions

A website redesign is often framed as a design and technology project. The risk is that the team focuses on the new look and the new platform while treating the existing site as something to replace. That is how organisations lose valuable content, break inbound links and interrupt conversion paths. Good website redesign planning treats the current site as a set of assets to protect, migrate and improve—not a draft to discard.

The most expensive redesign mistakes are rarely visible in a design review. They appear after launch as missing pages, redirected traffic that lands on the wrong page, forms that no longer submit, or product pages that lost their search visibility. Preventing them requires planning that starts before wireframes and continues after launch.

Start with an asset inventory, not a mood board

Before deciding what the new site should look like, document what the old site does. Build a content inventory and a URL inventory. Include every page, post, product, resource, landing page, PDF and form. Record the URL, page title, content owner, primary audience, approximate business value, last update and intended destination in the new site. The point is not to create bureaucracy; it is to make decisions explicit.

Add a conversion inventory. List the actions that matter: enquiries, demo requests, newsletter sign-ups, downloads, applications, purchases, dealer locators, support requests and account logins. For each, note where it happens, what happens afterwards and who owns it. A redesign that improves aesthetics but weakens a high-value conversion path is not an improvement.

Assign an owner for each asset group. Content, SEO, analytics, development, sales and customer support should each review the inventory. This prevents the common failure in which one team assumes another team has checked a page, redirect or form.

Map every URL to a destination

Create a URL map that links every old URL to its new URL—or to a deliberate retirement page. Use one-to-one redirects where possible. Avoid sending everything to the homepage; it frustrates users and weakens the relevance of the landing experience. For pages that are being merged, choose the strongest destination and update internal links to point there directly. Keep redirects in place long enough to protect links from search engines, partners and older marketing materials. Review the map for query strings, trailing slashes, uppercase variants and legacy paths.

Do not forget files and microsites. PDFs, event pages, campaign landing pages and old blog URLs often attract links or continue to appear in search results. If a file is retired, redirect to the closest relevant page or provide a clear replacement. Test redirects in staging and again after launch.

Protect the content that earns traffic and trust

Content migration is not a copy-and-paste exercise. Some pages need to be preserved almost exactly, some need updating, some should be merged and some should be removed. Make that decision page by page. High-value content often includes service pages, product documentation, help articles, comparison pages, policy pages and long-standing resources. Removing or rewriting them without a plan can erase the reason people visit the site.

Preserve metadata, headings, image alt text, internal links and structured data where relevant. Check that tables, embedded videos, downloads and forms still render in the new templates. For editorial content, confirm that author pages, dates and categories survive if they matter to readers. If the new design changes reading patterns, test a sample of long-form articles on mobile and desktop before migrating everything.

Use the redesign as an opportunity to fix genuine content problems: outdated information, duplicate pages, unclear calls to action and thin pages. But separate improvement from migration. If a page is being rewritten, keep a record of the old URL, the new copy and the reason for the change. This helps teams answer questions after launch and avoids accidental loss.

Rebuild conversion paths deliberately

Conversions are fragile because they depend on a sequence: the message, the call to action, the form or checkout, the confirmation and the follow-up. A redesign can break any step. Before launch, document each important conversion path and test it end to end in staging. Include validation errors, thank-you pages, email notifications, CRM hand-offs, payment steps and analytics events.

Review the new templates for the elements that support trust and action: clear value propositions, contact details, delivery and returns information, security cues, pricing context and accessible form labels. Do not remove a useful element simply because it complicates the layout. If a form is shortened or a step is removed, confirm that the business still receives the information it needs.

Set up a tracking plan before the new site goes live. Define the events, goals and dashboards that will show whether key actions still work. Compare pre-launch and post-launch behaviour without assuming that every change is caused by the redesign. A short period of close monitoring is normal; unexplained drops in form submissions or cart completions should trigger an immediate review.

Create a launch QA and rollback plan

A launch checklist should cover more than visual QA. Crawl the staging site and the live site after launch. Check for broken internal links, missing images, redirect chains, incorrect canonical tags, accidental noindex settings, robots.txt issues and sitemap errors. Test search, navigation, filters, forms, logins and checkout. Check the site on common mobile devices and with assistive technologies.

Prepare a rollback plan. Know who can revert the launch, how long the old site can remain available, and how to restore redirects or forms if something fails. A rollback plan is not a sign of weak planning; it is a control that lets the team act quickly if a critical path breaks.

Keep governance visible after launch

Redesign planning should end with ownership, not a launch party. Keep the URL map, content inventory and redirect list accessible. Assign someone to monitor broken links, search console issues, form failures and conversion dashboards. Review the first weeks of data with content, marketing, sales and support teams. Record decisions so future changes do not undo protections that were deliberately put in place.

The safest redesign is not the one that changes the least. It is the one that knows which assets must survive, which links must resolve, and which conversions must keep working. When website redesign planning starts with those protections, the new design can improve the experience without sacrificing the value the old site had already built.