Redesign SEO: migrate a site without losing its traffic to 2026

Your new site should not erase your organic capital.
Prepare the rocker before touching the design.

1. Key figures

2. Introduction

A redesign project often resembles a moment of renewal: new design, new CMS, new pages, new promise, new breath. This is sometimes true. But for SEO, it is also a moment of fragility. Deleted URL, poorly mapped redirect, title rewritten without intention, diluted pillar page, heavier template, forgotten markup: the loss is not always visible on launch day. It arrives later, in Search Console, as impressions erode.

We defend a simple position: the project should not start with the model. It should start with the inventory of assets. Pages that capture traffic, queries that convert, cited content, backlinks, forms, structured data, sales paths, analytics events.
Without this mapping, we cannot recast. We're moving in the fog.

3. Symptoms: weak signals of poorly prepared migration

We quickly recognize a risky project: the old URLs are not inventoried, the redirections are planned "at the end", the new site map ignores the pages that perform well, the content is rewritten to be shorter, the metadata is treated as a detail, the forms change without a tracking plan, the staging is blocked from the engines but never crawled:
The project is moving forward, but the organic capital is not protected.

Friction appears at launch. Pages respond to 404. Redirects create chains. Old service pages lose their intent. FAQs disappear. The images become heavier. Structured data doesn't track. The teams are looking at the new site, but the engines are looking at the old direction.

No inventory, no conservation.
No mapping, no continuity.
No tracking, no fix rapide.

The seriousness of the project can be judged in the weeks that follow, not only in the presentation of the design.

4. Actors: Google, Bing, Search Console, CMS, DNS, analytics, business team

A SEO migration involves more actors than one might think. Success comes from their coordination.

Where the SEO sees URLs, the salesperson sees objections. Where the developer sees roads, the manager sees revenue. Where the CMS sees collections, the reader sees promise.
The toggle protocol must hold these three readings together.

5. Definition: what is a migration SEO

A SEO migration is the set of decisions that make it possible to modify a site, its CMS, its domain, its URLs, its templates or its content without breaking the continuity of crawling, indexing, understanding and conversion.

This definition matters. The work is not limited to 301 redirects. It is an asset conservation operation: preserving the intention, the proof, the reputation, the structure, the data, the links, the paths.
The shape may change. The memory must remain.

6. Why this is becoming a priority in 2026

90,39 % global share for Google in May 2026: classic search remains a massive base (StatCounter Global Stats). But the context changes. Generative engines take up, summarize, compare and cite content. Google says its AI Overviews cover more than 200 countries and territories and more than 40 languages. A migrated page must therefore remain accessible to robots, understandable by the engines and usable in summary responses.

Performance adds a second pressure. The Web Almanac 2025 measures a median home page of 2,56 MB on mobile and 2,86 MB on desktop. The construction site can reduce this debt. It can also make it worse if you add scripts, animations, fonts, unoptimized images and unnecessary libraries.

Finally, monitoring becomes more demanding. A team can no longer just look at overall traffic. It tracks queries, pages, conversions, forms, indexing errors, logs when possible, and lead quality.
It is no longer an aesthetic project. It is a commercial continuity operation.

7. The five types of redesigns that threaten traffic

Not all redesigns carry the same risk. The type of change must be qualified before choosing the level of preparation.

The most common risk does not take the form of a spectacular failure. It is due to a distributed loss: ten pages less visible, twenty weakened queries, three forms less traced, a poorer mesh.
The loss spreads. So it becomes more difficult to correct.

8. Recommended method: 10 blocks to secure the flip-flop

The method recommended below is not a proprietary method Logiks. It is based on migration best practices documented by Google Search Central, SEO fundamentals, technical audit and project experience.

In the workshop, we use it as a setup before the shot. We output the URLs, the numbers, the dependencies. Only then do we arbitrate.

8.1. Inventory existing URLs

Export all known URLs: site crawl, sitemap, Search Console, analytics, CMS, backlinks if available. Classify each URL according to its role: traffic, conversion, proof, sales support, branding, technical page.

