You cannot guarantee zero volatility during an e-commerce website migration. Google must recrawl and process the new URLs, customers need to adjust to the new experience, and unexpected technical or commercial problems can still occur.

However, you can substantially reduce the risk of losing rankings, traffic and revenue by treating the migration as a controlled URL-and-revenue preservation programme—not simply as a website launch.

The four essentials are:

1. A complete inventory of every valuable existing URL
2. A one-to-one redirect map connecting old pages to their closest new equivalents
3. Rigorous technical, tracking and commercial quality assurance before launch
4. Intensive monitoring and rapid correction after the new site goes live

Google’s site-migration guidance recommends preparing and testing the new site, mapping old URLs to corresponding new URLs, using permanent server-side redirects, monitoring both the old and new sites and retaining redirects for at least one year.

For an e-commerce business, that is only the technical foundation. A successful migration must also protect product availability, paid-media destinations, Merchant Center feeds, checkout performance, conversion tracking and the landing pages responsible for organic revenue.

Why e-commerce migrations are commercially dangerous

An e-commerce migration affects several connected systems simultaneously.

Search engines must understand where existing pages have moved. Customers must still find the products and information they expect. Advertising, email, affiliates and feeds must point to valid destinations. The new site must preserve or improve conversion.

A migration can therefore preserve rankings but still lose revenue if:

• Product variants stop working
• Important filters disappear
• Mobile checkout becomes harder
• Prices or stock are incorrect
• Payment methods fail
• Product feeds are disapproved
• Conversion tracking breaks
• Delivery information is missing
• High-intent landing pages are redirected poorly

Equally, a website can look and convert well for direct visitors while losing organic visibility because old URLs return errors, canonical tags are wrong or useful category content has been removed.

The migration must be managed as both an SEO project and a trading-continuity project.

What counts as an e-commerce website migration?

A migration can involve one or several substantial changes:

• Moving to a new domain
• Replatforming, such as Magento to Shopify
• Moving from Shopify to a headless architecture
• Changing URL structures
• Reorganising categories and navigation
• Altering faceted filtering
• Redesigning product and category templates
• Changing JavaScript rendering
• Consolidating or removing content
• Merging brands or websites
• Moving subdomains or international folders
• Changing language, market or currency structures
• Switching from HTTP to HTTPS

The more changes introduced simultaneously, the harder it becomes to diagnose a loss.

If possible, avoid combining a domain move, new platform, new information architecture, complete content rewrite, international expansion and major visual redesign in one release.

Sometimes the commercial circumstances make that unavoidable. When it is, the baseline, testing, responsibilities and recovery plan must be exceptionally clear.

Define success before development begins

“The new website launched on time” is not a sufficient definition of success.

Agree measurable migration objectives such as:

• Priority organic landing pages remain indexable.
• Valuable old URLs redirect to relevant live equivalents.
• Organic revenue recovers within an agreed period.
• Conversion rate does not fall below a defined threshold.
• Product feeds and paid campaigns remain operational.
• Transaction and revenue tracking reconcile with the commerce platform.
• Checkout works across priority browsers, devices and payment methods.
• No critical crawl, canonical or indexation problem remains unresolved.

Define both tolerances and escalation thresholds before launch.

For example:

• A small temporary ranking fluctuation may be monitored.
• A 20% fall in organic revenue across priority categories may trigger immediate escalation.
• A checkout or payment failure is a launch-critical incident.
• Accidental noindex tags on commercial templates require immediate rollback or correction.

Pre-agreed rules reduce hesitation when decisions must be made quickly.

Establish migration governance

Every migration needs named ownership.

At minimum, identify responsibility for:

• Overall migration leadership
• SEO and URL mapping
• Development
• Infrastructure and hosting
• Product and merchandising data
• Analytics and consent
• Paid Search and product feeds
• UX and conversion
• Content
• Quality assurance
• Launch approval
• Incident escalation

Create a central migration log containing:

• Risks
• Owners
• Deadlines
• Dependencies
• Test status
• Redirect decisions
• Launch blockers
• Post-launch incidents
• Resolution status

