Store migration SEO: how to move between Salla, Zid and Shopify without losing your Google traffic

To move a store without losing Google traffic, keep the same domain, list every URL that earns visits, map each to its closest page on the new platform, and launch 301 redirects with the new store on the same day. Then test them, submit the new sitemap and watch Search Console for weeks. Move outside peak seasons.

This guide is for owners and e-commerce managers of online stores in Saudi Arabia and the Gulf who are moving between Salla, Zid, Shopify, WooCommerce or a custom platform. It covers what breaks in a move, how to build the URL map, what each platform gives you for redirects, how to keep Arabic and English versions together, and how to choose the week.

Searchers phrase it in two ways. In Google’s autocomplete for Saudi Arabia on 19 October 2026, “website migration seo” is followed by “does changing your website affect seo”, and in Arabic the question arrives as a direction: «نقل المتجر من سلة الى زد».

Free 5-point SEO audit for your store. Send us your store’s address. Within 48 hours a senior specialist sends you 5 prioritized fixes with the evidence, the competitor that ranks above you for your best category, and why. Get your free SEO audit.

What actually goes wrong when a store changes platform

A new platform almost always means new URL shapes. Shopify’s own migration guide for WooCommerce stores says its link structure for individual pages is likely different from the previous service, so old links to specific pages likely will not load, and gives the example of a shipping policy moving from /policies/shipping-policy to /pages/shipping-policy. Every product, category and blog URL is in the same position. Traffic is lost in a small number of repeatable ways:

What goes wrong	What it looks like	The fix
Old URLs have no redirect	Pages that earned visits and links return an error page	A 301 for every URL that earns traffic, links or orders
Everything is redirected to the home page	Hundreds of old URLs land on one page. Google says this can be treated as a soft 404	Redirect each URL to its closest equivalent
Redirect chains	Old URL, then an interim URL, then the final one	Redirect straight to the final address. Google follows up to 10 hops but advises keeping chains ideally to no more than 3 and fewer than 5
Temporary redirects	A 302 or 307 tells Google to keep showing the old page	Use 301 or 308, which are the signal that the new URL should be the canonical one
Test settings left on	noindex, a robots.txt block or a store password survives launch. A Shopify store in private mode also hides its sitemap from search engines	List every setting that is on during development and switch it off at launch
Text and titles rewritten during the move	The page that ranked is no longer the same page	Move the content as it is first and improve it later. Google’s advice is to change only one thing at a time
Canonical and hreflang still point to the old URLs	The signals contradict the redirects	Every new URL needs a self-referencing canonical, and hreflang must use the new URLs

Sources: Google Search Central, “Site Moves and Migrations” (last updated 20 August 2026) and “Redirects and Google Search” (last updated 14 April 2026); Shopify Help Center, “Migrate from WooCommerce”. All read on 19 October 2026.

The good news is in the same Google page: 301 and other permanent redirects do not cause a loss in PageRank. A move is not what hurts a store. An unplanned move is. If you keep the platform and only change the design, our guide to redesigning a website without losing SEO covers that case.

Step 1: build the old-to-new URL map

The map is a two-column sheet: every old URL, and the page on the new store that replaces it. Build it before anything is imported, from several sources, because no single one is complete:

• The old sitemap and the CMS list. They show what the store thinks it has.
• Search Console and analytics. They show what Google and shoppers actually use. Google suggests starting with the URLs that get the most traffic, and with pages that have internal and external links in the Search Console links report.
• Server logs, where you can get them. URLs visited at least once recently.
• Images, files and scripts. Google says to include the URLs of embedded content such as images, videos, JavaScript and CSS in the move plan. Product images that earn traffic from image search are easy to forget.

Then decide the destination of each row with simple rules:

1. Product to the same product on the new store. If the product is discontinued, send it to its closest replacement or its category, not to the home page.
2. Category to category, even if the category was renamed or merged.
3. Blog posts, brand pages and policy pages to their equivalents. Keep the posts that bring visits; do not drop them to save time.
4. Pages you are deleting on purpose should return 404 or 410. Google says that is the right response for deleted or merged content, so redirect only when a real equivalent exists.
5. Where the platform lets you, keep the URL exactly as it was. The best redirect is the one you do not need.

Check the finished map for chains (a redirect that leads to another redirected URL) and for loops before it is loaded. Our technical SEO work starts with this sheet, because every later step depends on it.

Step 2: what each platform gives you for redirects

