Rankings are rarely lost to the migration itself — they are lost to redirects treated as an afterthought. What to map before cutover, and why bilingual stores need twice the care.
The fear is reasonable. You have spent years earning rankings, and a replatform can undo them in a weekend. But rankings are rarely lost to the migration itself. They are lost to redirects treated as an afterthought.
Every URL that Google has indexed needs a mapped destination on the new store, decided before cutover rather than discovered afterwards. That means crawling the live site properly — not exporting a product list, but crawling — because the indexed set always includes pages nobody remembers: old category filters, paginated archives, campaign landing pages still earning backlinks.
Bilingual stores double this. An Arabic URL tree ranks separately from the English one, and it needs mapping with the same care. This is the single most common thing we see skipped in Gulf migrations.
Products, variants, collections and customers are the easy part. Order history is the piece most migrations quietly drop, because it is fiddly and nobody asks about it until the first return request arrives and support has no record of the purchase.
Done properly, a migration is a scheduled switch with a rollback. Done in a hurry, it is a bet.
Tell us what your store needs and where it's stuck. You'll get a clear, fixed-price plan within 48 hours.
Let's Talk