SEO should not be invited to review the site two days before launch. URL structure, navigation, templates, canonicals and rendering must be considered while the new platform is being designed.

Start with revenue protection

Before the new site is built, identify the URLs that currently create commercial value.

Do not rely on the XML sitemap alone. A sitemap can omit legacy URLs that still rank, receive links, generate sales or appear in paid campaigns.

Build a master inventory using:

• A complete crawl of the live website
• Current and legacy XML sitemaps
• Image and video sitemaps where relevant
• Google Search Console page and query data
• GA4 organic landing-page data
• Commerce-platform orders and revenue
• Gross-margin data where available
• Paid Search landing pages
• Merchant Center product destinations
• Email, affiliate and social campaign links
• Backlink data
• Server logs where available
• Internal search and customer-service insights

The inventory should contain every old URL that search engines, customers or marketing channels may still use.

Categorise URLs by type and importance

Tag each URL as one of the following:

• Homepage
• Category or collection
• Product
• Brand
• Buying guide or editorial content
• Filter or facet
• Campaign landing page
• Customer-service page
• Legal page
• Out-of-stock product
• Discontinued product
• Account, basket or checkout page
• Image or downloadable asset

Then add performance and risk fields:

• Organic sessions
• Search Console clicks and impressions
• Rankings or visibility
• Orders and revenue
• Gross profit
• Conversion rate
• Average order value
• Backlinks and referring domains
• Paid-media usage
• Stock status
• Strategic category
• Migration priority

This transforms the URL inventory from a technical list into a commercial protection plan.

Prioritise the revenue-driving URLs

Record the top 100–500 URLs responsible for:

• Organic revenue
• Organic gross profit
• Organic traffic
• Non-brand visibility
• Paid-media spend
• External links
• Strategic categories

The exact number depends on the site’s size. A large retailer may need priority groups rather than one list.

These pages should receive enhanced testing before and immediately after launch. If a migration issue affects one of them, the business needs to know within hours—not at the next monthly report.

Build the redirect map before the new site is finished

Redirect planning must begin before launch and should influence the new site structure.

Every valuable old URL needs one deliberate outcome.

Old-page situation	Correct destination
Product has a direct equivalent	Matching new product URL
Product has been replaced	Closest successor product
Discontinued product with relevant alternatives	Useful category, brand or alternative-product page
Category remains available	Matching new category URL
Several old pages are genuinely consolidated	New consolidated page covering the same intent
Buying guide has been updated	Equivalent new guide
Page has no relevant replacement	Genuine 404 or 410, depending on the circumstances

The destination must serve the same or closely related customer intent.

Why blanket homepage redirects are dangerous

Do not send large groups of unrelated old URLs to the homepage.

Google advises against redirecting many old pages to one irrelevant destination because it can confuse users and may be treated as a soft 404.

A customer clicking an old product URL expects:

• The same product
• A genuine replacement
• A highly relevant category
• An explanation and useful alternatives

The homepage rarely satisfies that intent.

Redirecting everything there may retain a technically successful status code while destroying both user relevance and page-level search signals.

Use permanent server-side redirects

When a URL has moved permanently, use a permanent server-side redirect—normally HTTP 301 or 308.

Google recommends permanent server-side redirects where possible because they clearly signal that the new destination should replace the old URL in Search.

Avoid relying on:

• Temporary 302 or 307 redirects for permanent moves
• Client-side JavaScript redirects
• Delayed meta refreshes
• Manual pages asking users to click again

Other redirect methods can sometimes be interpreted, but server-side permanent redirects are the most reliable choice for a permanent migration.

Keep redirects direct

Each old URL should redirect straight to the final live destination:

Old URL → final new URL

Avoid:

Old URL → previous redirect → temporary URL → final URL

Google advises avoiding redirect chains and linking directly to the final destination. Chains add latency, increase failure risk and create unnecessary crawling work.

Audit historic redirects before launch. An old redirect may need to be rewritten so it points directly to the new final URL rather than passing through multiple generations of site structure.

Decide how to handle discontinued products

Discontinued products require commercial judgement.