The platforms differ here more than anywhere else, and it should be part of the decision to move. This is what each help center says, read on 19 October 2026:

Platform	Redirect tool	Limits and rules to know
Shopify	URL redirects in the admin, with CSV import and export	Redirects work only from URLs that are broken (404). Maximum 100,000 redirects, and 20,000,000 on Plus. Products and collections live under the fixed /products and /collections paths. A redirect applies to the same path in every language or market subfolder
Zid	Link redirection under Settings, with Excel import and export (help page updated 3 August 2026)	Works only on broken (404) URLs, never on a page that exists. Every redirect is a 301 permanent redirect
Salla	We did not find a redirect manager in the help articles we opened (SEO, domain, custom links, product import)	Custom links are described as short links for SMS and social sharing. Ask Salla support in writing how old URLs are redirected before you commit to a move to Salla

Two details matter in practice. First, Shopify and Zid redirect only URLs that currently return an error, so a leftover page with the same URL on the new store would block the redirect; check before you load the file. Second, if you are leaving Salla, the old paths will be requested from the new platform once your domain points there, so the redirects are created in Zid or Shopify, not in Salla. Choosing between two platforms on search grounds before you move? See Salla or Zid for SEO.

Moving between platforms: direction by direction

Each platform documents its own side of the move. The product data usually has a path; the SEO work does not move by itself.

Direction	What the platform’s own guide gives you	What you must still do
Salla to Zid	Zid’s guide (updated 5 August 2026): export products and customers from Salla as CSV and import them into Zid	Load the redirect file in Zid. Zid’s guide answers the SEO question with the 404 redirect feature. Update DNS to Zid, and if the domain is owned by Salla, have its ownership transferred to you
Zid to Salla	Salla’s import article (31 August 2026): products come in from Zid through an Excel file	Get written confirmation of how Salla will redirect old URLs
Shopify to Salla	Salla’s import article: products come in from Shopify through an API connection	The same written confirmation on redirects
Salla or Zid to Shopify	Shopify’s migration checklist (it lists creating URL redirects) and its CSV imports. Shopify’s redirect tool accepts a CSV	Map to Shopify’s /products/ and /collections/ paths and load the redirects. Shopify generates the sitemap.xml automatically
WooCommerce to Shopify	Shopify’s WooCommerce guide, with a field map and CSV import	The URL map and the redirect CSV, the same as above

One item decides more migrations than any other, and it has nothing to do with Google: the domain. If the domain was registered through your current platform, confirm who owns it before you cancel anything. Salla’s help center says an external domain connects by Name Server (primary domain only) or by CNAME, with the connection typically taking about 24 hours, and Shopify says DNS propagation after a domain transfer can take up to 48 hours. Plan the cutover for the slowest of these, not the fastest.

Arabic and English: move both versions together

Most Gulf stores run two languages, and a migration is where one of them quietly disappears. Treat the Arabic and English sites as one project:

• Map the Arabic URLs to Arabic pages. An Arabic product page redirected to its English twin, or to the home page, is the most common bilingual error we see.
• Update hreflang to the new URLs. Google lists this explicitly as part of a site move, along with a self-referencing canonical on every new URL.
• Know how your new platform redirects across languages. Shopify says one redirect applies to the same path in every language or market subfolder, and that you can still add separate redirects when a market needs a different destination. For the Arabic and Markets side of a move to Shopify, see our Shopify SEO guide for Saudi stores.
• Decide the Arabic address style once. Whether product and category addresses stay in Arabic letters or move to Latin letters, change it only if you must, and only before the map is built. Changing it halfway breaks the sheet.
• Check that titles, descriptions and headings survived the import. Product exports often truncate or drop Arabic fields.

Language versions are where we have seen some of the largest swings: for a travel agency serving the French market, organic clicks grew 991% in 3 months after we fixed how its language versions were set up. A single-store business should expect a different scale, but the mechanism is the same.

Launch day: the checklist

