Redesign your website without throwing away its search history

Find out what already earns its place

The old design can go. The useful URLs, customer questions and pages that bring enquiries deserve a more careful handover. Before replacing the website, make an inventory of its pages and find out which ones people use, which appear in search and which receive links from other sites.

Look beyond total visits. A quiet service page may bring better enquiries than a popular article. Record the purpose of each important page, the action it supports and any content customers regularly ask about. This gives the redesign a clearer starting point than deciding what to keep from appearance alone.

Give every important URL a destination

Keep useful existing URLs where practical. When an address must change, map it to the most relevant replacement before launch. A simple worksheet with the old URL, new URL, intended action and test result makes the work reviewable.

Do not redirect every removed page to the homepage. Google's migration guidance warns that unrelated destinations can confuse visitors and may be treated as soft 404 errors. When several pages genuinely become one consolidated resource, redirecting them to that resource can make sense. A page with no suitable replacement needs a deliberate removal decision.

Test the handover, not just the new pages

For a permanent URL change, Google recommends a permanent server redirect where possible. The common status codes are 301 and 308. Ask the developer to test the actual old addresses, including important variations, and confirm they lead to the intended final page.

Then update navigation, content links, canonical URLs and the sitemap to use the current addresses. Visitors should not need to pass through an old URL every time they follow a link on the new website. Check downloadable files and image links too if their locations have changed.

Run a launch checklist on the production site

A staging site can look finished while still carrying settings that should not reach production. Verify indexing instructions, canonical URLs and sitemap destinations after deployment. Also check the actions that make the site commercially useful: enquiries, booking links, phone links and any purchases.

Give the review clear owners. Content approval, technical checks and the decision to switch the site live are different responsibilities. Keep a record of the release and a practical recovery plan in case a critical feature fails.

• Open the important pages and confirm their titles, headings and content.
• Submit and receive a real test enquiry through each form.
• Check mobile navigation, keyboard access and error messages.
• Confirm that production pages intended for search are accessible to crawlers.

Check how the site behaves on ordinary devices

Large imagery and motion deserve performance testing alongside visual review. A page can appear quickly and still respond poorly to a tap. web.dev distinguishes controlled lab tests from measurements gathered during real visits; both are useful because devices, networks and visitor behavior vary.

Before launch, test the main journeys under realistic conditions. After launch, watch actual performance where data is available. Treat a slow form, delayed menu or moving button as a usability problem, even when the overall design looks polished.

Keep watching after launch day

Submit the new sitemap and monitor indexing, errors, traffic and enquiries. Google advises keeping migration redirects for at least a year in general. Update important profile links and ask owners of valuable referring pages to use the new destination where appropriate.

Temporary search fluctuations can happen during a move, so no responsible redesign promise guarantees zero disruption. The goal is to reduce avoidable mistakes and investigate changes with evidence. If you are planning a rebuild, Resoltives can help connect the new design with a considered content, development and migration plan.