If the URL still receives relevant demand, backlinks or traffic, consider keeping a useful page that explains:

• The product is discontinued
• Its closest replacement
• Compatible alternatives
• Relevant category options
• Support information

If a successor exists, redirecting may be appropriate. If there is no relevant replacement and the page has no ongoing value, a genuine 404 or 410 may be more honest than an irrelevant redirect.

The decision should consider customer intent, link value, search demand and catalogue strategy.

Preserve the signals that earned rankings

A new design often removes content because it appears visually inconvenient. This can destroy useful relevance and conversion information.

Preserve or improve:

• Page titles and meta descriptions
• Main headings
• Category copy
• Product descriptions
• Specifications and attributes
• Product identifiers
• Reviews
• FAQs
• Buying guidance
• Delivery and returns information
• Internal links
• Images and video
• Structured data

The content does not have to remain in the same layout. It must continue meeting the customer need and giving search engines enough information to understand the page.

Preserve product identifiers and structured data

Where appropriate, retain or correctly migrate:

• SKU
• GTIN
• MPN
• Brand
• Price
• Currency
• Availability
• Variants
• Review information
• Product images

Validate that structured data matches the visible content on the page.

A technically valid product schema implementation is not sufficient if the displayed price, stock or variant information is inconsistent.

Use rich-results testing and crawl-based validation across template samples and large page groups.

Technical requirements before launch

The production site must be:

• Crawlable
• Renderable
• Indexable
• Canonicalised correctly
• Internally linked
• Fast and stable enough for customers
• Accessible on mobile devices

Check specifically for:

• Accidental noindex directives
• Robots.txt blocks
• Password protection
• CDN or firewall restrictions
• Canonicals pointing to staging or old URLs
• Canonicals pointing to the wrong variant
• Broken JavaScript rendering
• Orphan pages
• Duplicate templates
• Pagination errors
• Faceted-navigation indexation
• Hreflang mistakes
• Mixed protocol or hostname references
• Incorrect status codes
• Broken image and asset URLs

Staging should be protected from indexation, but the protection must not accidentally transfer to production.

Update internal links to final URLs

The new website should link directly to new URLs rather than relying on redirects internally.

Update:

• Navigation
• Breadcrumbs
• Product recommendations
• Category links
• Editorial links
• Footer links
• Canonicals
• Hreflang
• Structured-data URLs
• Image URLs where changed

Internal links help customers and search engines understand the new architecture. Sending all internal traffic through redirects creates unnecessary latency and weakens clarity.

Build clean XML sitemaps

The new sitemap should include only URLs that are:

• Canonical
• Indexable
• Live
• Intended to appear in Search
• Returning HTTP 200

Separate sitemaps by page type where scale makes diagnosis easier—for example products, categories, editorial content and images.

After launch, submit the new sitemaps in Search Console and monitor processing and indexation.

Google’s migration guidance also describes monitoring old and new sitemap patterns as pages transfer from the old site to the new one.

Crawl and test staging thoroughly

Run a complete crawl of staging and compare it with the live-site inventory.

Validate:

• Status codes
• Indexability
• Canonicals
• Robots directives
• Internal links
• Orphan pages
• Titles and headings
• Content parity
• Breadcrumbs
• Pagination
• Hreflang
• Structured data
• Mobile rendering
• JavaScript rendering
• Image loading
• Page performance
• Faceted navigation

Test representative examples from every template and bulk-check the complete URL set wherever possible.

Do not approve launch based on the homepage, a category and two products. E-commerce problems often appear only on particular templates, variants, brands, countries or catalogue conditions.

Validate analytics before launch

Tracking must be tested before migration day.

Confirm:

• GA4 page views
• E-commerce events
• Transaction IDs
• Revenue and currency
• Product and item data
• Refund handling
• Consent management
• Cross-domain tracking
• Payment-provider referrals
• Google Ads conversion tracking
• Meta and Microsoft tags where relevant
• Affiliate tracking
• CRM and email integrations

Run complete test purchases and reconcile them across the website, analytics platform, advertising systems and back office.

