Website redesign SEO checklist: protect useful pages and links

A redesign needs a plan for the website people already use

Protecting SEO during a website redesign starts with understanding existing URLs, useful content, internal links and customer journeys. Keep valuable addresses where practical, map necessary changes to relevant destinations and check the live website after launch.

No migration plan can promise unchanged rankings. The aim is to make the change clear, preserve useful information and catch avoidable errors.

Build an inventory before designing the replacement

Collect the current sitemap, important pages from Search Console, relevant analytics and known external links. Include services, projects, articles, downloadable resources and images that matter to users.

Give each existing URL a decision:

• Keep: the purpose and address remain appropriate.
• Improve: the page stays but its information or presentation changes.
• Combine: overlapping pages become one stronger resource.
• Retire: the content no longer has a useful equivalent.

Record who owns the decision. A short page that looks unimportant to a designer may answer a frequent sales question or receive a valuable external link.

Map changed URLs to relevant destinations

For pages that move, create an old-to-new mapping. Match the original purpose as closely as possible. If two pages are combined, the replacement should actually cover the useful information being consolidated.

Google’s site-move guidance recommends preparing URL mappings, implementing suitable permanent redirects and monitoring the result. It also warns against redirecting many unrelated URLs to an irrelevant homepage.

Avoid long redirect chains. Update your own navigation and content links to point directly to the final destination. For genuinely removed content without a relevant replacement, use an appropriate not-found or gone response and give the visitor a useful onward route.

Preserve the information behind the design

Review titles, descriptions, headings, image descriptions and important business details. Carry useful answers into the new content rather than replacing every page with a short visual introduction.

Check who can edit the content after launch. A redesign should leave the business able to update services, projects and contact details without breaking the page structure.

Separate claims from presentation. If an old page contains a result, qualification or testimonial, verify that it is still accurate and approved before carrying it forward.

Keep staging and production clearly separated

Use an isolated staging environment while developing. Check its access and indexing settings, and use test delivery arrangements so forms and commerce functions do not accidentally act like production.

At launch, verify the production site’s settings directly. A forgotten noindex instruction, blocked resource or incorrect canonical can undermine an otherwise successful visual change. Do not assume that a setting is correct simply because it was correct on another environment.

Test the live site as a visitor and as a content system

1. Open representative pages and confirm their intended HTTP status.
2. Follow old URLs and check that redirects reach relevant final pages.
3. Check titles, descriptions and canonical URLs for duplication or staging addresses.
4. Confirm important content is available without requiring chat interaction.
5. Check navigation, images and contact routes on mobile.
6. Submit a clearly labelled enquiry and verify the saved details and email receipt.
7. Check the XML sitemap and the production indexing settings.

Google’s AI-feature guidance says ordinary SEO best practices remain relevant to its AI search experiences. A redesign should preserve crawlable, understandable content; it does not need a separate collection of thin pages written for machines.

Monitor after launch and keep rollback practical

Keep the previous release and a usable database backup. Document which content, code and settings changed, and what would trigger a rollback. Restoring a database after new enquiries or orders arrive needs careful handling so those records are not lost.

After launch, review errors, enquiry delivery and important pages in Search Console. Expect that search systems may take time to revisit changed content. Investigate specific problems instead of making repeated emergency changes without evidence.

Common questions

Does changing the design always mean changing the URLs?

No. Keep useful addresses unless there is a good reason to change them. A new appearance does not require a new slug for every service.

Can a plugin handle the whole migration?

A tool can help create redirects or copy data, but someone still needs to decide which pages are useful, verify the mappings and test the result.

How long should redirects remain?

Google advises retaining redirects for as long as possible, generally at least a year. Keep useful old links working longer where practical, and update links you control.

Our website redesign service brings content, design and migration planning together. Talk through your current website before committing to a new structure.