SEO redesign: how to redesign a website without losing traffic

This page is for the e-commerce or SEO manager preparing a change of structure, URLs, templates or platform. An SEO redesign is how you redesign a website without losing traffic: you run it as a migration, assessing each change for its effect on crawling, indexing and the signals your existing pages have earned.

You will find what you need to decide which URLs to protect, how to build the redirect mapping, what to check before go-live and what to monitor afterwards. The overall framework for ranking an online shop is set out in our guide to ecommerce SEO.

Why a redesign loses traffic

In search terms, a redesign is any change that alters how Google discovers, understands and ranks your pages. Losses come from change that is not measured, and fall into four families:

• URLs changed without redirects: new slugs, new folders, removing ".html" or adding a trailing slash; old addresses return 404s and lose both their rankings and their inbound links.
• Content removed or merged: a page that met an intent disappears, or the target page does not retain what drove its performance (sections, evidence, FAQ).
• Rendering and indexability: JavaScript rendering that hides content or links, a forgotten noindex, inconsistent canonicals, a blocking robots.txt, an incorrect sitemap.
• Broken internal linking: orphan pages, increased depth, internal links that pass through redirects instead of pointing to the new URL.

Add duplication to this: http and https, www and non-www versions coexisting, or poorly managed parameters, facets and pagination. Several URLs then compete for the same content. If a drop persists on one segment after go-live, look for the cause in one of these families.

The stages of a redesign project and their deliverables

A redesign project follows five stages, from scoping to stabilisation. Each one produces a deliverable that the SEO team checks before moving on to the next:

Avoid changing content, structure and tracking at the same time: if traffic drops, you will not know which change is responsible. A gradual redesign, section by section, limits this risk when the timeline allows it.

Building the migration plan

The migration plan is the project's operating document. It links every old URL to its destination, sets the decision rules and makes every risk testable before go-live.

Inventory URLs and establish the baseline

Start with a complete inventory of active URLs, enriched with performance data. Analyse at least the last twelve months to smooth out seasonality. Three sources complement each other:

• Search Console: clicks, impressions, CTR, average position, queries and landing pages.
• Google Analytics 4: organic sessions, conversions and revenue per page, segmented by device and country.
• Site crawl: HTTP status codes, indexability, canonicals, depth, internal links, existing redirects, supplemented by CMS exports, sitemaps and server logs where available.

Use this inventory to identify pages that earn external links (backlinks): the risk is not only losing links, but losing the URL receiving them. Also define alert thresholds, for example a drop in clicks on a priority folder or a spike in 404s.

Decide for each page: keep, merge, redirect, remove

Most of a site's SEO value is concentrated in a limited number of URLs. Rather than starting from scratch, classify each page using four rules:

• Keep if the page drives organic traffic, converts, ranks for strategic queries or earns links.
• Merge if several pages cannibalise the same intent: one target page, the rest 301 redirected.
• Redirect if the content moves, to the new URL that is the closest match in intent and content.
• Remove, with a 410 status, only if the page has no business value and no useful SEO signal.

Build one-to-one 301 redirect mapping

The mapping is an "old URL → new URL" table covering 100% of the inventoried URLs. The priority rule is one-to-one; consolidate only when relevance genuinely improves. Work by template (products, categories, blog), then manually validate critical pages and document exceptions. A redirect to a page that does not meet the same intent often costs more than a technical error.

Align canonicals, hreflang, sitemap and internal linking

Redirects are not enough if other signals contradict the new structure. Check these four points in the plan:

• Canonical: one version per page, aligned with redirects and indexability.
• Hreflang: on an international site, reciprocal tags consistent with the canonicals.
• XML sitemap: only URLs that return 200, are indexable and canonical.
• Internal linking: menus, breadcrumbs and contextual links point directly to the new URLs, with business pages no more than three clicks deep; the method is detailed in our guide to internal linking.

A domain or subdomain change remains the riskiest case: it requires large-scale redirects, verification of both properties in Search Console and consistent https and www handling across all URLs.

Deploying 301 redirects without chains or loops

An excellent strategy can fail with poor implementation. The goal is direct, consistent, mass-verified redirects, implemented at the most reliable level: server or CDN for global rules, CMS only if the team needs to manage them itself.

Choose the right status

Each status sends a different signal to Google. The table below shows when to use each one and the trap to avoid:

Avoid costly mistakes

Four mistakes recur in failed migrations:

• Chains (A → B → C): they consume crawl budget and dilute signals; aim for a single hop.
• Loops (A → B → A): they block crawlers and users.
• Homepage redirects: seen as irrelevant, they may be treated as soft 404s.
• Masked 404s: a page that returns 200 but displays "not found".

Staging and SEO QA: checking before go-live

Staging must be testable by the team without becoming indexable. Protect it with a password or IP restriction; a noindex helps, but is not sufficient on its own if a public link leads to it.

Compare old and new, check by check

Crawl staging in full and compare it with the inventory, starting with high-volume templates and landing pages that convert. The checks and their pass criteria:

Performance deserves a separate check: only 40% of sites pass the Core Web Vitals assessment (SiteW, 2026). So compare the new site's templates with the old ones before go-live rather than after.

Prepare the launch plan

Go-live should be prepared as an operation in its own right. Set in advance:

• a freeze on critical SEO changes in the days before launch;
• a deployment window with low traffic and the team available;
• a realistic rollback plan: who decides, by which criteria, and within what timeframe;
• a named owner for redirects, the sitemap, Search Console and analytics.