If tracking breaks at launch, the team loses the evidence needed to distinguish a measurement problem from a real trading loss.

Protect Merchant Center and Paid Search

Migration planning should include all paid and shopping destinations.

Update and test:

• Merchant Center feeds
• Product landing-page URLs
• Google Ads final URLs
• Performance Max asset destinations
• Microsoft Ads
• Dynamic remarketing parameters
• Affiliate links
• Email campaign templates
• Social adverts
• Marketplace or partner links

Product feeds should not rely permanently on redirects. Update them to the final URLs and monitor disapprovals, crawl issues, price mismatches and availability mismatches.

Protect conversion, not only SEO

A site can preserve organic traffic while losing revenue because the new experience converts worse.

Test the full customer journey on desktop and mobile:

1. Organic landing page
2. Navigation or on-site search
3. Product selection
4. Variant selection
5. Add to basket
6. Basket
7. Checkout
8. Payment
9. Confirmation page and email

Validate:

• Prices
• Stock
• Variants
• Voucher codes
• Delivery thresholds
• Delivery dates
• Tax
• Payment methods
• Account and guest checkout
• Address validation
• Confirmation and tracking

Compare important filters and sorting options with the old site. Removing a popular filter can reduce category conversion even when rankings and traffic remain stable.

Capture an 8–12-month baseline

Before launch, record enough history to distinguish migration effects from normal seasonality.

Capture:

• Organic sessions
• Search Console clicks and impressions
• Organic orders and revenue
• Gross profit
• Conversion rate
• Average order value
• New and returning customers
• Assisted revenue
• Category and product-page performance
• Indexed URL counts
• Crawl health
• Rankings or visibility
• Paid-media spend
• Stock availability
• Promotions
• Page performance

Create specific baselines for priority categories and URL cohorts rather than relying only on a site-wide total.

Choose a low-risk launch window

Avoid launching during:

• Black Friday
• Christmas peak
• A major sale
• A new product launch
• A planned advertising surge
• A critical trading weekend
• A period without full technical coverage

Choose a time when the business can monitor and correct problems immediately.

Freeze non-essential releases around launch. Unrelated changes create additional variables and make diagnosis harder.

Create a launch-day command plan

The launch plan should include:

• Named decision-maker
• Technical contacts
• SEO contact
• Analytics contact
• Paid-media and feed contact
• Trading and merchandising contact
• Launch checklist
• Rollback criteria
• Communication channel
• Incident severity levels
• Status reporting frequency

Each critical check should have an owner and deadline.

Do not assume someone else is checking redirects, checkout or tracking.

Launch-day SEO checks

Immediately after release:

• Remove production indexation blocks.
• Confirm robots.txt is correct.
• Test priority old URLs.
• Confirm single-hop permanent redirects.
• Crawl the full old URL inventory.
• Crawl the new website.
• Validate status codes and canonicals.
• Check navigation and internal links.
• Confirm sitemaps are accessible.
• Inspect priority URLs in Search Console.
• Test structured data.
• Check server availability and response times.

Every priority old URL should lead to a live, relevant and indexable final page returning HTTP 200 after one permanent redirect.

Launch-day commercial checks

• Complete purchases on key devices.
• Test payment methods.
• Check prices, variants and stock.
• Validate delivery rules.
• Confirm confirmation emails.
• Verify transactions in GA4.
• Verify advertising conversions.
• Review Merchant Center diagnostics.
• Check paid landing pages.
• Monitor payment failures.
• Review live conversion rate and revenue.

A successful crawl does not mean the store is trading correctly.

Signal the migration to Google

Submit the new XML sitemaps in Search Console.

If the domain changes:

• Verify the old and new domains in Search Console.
• Verify relevant hostname variants.
• Use the Change of Address tool from the old property.

Google recommends the Change of Address tool for domain or subdomain moves. It is not required for a simple HTTP-to-HTTPS migration.

Update important external profiles and campaign links to the new destinations where possible.

Keep redirects for at least one year

Google recommends retaining redirects for as long as possible, generally at least one year. This gives Google time to recrawl old URLs and transfer signals to the new destinations.