1. Everything from the map is loaded and tested on a sample of at least the top 50 URLs by traffic before DNS changes.
2. Test settings are off. No noindex, no store password, no private mode, a robots.txt that matches the live site.
3. Canonical tags and hreflang use the new URLs, and internal links point straight to the final addresses, not through redirects.
4. The new sitemap is submitted in Search Console. Google’s guide also suggests submitting the sitemap of the old URLs while the move runs, so you can watch them drop out as the new ones are indexed.
5. Redirect checks use a real tool. Request the old URLs with a command-line tool or script and confirm one hop, status 301, and a 200 on the destination. Google also lists the URL Inspection tool for single URLs.
6. Search Console and analytics still work on the new store. Google warns that verification files and tags must be carried across, or ownership checks fail after the move.
7. The server can take the load. Google crawls a moved site more heavily for a while, because its crawls of old URLs are redirected too.
8. Tracking fires on the new checkout: purchase, add to cart and lead events. A migration that loses its analytics loses the evidence that it worked.
9. Pause checkout on the old store during the DNS window if it can still answer some visitors, so no order lands on the wrong platform. This is our own practice, not a platform requirement.
10. Save the old URL list and the redirect file with the launch date. You will need them in month 3.

If you also use Search Console to monitor the move, our Salla and Search Console setup guide shows how to verify a store property correctly.

When to move: not in the weeks before a peak

Google’s site move guide says to time the move for a lower-traffic period if you can, and that for a medium-sized site it can take a few weeks or more before the new URLs replace the old ones. In Saudi Arabia that points to a simple rule: do not let the settling period overlap a sales peak.

This year makes it concrete. White Friday 2026 falls on 27 November, 39 days after 19 October (Khaleej SEO calculation). Our rule of thumb is to be live and verified at least four weeks before a peak. For White Friday that means about 3 November, which leaves roughly two weeks from today to build, map and test a whole store. If that is not already planned, the safer choice is to wait until the sale has passed and the redirects can be tested calmly. Our White Friday plan for stores covers what should be live instead.

We also looked at when online card spending is thin. Using SAMA’s monthly mada e-commerce series, and dividing each month by a 12-month centred moving average to remove growth, we get this:

Month	Mada e-commerce sales as a share of trend, each year 2021 to 2025
January	94% to 99%, below trend in all five years
February	85% to 95%, below trend in all five years
March	102% to 117%, above trend in all five years, the month before or at the start of Ramadan in each of those years

Source: Khaleej SEO calculation from the Saudi Central Bank (SAMA) monthly series “Points of Sale Transactions and E-Commerce Transactions (Mada Cards)” as republished by the KAPSARC Data Portal (dataset last modified 15 September 2026). It covers mada debit cards only, not every online payment, and months are not adjusted for length. Details in our payments statistics.

Read it as a hint, not a rule. Ramadan moves about eleven days earlier each year, so the quiet months move with it. The better test is your own weekly orders: pick the quietest recurring window in your analytics, make sure the redirects can be live and verified at least a few weeks before the next peak, and leave a buffer for fixes.

After launch: what to check and when

When	What to check
Day 1	The top 50 old URLs by traffic redirect in one hop to the right page. Search Console shows no spike of server errors. The sitemap is read
Week 1	Pages crawled and indexed on the new store, orders and revenue against the previous week, and the Pages report in Search Console for new errors
Weeks 2 to 4	Organic landing pages compared with the same pages before launch. Old URLs still getting clicks that were not mapped. Any 404 that has traffic or links gets a redirect
Week 8	The review: organic clicks and revenue against the pre-move baseline, by Arabic and English pages
Month 12	Google says to keep redirects as long as possible, generally at least one year. Do not remove them to tidy the file

If pages from the new store are missing from Google after the first weeks, start with our checklist for a store that is not showing on Google.

What a managed migration includes

A platform move is a technical SEO project with a deadline. When we run one, the scope is:

• A crawl of the current store and a prioritised URL map built from the sitemap, Search Console, analytics and backlinks.
• The redirect file in the format your platform needs (a CSV for Shopify, an Excel file for Zid) and a plan for Salla based on written answers from the platform.
• A review of the new store before launch: titles, headings, canonical tags, hreflang, structured data, robots rules and the Arabic fields after import.
• Launch-day verification against the map and a 30-day monitoring plan with the checks above.
• Fixes for whatever the monitoring finds, with the Arabic and English versions handled together.

It sits inside our e-commerce SEO work, and our Salla SEO service covers stores that stay on Salla. No one can promise that every ranking holds through a move, and Google itself says visibility can fluctuate while it recrawls. What a good plan does is remove every avoidable cause of loss, and tell you within days, not months, if something slipped.

See where your store stands before you change anything. Our free 5-point audit shows the fixes that matter most for your store, the competitor that ranks above you and why, and what we would fix first. No obligation, delivered within 48 hours. Request your free SEO audit.