Rebuilding a website involves more than changing how it looks. It may also mean reorganising content, changing URLs, moving to a different content management system, reviewing functionality or transferring the platform to new infrastructure. If these changes are not planned carefully, pages that already appear in search results can disappear, while forms and lead-generation channels may stop working.
A well-planned website migration should preserve everything that already delivers value: search rankings, organic traffic, backlinks, analytics data and conversion journeys. At the same time, it provides an opportunity to address issues with site architecture, performance, usability and maintenance.
No one can guarantee that there will be no fluctuations after launch, but the risks can be reduced considerably. The key is to include SEO, measurement and technical validation from the start rather than reviewing them once the new website is already live.
Why can a website redesign affect SEO and lead generation?
Search engines build up information about existing pages: their URLs, what they cover, how they link to one another and which external websites refer to them. When a redesign removes or changes these signals without indicating what has replaced them, search engines have to interpret the website again.
The most common problems caused by a poorly coordinated website redesign and SEO process include:
- Old URLs returning 404 errors.
- High-ranking content being removed or significantly reduced.
- Changes to menus and internal links that leave important pages buried too deeply.
- Accidental blocks preventing crawling or indexing.
- Lost metadata, structured data or multilingual settings.
- Forms, telephone links, email links or analytics events no longer recording leads.
- A new platform that is slower or performs poorly on mobile devices.
Therefore, the project must be understood as a controlled reconstruction of a commercial asset, not as a purely visual replacement. Good user-centered web design should improve hierarchy and navigation without erasing the value accumulated by the previous structure.
If the redesign involves rebuilding the platform, changing the CMS or reorganising the architecture, it should be approached as a web development project prepared to preserve and evolve the site, with migration and checks built into the work plan.
What needs to be audited before a website migration?
Before designing the new architecture, it is necessary to obtain a reliable snapshot of the current website. This audit allows you to differentiate between what needs to be kept, what can be improved and what can be removed without harming results.
Content, URLs and rankings
An inventory of indexable URLs must be compiled and cross-referenced with traffic data, search queries, backlinks and conversions. A page with few visits may still be important if it answers a very specific query, receives relevant links or generates high-quality leads.
The audit should also identify duplicate content, useless pages, keyword cannibalisation—where several URLs compete for the same search—and sections that need a new hierarchy. The decision should not be to keep everything automatically, but to know what value each page provides before modifying it.
Channels and conversion points
Redesigning a website without losing rankings also means preserving commercial opportunities. Forms, downloads, bookings, purchases, calls, subscriptions, CRM integrations and thank-you pages must be documented. It is also advisable to record which channels drive visits to specific URLs: search engines, campaigns, newsletters, social media, QR codes or marketing materials.
Technical configuration
The review must include titles and descriptions, canonical tags, XML sitemaps, robots.txt, structured data, languages, media files, performance, analytics and consent management. If security systems or CDNs are used, check that they do not prevent legitimate crawling. The article on how to manage robots.txt and bots without affecting SEO expands on this point.
How should SEO redirects be prepared?
SEO redirects indicate that an old URL has been replaced by another. In a migration, the 301 permanent redirect is the standard choice for moving users and ranking signals to the equivalent new page.
The process must start with a map that links each old URL to its destination. It is not enough to redirect all deleted pages to the homepage: this practice offers little utility to the user and does not properly preserve the context of the original content.
A correct mapping follows these criteria:
- If a new version of the same content exists, redirect to it directly.
- If several pages have been merged, redirect them to the page that integrates the information.
- If there is no exact equivalent, look for the closest thematic destination.
- If the content has been removed and there is no useful alternative, consider keeping a 404 or using a 410 instead of creating a misleading redirect.
Redirect chains—such as an old URL pointing to an intermediate one and that to a third—should also be avoided. Redirects must go directly to the final destination and be tested before and after launch.
What should a CMS change brief include?
A CMS change modifies the foundation from which content and functionality are managed. Therefore, the brief must go beyond asking for texts and images to be copied. It must specify how the structure, data and operations that depend on the website will be preserved.
Requirements that should be defined include the content map, the redirect plan, metadata migration, analytics configuration, forms, integrations, languages, user permissions, backups and an independent staging environment.
In a WordPress migration, the theme, plugins, custom fields and bespoke functionalities must also be audited. Migrating should not mean reproducing all existing dependencies without questioning them. It can be an opportunity to remove unnecessary extensions, improve performance and facilitate updates. To maintain this foundation with sound judgment, it is useful to know the best practices for following the evolution of WordPress without automatically adopting every new feature.
During development, the staging environment must be protected so that it does not appear in search engines. Upon launch, however, any temporary blocks must be removed. Forgetting a “noindex” or a crawl restriction is a simple mistake with significant consequences.
What needs to be monitored after the new website is launched?
Launching does not end the migration. During the first few hours and weeks, you must verify that search engines can access the site, that important pages respond correctly and that commercial channels remain active.
Monitoring should include:
- 404 errors and incorrect redirects.
- Indexing of new URLs and progressive removal of old ones.
- Organic traffic per page and per query type.
- Rankings for priority searches.
- Functioning of forms, purchases and integrations.
- Correct recording of conversions and analytics events.
- Performance, visual stability and mobile experience.
Data should be compared against a baseline collected before the migration. Looking only at total traffic can hide problems: a drop on an important commercial page is not necessarily compensated for by more visits to content that does not generate enquiries.
Rebuilding a website without losing rankings requires coordinating content, design, development, SEO and measurement. When these decisions are made together, migration stops being an improvised risk and becomes an opportunity to preserve what works, correct limitations and build a clearer, more maintainable platform.
We like to talk about these topics before they become a closed project. Tell us about your case.