Redesigning Your Website? Keep The Useful Parts Working

The new homepage looks right. The team is ready to share it. Then someone asks what will happen to the article customers still read, the product link in a brochure or the form sales relies on.

Those questions belong in the redesign plan, not the launch-day scramble.

A redesign changes the experience people see. It also needs to account for the useful work your existing website already does.

Make An Inventory Before Removing Pages

List the current pages, articles, downloads and important forms. Include older URLs that still appear in search results or are linked from other websites.

Use your content system, website data and Search Console as starting points. Ask sales and customer service which links they send to people. A page can be useful even when it is not among the most visited.

Decide what to keep, improve, combine or remove. Give each decision a reason beyond "it is old" or "it does not fit the new menu".

Keep Useful Addresses Where You Can

A fresh design does not require a new address for every page.

When a URL genuinely needs to change, agree where the old link should lead. The replacement should answer the same need. Sending every old article to the homepage leaves readers looking for the information they expected.

Google's website-migration guidance recommends mapping old URLs to their new destinations and avoiding irrelevant redirects. If several articles are combined, finish the useful replacement before redirecting readers to it.

Keep a shared record so the content team and developer are working from the same decisions.

Check The Content With Real Examples

Do not review only pages filled with short sample copy.

Check long service names, detailed product descriptions, older articles and documents with similar titles. Make sure the layout can accommodate the information people need without clipping it or hiding essential details.

Confirm business facts, contact routes, people, offers and policies with the responsible owners. A redesigned page can still carry an outdated promise.

Test The Enquiry, Not Just The Button

Try the important journeys from beginning to end on a phone and a computer.

Can a visitor find the right service, reach the form and understand the fields? Does the confirmation make sense? Does the message reach the right team with the information they need?

Include downloads, search, filters and any handoff to another system. Agree how testing will avoid accidental customer messages, orders or bookings.

Separate Preview Protection From Launch Settings

It is reasonable to keep a work-in-progress site private. The developer should have a separate launch check for access, search visibility and the final website address.

Ask the team to confirm that the intended public pages are available, their links point to the correct destination and the search settings reflect the approved launch plan.

This is a handover question for the responsible team, not a reason to remove protection from an unfinished preview.

Know Who Is Watching After Launch

Assign someone to check important pages, incoming enquiries and reported problems after the switch.

Keep the old content inventory and approved URL map available. They make it easier to investigate a missing page than trying to remember what used to exist.

Review search visibility and enquiries in context. A redesign does not guarantee an improvement, and a change in one report does not explain its cause on its own.

Make Launch A Shared Checklist

Before agreeing that the website is ready, confirm who has approved the content, who has tested the journeys and who owns unresolved issues.

You do not need every future feature at launch. You do need a clear plan for the pages you are releasing and the existing information people still depend on.

Preparing a redesign? Talk To Us About The Move.