An address without a role can be deleted. A URL that sells, reassures or attracts deserves to be protected.

8.2. Identify valuable pages

Not all pages have the same value. Some capture impressions. Others convert little but reassure a prospect. Still others support a pillar page through networking. So the decision is not just SEO; it is commercial.
Traffic is not the only asset. Evidence matters too.

8.3. Map old and new URLs

Each URL kept, merged or deleted must have a status: keep, redirect, merge, deindex, delete. Redirects should point to the closest equivalent, not to the home page for convenience.
A lazy redirect is a disruption of meaning.

8.4. Preserve search intent

Before rewriting content, identify its intention: information, comparison, decision, proof, transaction, support. The new version may be clearer, more beautiful, denser. She must not lose the question that the old page answered.
We do not migrate blocks. We migrate intentions.

8.5. Check templates SEO

Control H1, title, meta description, canonical, robots, Open Graph, schema, breadcrumbs, pagination, collection pages, categories, tags and author pages. On a CMS, a template error is sometimes repeated on 200 pages.
The detail takes on an industrial dimension.

8.6. Test staging like a real site

The staging site must be crawled, even if it remains blocked from public indexing. We check HTTP statuses, internal redirects, broken links, orphan pages, canonicals, loading times, heavy assets and missing content.
What we don't test before, we discover later. More expensive.

8.7. Preserve the internal network

The site often modifies menus, link blocks, pillar pages and recommendation modules. The network must be rebuilt around strategic pages: services, sectors, customer cases, guides, FAQ, proof content.

Google points out that links help you discover pages and understand their meaning. The mesh is not a decoration.

8.8. Keeping Structured Data Useful

Structured data must follow the redesign: Organization, BreadcrumbList, BlogPosting, FAQPage, Product or Service when the template and content justify it. The schema must not invent information missing from the page.
No semantic theater. Consistency.

8.9. Launch with a monitoring protocol

On launch day, monitor statuses, redirects, important pages, sitemap, Search Console, analytics, forms, events and Core Web Vitals. The first 48 hours are used to correct quickly.
Success depends on follow-up as much as preparation.

8.10. Compare after 30, 60 and 90 days

Compare impressions, clicks, positions, conversions, landing pages, queries, errors and qualified leads. A temporary setback may occur. An unmeasured drift turns into a lasting loss.
The goal is not to throw. The objective is to find, then exceed, the useful level.

9. Logiks Tips: Protect Intent Before Mockup

We do not recommend starting with an aesthetic workshop. Design matters, of course. But the first asset of a B2B site remains its decision architecture: what questions the prospect asks, what evidence reassures him, what content moves him forward, what pages convert.

First tip: create a living inventory of pages to protect. For each important URL, we note the query, intent, business role, future status, redirect, owner and risk.

Second tip: keep a “proof” column. Content can generate little traffic but be used in a sales cycle: customer case, comparison, technical FAQ, sector page, security page, price page. Deleting it can fragilize sales speech without immediately appearing in the SEO numbers.

Third tip: refuse redirects for convenience. An old guide "SME cybersecurity audit" should not go to a generic "services" page. It must join the page closest in intent, or be merged cleanly into content that really meets the same need.
Finally, we recommend treating the redesign as a three-step operation:

• retain existing assets;
• clarify the new architecture;
• measure what the seesaw actually changes.

This is not a technical migration. It’s a transmission of value.

10. Decision grid: is your redesign ready to go into production?

If two lines remain in "Fragile", the launch must wait. One week of preparation is better than three months of recovery.

11. Common Mistakes: Six Decisions That Cost Traffic

First trap: delete pages because they seem old. Dated content can still serve profitable intent. We improve it before burying it.

Second drift: merge too wide. Grouping ten pieces of content into a generic page may seem neat. But if the intentions were different, the whole thing loses precision.

Third weakness: changing URLs unnecessarily. A stable address is an asset. Modifying it must respond to a real reason: architecture, readability, consolidation, technical debt.