Cases specific to e-commerce

An online shop adds risks that a brochure site does not face: a living catalogue, thousands of URLs generated by filters, variants and a product feed. The "one product = one URL" rule must survive the redesign. The cases to handle in the mapping:

A platform change (from PrestaShop to Shopify, for example) imposes its own URL conventions: the mapping is then built template by template, and checked on the product and category pages that generate revenue. Also check that each migrated product page keeps its content and structured data.

D-30, D-Day, D+30: the migration timeline

The method comes down to three phases, each with verifiable actions.

D-30: prepare

• Extract baseline KPIs (Search Console, GA4) and set alert thresholds.
• Complete the inventory, the page classification and the one-to-one mapping.
• Record baseline AI citations on a set of questions.
• Prepare the target sitemap and the staging QA plan.

D-Day: go live

On launch day, the order of checks matters: redirects come before everything else.

• Validate redirects on critical pages, then in bulk.
• Check robots.txt (the staging file must not go to production), meta robots, canonicals and HTTP statuses.
• Confirm that GA4 and Google Tag Manager tracking is recording.
• Submit the new sitemap in Search Console.

D+30: stabilise

• Day 1: urgent checks on 404s, 5XX errors, redirects and coverage.
• Day 7, Day 14, Day 30: analyses segmented by folder, page type, device and country.
• Prioritise fixes to redirects, internal linking, canonicals, missing pages and duplication.
• Recover links pointing to removed URLs, then document a stable version before any new workstream.

Monitoring the migration: Search Console, rankings and AI citations

Monitoring compares each page with itself, before and after go-live: daily in week one, then weekly, segmenting rather than averaging.

What Search Console shows

Search Console confirms what Google actually sees; our guide to Google Search Console details its reports. After a migration, monitor first:

• indexed and excluded pages, especially those excluded for noindex, canonical, duplication or soft 404;
• crawl errors: 404s on pages with traffic or links, chains, loops;
• the canonical chosen by Google in URL inspection, not only the one you declare;
• impressions, clicks and rankings by page and query, compared with the baseline.

Do not confuse impressions with clicks: with the rise of zero-click searches, a site can remain visible whilst receiving fewer visits. Also track rankings for a set of strategic keywords, separating brand and non-brand queries, and conversions by landing page in GA4. If a segment stays below its baseline, a targeted SEO audit of that folder will identify the cause.

Measure AI citations before and after

At the time of writing, AI Overviews and AI Mode have been available in France since summer 2026 and cite sources; Search Console counts them without distinguishing them. To know whether the redesign has changed your presence in generated answers, record before go-live, question by question, whether your brand is named, your domain cited or absent, then repeat the same check afterwards.

Also check that the new robots.txt allows GPTBot, PerplexityBot and Google-Extended, and that templates retain titles, lists, tables and FAQs: generative engines cite pages that are indexed, structured and accessible. A change observed after go-live remains a correlation, not proof of causation.

Depending on your situation

Depending on your starting point, these guides complete the method:

• You are launching a new site rather than a redesign: see how to design a site that is visible from launch.
• Your product pages change template during the redesign: follow the method to make each product page readable by Google and AI.
• Your new site is slower than the old one: run a website performance audit before fixing anything.
• JavaScript rendering or indexing is causing problems: rely on our guide to technical SEO.

Before you start the mapping, the Incremys 360 GEO & SEO audit provides the diagnosis and map of the existing site, along with its AI presence by keyword (brand named, domain cited, domain as source, absent): a basis for comparing each page with itself after go-live.

FAQ: redesigns, migrations and maintaining SEO results

How do you redesign a website without losing traffic?

By treating the redesign as a migration. Establish a baseline in Search Console and GA4, inventory every URL, build one-to-one 301 mapping, check staging with a full crawl, then monitor each segment after go-live. Most lasting losses come from unredirected URLs, duplication or blocked indexing.

Should you redirect every old URL?

Yes, any URL with traffic, links or rankings should get a 301 to the closest page in intent. Only pages with no business value and no SEO signal can return a 410. Avoid bulk redirects to the homepage: Google may treat them as soft 404s and the old page's signals are lost.

How long does the drop last after a migration?

No timeframe applies to every site: it depends on crawling, indexing and signal consolidation. Rather than waiting, measure each segment against its baseline at Day 7, Day 14 and Day 30. A drop that persists on one folder points to a specific problem to fix: redirects, canonicals, rendering or internal linking.

Visual redesign or SEO redesign?

A visual redesign changes the look without touching URLs or templates; its SEO risk stays low if content and structure remain identical. As soon as URLs, site architecture, platform or templates change, it is an SEO redesign, to be run with an inventory, a mapping and pre-launch checks.

What is the difference between a redesign, a migration and a Change of Address?

A redesign covers all changes to structure, URLs, platform or templates. A migration is the method that manages them without losing earned signals. A Change of Address means a domain change: it requires large-scale 301 redirects and verification of both properties in Search Console.

What actions should you take in Search Console at launch?

Submit the new sitemap as soon as you go live. Then monitor indexed and excluded pages, crawl errors and unusual redirects. Use URL inspection to check the canonical chosen by Google and to request re-crawls of critical URLs after a significant fix.

What should you do with products removed from the catalogue during a redesign?

301 redirect each removed product page to the product that replaces it or, failing that, to its category. If no equivalent exists and the page had neither traffic nor links, a 410 is acceptable. Also update the Merchant Center feed so it no longer points to the old URLs.