Website migration SEO: protect the journeys that already work

Build an inventory that reflects business value

Start with existing URLs, then add context. Identify pages that attract relevant search visits, generate enquiries, support paid campaigns or answer common customer questions. Include downloadable documents, language versions and older pages linked from important external sources. A navigation export alone will miss content that is no longer in the menu but still receives visitors.

Give each URL a proposed destination and a decision: keep, merge, replace or retire. Record why that decision makes sense for users. This turns a vague request to “preserve SEO” into a reviewable plan. It also exposes disagreements early, before a designer removes a page that sales still uses.

Map destinations by meaning

A redirect should lead to the closest useful equivalent. Sending every retired product or service page to the homepage may technically move a visitor, but it rarely fulfils the original intention. If several articles become one stronger guide, map those addresses to the new guide and check that it genuinely covers their important questions.

Google’s site-move documentation recommends mapping old URLs to new destinations and implementing appropriate permanent redirects. Use that guidance as a technical reference, while keeping the mapping decision human. Nobody should approve hundreds of destinations simply because a spreadsheet contains no empty cells. Review high-value journeys individually and sample the long tail.

Separate the redesign from unnecessary change

A hypothetical consultancy might move to a new platform while rewriting its offer and adding Spanish pages. Those are three different changes. Combining them can be reasonable, but diagnosing a problem becomes harder: did traffic change because a URL disappeared, a message changed or a language version was configured incorrectly?

Keep valuable addresses when there is no strong reason to change them. Preserve useful content until its replacement is ready. If the migration also changes the domain, describe that explicitly in the plan. A staged approach may feel less dramatic than a complete relaunch, yet can make validation and rollback considerably more manageable for a small team.

Test complete journeys before launch

Review a customer arriving from an old search result, a campaign link and a saved product page. Check where they land, whether the page answers the expected question and whether the next action works. Include forms, payments, downloads and language switching. A successful page response does not prove a successful journey.

• Confirm every important old URL has an intentional outcome.
• Check redirects reach the final destination without avoidable chains.
• Review internal links, canonical references and sitemap addresses.
• Remove staging restrictions only where public indexing is intended.
• Verify forms, tracking and consent behaviour in the production environment.
• Keep backups and name the person authorised to pause or reverse the launch.

Plan monitoring before the switch

Create a baseline that includes search visibility, useful landing pages, enquiries and technical errors. Annotate the launch date and any simultaneous campaign changes. During the first review period, investigate broken journeys before debating small ranking movements. Different pages may be discovered and processed at different times; an immediate snapshot is not a complete migration verdict.

Assign someone to inspect redirect exceptions and someone to verify commercial behaviour. These responsibilities often fall between agencies, developers and marketing teams. A short daily exception review immediately after launch can be more useful than a large report delivered weeks later, when customers have already encountered preventable problems.

Define what completion means

Migration is complete when the agreed checks pass and the remaining issues have owners, not simply when the new homepage is visible. Keep a record of retired URLs and redirect rules so future maintenance does not accidentally undo the transfer. Document any content intentionally deferred and its commercial importance.

Google’s people-first content guidance offers a useful reminder for the redesign itself: new pages should help the intended audience. Migration is not an excuse to multiply near-identical pages or remove helpful explanations for a cleaner screenshot. Protect relevance, simplify the buying journey and accept that no responsible migration plan can guarantee unchanged search rankings.