Fourth pitfall: neglecting forms and events. The new site may keep traffic but lose measurement of conversions. In this case, the team no longer drives; she guesses.

Fifth risk: weighing down the front. Median pages are already heavy according to HTTP Archive. Adding animations, third-party scripts, and uncompressed images can turn a sleek design into mobile friction.

Last point: forget about generative engines. Shorter, less sourced, less structured content may be pretty for a busy human, but less quotable to an assistant.

12. Action Plan 30 / 60 / 90 days

12.1. Within 30 days

• export all URLs;
• identify pages with traffic, conversion and proof;
• map intentions;
• choose the content to keep, merge, redirect or delete;
• define the SEO templates of the future CMS;
• prepare the tracking plan;
• open Search Console properties if necessary.

We haven't touched production yet. We are preparing the site.

12.2. Within 60 days

• write or migrate strategic content;
• build the redirection mapping;
• crawl the staging;
• correct internal links, canonical, robots and sitemap;
• test performance, forms, events, structured data;
• document remaining risks.

The project becomes controllable.

12.3. Within 90 days

• launch according to a written protocol;
• monitor the first 48 hours;
• correct indexing errors;
• compare priority pages and queries;
• update content that is going backwards;
• enrich the network around the new pillar pages.

At this point, the seesaw ceases to be an event. It becomes a steering.

13. FAQ: SEO redesign and migration

13.1. Does a redesign always lose traffic?

No. A well-prepared project can retain traffic and improve conversions. The risk mainly comes from modified URLs without mapping, impoverished content, lost linking, degraded performance or absent tracking.

13.2. Should we keep all the old URLs?

No. You must keep or redirect URLs that have value: traffic, backlinks, conversions, commercial proof, networking role. Pages of no use may be deleted, but this decision must be documented.

13.3. How long should you monitor a SEO migration?

The first 48 hours are used to detect critical errors. The first 30 days show the first signals. 60 to 90 days allow us to distinguish a normal adjustment from a structural loss.

13.4. What to do in Search Console?

Submit the sitemap, monitor for indexing errors, monitor important pages, compare impressions and clicks, and check for experience or structured data issues. In the event of a change of domain, Google's change of address procedure must be studied.

13.5. Is structured data a priority?

Yes, when they reflect the visible content. They don't make up for a bad page, but they help clarify the entity, breadcrumbs, article, organization, and FAQ.

14. Conclusion: the redesign becomes an asset conservation operation

A SEO redesign is not about changing the skin of a site. It consists of transmitting a capital: pages, links, evidence, intentions, data, conversions, reputation.

The new site must be clearer. He must also remember what the old one had built. This is where the maturity of the project comes into play: do not confuse novelty and progress, aesthetics and performance, launch and success.

For Logiks, the right overhaul comes down to three verbs: inventory, preserve, measure. The rest comes later.

This is no longer a site redesign.
It becomes a commercial continuity operation: preserve, clarify, accelerate.

15. Main sources

• Google Search Central - Site moves and migrations - accessed on June 17 2026 - https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
• Google Search Central - Search Engine Optimization Starter Guide - accessed on June 17 2026 - https://developers.google.com/search/docs/fundamentals/seo-starter-guide
• Google Search Central - Link best practices for Google - accessed on June 17 2026 - https://developers.google.com/search/docs/crawling-indexing/links-crawlable
• Google Search Central - Introduction to structured data markup in Google Search - accessed on June 17 2026 - https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
• Google - AI Overviews expand to over 200 countries and territories, more than 40 languages - 20 mai 2025 - https://blog.google/products-and-platforms/products/search/ai-overview-expansion-may-2025-update/
• StatCounter Global Stats - Search Engine Market Share Worldwide - May 2026 - https://gs.statcounter.com/search-engine-market-share
• HTTP Archive - Web Almanac 2025, Page Weight - accessed on June 17 2026 - https://almanac.httparchive.org/en/2025/page-weight
• HTTP Archive - Web Almanac 2024, Page Weight - accessed on June 17 2026 - https://almanac.httparchive.org/en/2024/page-weight