Website migration: a practical method for SEO continuity

Why can a redesign lose search visibility?

The risk is not limited to a technology change. Pages disappear, addresses change, useful explanations become shorter, indexing is blocked or a form stops working. A more attractive interface can conceal a commercial regression. Compare journeys and content, rather than only before-and-after screenshots.

Separate necessary changes from cosmetic ones. A clear, working address does not need replacing because the visual direction changes. An article’s useful answer should survive its new layout. Reducing unnecessary changes also reduces the number of possible causes when a metric moves after launch.

What should the initial inventory contain?

Combine the sitemap, known analytics addresses and navigation links. Include campaign pages, downloadable documents, older language versions and forms. Compare the sources: no single list is guaranteed to contain everything people still use.

Record each address, its purpose, important content, planned destination and the person approving the decision. Classify pages as retained, merged or removed. Removal should follow a real content or business decision rather than simply making implementation easier.

What makes a useful redirect plan?

A redirect should connect an old address to the page meeting the same need. Sending every old page to the homepage discards context. If no relevant replacement exists, handle removal clearly instead of pretending the content continues elsewhere.

Test each rule in the review environment. Check the final destination, loops and redirect chains. Include address variants actually in use, translated routes and document links. Keep the mapping readable and maintainable rather than burying it in an undocumented configuration.

Which content needs to survive?

Preserve useful answers, meaningful headings, internal links and information needed to choose a service. A new layout can improve readability without removing technical details or conditions. Inspect the rendered page: data stored in a database but missing from the interface helps neither readers nor search engines.

For multilingual sites, test every version of the same journey. Switching language should not always send the visitor to the homepage. Headings, fields, errors and button destinations must follow the chosen language. Multilingual and RTL implementation belongs in the migration acceptance process.

How should you test before launch?

1. Inspect important pages on desktop and mobile.
2. Follow the old address inventory through the redirect rules.
3. Check visible content and actual links within articles.
4. Submit forms using isolated test data.
5. Confirm success messages and the corresponding administration record.
6. Verify indexing rules for the final environment.
7. Prepare a backup and a rollback procedure.

Give each check an owner. “The website works” is not test evidence. “A test enquiry appears in the CRM with its language and origin” is observable. Record the date, environment and limits of the test.

When should launch be postponed?

A broken primary form, widespread redirect errors, missing backups or a rule blocking the entire site are reasons to postpone. A minor visual difference can enter a correction list when it does not obstruct use. Agree on these criteria before launch day.

The rollback procedure must address new data. Restoring files alone is different from restoring a database that may contain fresh enquiries. Separate code, editorial content, media and commercial records. A restore exercise provides stronger evidence than a generic statement that backups are included.

What should you monitor after launch?

Monitor navigation errors, important pages, forms and received enquiries. Compare suitable periods and account for campaigns or seasonal changes. A traffic variation alone does not identify its cause. Investigate affected pages and the changes actually released.

Keep the original inventories and document corrections. Migration does not finish when the new homepage appears; it finishes when essential journeys are verified and critical discrepancies are resolved. Include that follow-up in the proposal.

How should you scope the work?

Bring the current website address, principal offers, connected tools and operating constraints. A technical review separates existing problems from migration risks. The redesign service, performance work and project form then help establish observable deliverables.

Technical reference checked on 20 September 2026: Google’s guidance for site moves with URL changes. The responsibility matrix and acceptance procedure above are a project method, not a search-ranking guarantee.