From the customer’s perspective, some redirects may be worth keeping indefinitely—particularly where old links continue to appear in bookmarks, emails, external websites or printed material.

Continue monitoring old URLs that receive:

• External links
• Customer visits
• Googlebot activity
• Referral traffic
• Campaign traffic

Do not remove redirect infrastructure simply because the initial recovery appears complete.

What should you monitor after migration?

Use a dashboard that separates technical health, organic visibility, revenue and trading performance.

Area	Daily during first 14 days	Weekly during first three months
Crawling and indexation	Errors, blocks, noindex, robots.txt, redirects, canonicals and sitemap processing	Indexed-page trends, crawl volume and duplicate/canonical patterns
Organic visibility	Clicks, impressions, CTR, priority positions and landing pages	Page-group recovery against baseline
Revenue	Organic orders, revenue, margin, conversion rate, AOV and refunds	Gross profit, assisted revenue and new-versus-returning customers
Trading health	Stock, pricing, checkout, feeds, payment failures and tracking	Category conversion, availability, returns and feed disapprovals
Redirect health	404s, chains, loops and irrelevant destinations	Legacy URLs still receiving visits, links or crawler activity

Monitor both the old and new sites during a domain move. Google’s guidance notes that traffic should fall on the old site while increasing on the new one.

Expected volatility versus a serious problem

Some temporary search fluctuation is normal while Google processes changed URLs. Google states that small-to-medium sites can take several weeks for most pages to move, while larger sites may take longer.

Do not treat every short-term movement as a crisis.

Escalate rapidly when:

• Priority pages are blocked
• Important URLs return errors
• Redirects lead to irrelevant pages
• Canonicals point to old or staging URLs
• Commercial pages disappear from the index
• Organic revenue and conversion both decline materially
• Checkout or payments fail
• Product feeds become disapproved
• Tracking stops recording transactions
• Large groups of old URLs have no mapping

Adjust for seasonality, stock, promotions and paid-media changes before attributing every decline to the migration.

Diagnose the shape of a traffic loss

Different patterns suggest different causes.

Impressions and clicks both fall

Possible causes:

• Indexation loss
• Redirect failure
• Canonical errors
• Removed content
• Lost internal links
• Changed search demand

Impressions remain stable but clicks fall

Possible causes:

• Changed titles or snippets
• Different search-result appearance
• Less attractive proposition
• Ranking distribution changes

Traffic remains stable but revenue falls

Possible causes:

• Conversion problem
• Missing products
• Broken variants
• Price or delivery issue
• Checkout friction
• Tracking error

Paid performance declines after migration

Possible causes:

• Invalid landing pages
• Feed disapprovals
• Tracking failure
• Changed product identifiers
• Slower or weaker landing pages

The recovery plan should address the observed pattern rather than applying broad SEO changes indiscriminately.

Common migration mistakes

Building the redirect map after launch

This leads to rushed, incomplete and commercially weak decisions.

Redirecting everything to the homepage

This fails to preserve customer intent and may be treated as a soft 404.

Leaving internal links pointed at old URLs

The new site should link directly to final destinations.

Removing useful content during redesign

Category copy, specifications, reviews and guidance may have supported both ranking and conversion.

Launching with staging directives

Accidental noindex, robots blocks or staging canonicals can remove large sections from Search.

Measuring only traffic

A migration can retain sessions while losing conversion and profit.

Forgetting Paid Search and feeds

Invalid product destinations and tracking failures can create an immediate revenue loss.

Launching at peak trading time

This increases commercial exposure and reduces the room to diagnose problems calmly.

Removing redirects too early

Old URLs can continue receiving crawler, customer and backlink traffic long after launch.

A phased migration checklist

Phase 1: strategy and baseline

• Define scope and success criteria.
• Name owners and escalation routes.
• Capture 8–12 months of performance.
• Identify priority URL cohorts.
• Document commercial risks.

Phase 2: inventory and mapping

• Crawl the live site.
• Combine sitemap, analytics, Search Console, backlink and campaign URLs.
• Tag every URL by type and value.
• Map each valuable URL to an appropriate outcome.
• Review discontinued-product decisions.

