Two web pages connected by a green path illustrating a website migration.

Web Design & Development

Web Design & Development

Website redesign: planning an SEO migration

Website redesign: planning an SEO migration

Daniel Revenco

Daniel Revenco

3 min

19.10.2026

Plan a website redesign with a URL inventory, redirect map, content checks and post-launch monitoring. A practical guide to SEO migration.

A redesign changes how a website looks and works. For search engines, the more consequential change may be a page disappearing, moving or losing the information that answered a query. SEO migration planning therefore starts before the new layouts are drawn.

Build an inventory before making decisions

Collect URLs from your sitemap, analytics and Search Console. Add commercially important pages even when their traffic is low. Record each page’s purpose, available organic traffic, internal links and intended treatment: keep, improve, consolidate or remove.

Low traffic alone is not a sufficient reason to delete a page. It may support existing customers, a campaign or a seasonal service. Every removal needs an explicit reason and an owner who understands the effect.

Map old URLs to relevant destinations

When an address changes, identify the new page that best continues its purpose. A service page should point to its equivalent service, rather than automatically redirecting to the homepage. If content has been removed without a relevant replacement, a 404 or 410 response can be appropriate.

Create a table of old URL, new URL and expected outcome. Test permanent redirects for loops and unnecessary chains. Update internal links as well, so visitors do not need to pass through redirects whenever they navigate the site.

Check the new site before release

Compare important old and new pages. Review titles, descriptions, headings, main content and links in context. Test forms, mobile layouts and images alongside canonical URLs and language alternatives. A visually successful redesign can still fail if its enquiry form no longer delivers messages.

Protect the staging environment from indexing, then ensure that protection does not accidentally reach the public domain. Include robots.txt, meta robots and HTTP responses in the launch checklist. The final sitemap should list public, canonical URLs that are eligible for indexing.

Monitor outcomes after launch

Immediately check a sample from every page category and all key commercial pages. Monitor errors, indexing, organic visits and enquiries. Compare suitable periods and allow for seasonality; a single day’s traffic cannot establish whether a migration succeeded.

Google’s guide to site moves with URL changes covers the technical process. Even a carefully prepared migration can experience temporary fluctuations. Planning reduces avoidable risk but cannot guarantee every ranking remains unchanged.

Frequently asked questions

Does a redesign require changing every URL?

No. Keep clear, useful addresses unless there is a concrete reason to change them. A new visual design does not automatically require a new URL structure.

Can all changes go live on the same day?

Yes, when they have been tested and a rollback plan exists. On a complex site, separating major changes can make problems easier to diagnose.

For ongoing upkeep, read what website maintenance includes. To plan a migration, contact Nightstar.