Phase 3: build and staging QA

• Preserve content and product data.
• Validate technical templates.
• Crawl staging.
• Test rendering and mobile experience.
• Test analytics and consent.
• Test paid-media and feed integrations.
• Complete end-to-end purchases.

Phase 4: launch preparation

• Approve redirect map.
• Prepare old and new sitemaps.
• Define launch and rollback criteria.
• Freeze non-essential changes.
• Schedule full team coverage.

Phase 5: launch

• Activate permanent redirects.
• Remove production blocks.
• Crawl old and new URL sets.
• Submit sitemaps.
• Use Change of Address where required.
• Test checkout, tracking and feeds.

Phase 6: recovery and optimisation

• Monitor daily for two weeks.
• Review weekly for three months.
• Fix errors by commercial priority.
• Update important external links.
• Compare recovery by URL cohort.
• Retain redirects for at least one year.

Questions directors should ask before approving launch

1. Do we have a complete inventory of valuable old URLs?
2. Has every revenue-driving page been mapped and tested?
3. Are redirects direct, permanent and relevant?
4. Has staging been crawled at scale?
5. Have we preserved the content and data that supported rankings and conversion?
6. Has checkout been tested across priority devices and payments?
7. Are analytics, consent and advertising conversions working?
8. Have feeds and paid landing pages been updated?
9. What are the launch blockers and rollback conditions?
10. Who monitors technical health and revenue during the first 14 days?
11. What level of volatility is acceptable?
12. How quickly can the team correct a critical issue?

If these questions cannot be answered clearly, the site is not ready to launch.

The migration principle: preserve user intent

The safest migration protects one thing at every stage: the customer’s intent.

A shopper following an old product, category, brand or guide URL should reach the closest useful equivalent on the new site. The information should be the same or better, and the path to purchase should work.

That same principle helps search engines understand the move. Relevant redirects, preserved content, accurate canonicals and strong internal links all reinforce the relationship between the old and new pages.

When user intent, URL signals, commercial content, technical accessibility and conversion tracking are protected before launch, the business gives Google the clearest migration signals and customers fewer reasons to abandon their journey.

Frequently asked questions

Can you migrate an e-commerce website without losing traffic?

You cannot guarantee zero movement. Temporary fluctuations are common while search engines recrawl and process new URLs. A complete redirect map, strong QA and rapid monitoring can substantially reduce the risk and duration of losses.

How long does an e-commerce migration take to recover?

Google states that small-to-medium sites may take a few weeks for most pages to move, while larger sites can take longer. Recovery depends on site size, server performance, redirect quality, indexability and how much changed.

Should every old URL be redirected?

Every valuable old URL needs an intentional outcome, but not every URL deserves a redirect. Where no relevant replacement exists, a genuine 404 or 410 may be more appropriate than an irrelevant destination.

How long should 301 redirects remain after migration?

Google recommends keeping redirects for as long as possible and generally for at least one year. Some commercially valuable redirects should remain indefinitely.

Should an old product URL redirect to the homepage?

Usually not. Redirect to the matching product, genuine successor, useful alternative or relevant category. An irrelevant homepage redirect may confuse users and be treated as a soft 404.

When should the redirect map be created?

Before the new site is completed. Redirect requirements can influence the new URL structure and need time for review, implementation and large-scale testing.

Do you need Search Console’s Change of Address tool?

Use it when moving from one domain or subdomain to another. It is not required for a straightforward HTTP-to-HTTPS migration.

When is the safest time to launch?

Choose a lower-risk trading period with full technical and commercial coverage. Avoid peak sales, major campaigns and important product launches wherever possible.

Protect the commercial value of your migration

An e-commerce migration should improve the business without sacrificing the search visibility, customer journeys and revenue already built.

Clubbish can provide senior SEO and measurement oversight throughout planning, staging, launch and recovery—connecting URL preservation with organic revenue, Paid Search, feeds, analytics and conversion.

Book a strategy call before your migration to identify the pages, signals and commercial journeys that must be protected.