Four weeks after a clean-looking launch, the organic traffic line on the analytics dashboard falls off a cliff and stays there. The store looks better than it ever did. The checkout is smoother, the theme is modern, and yet the pages that used to bring in customers no longer show up where they used to. This is not a fluke or bad luck. It is the predictable result of moving a store to a new platform without treating the URLs and content as assets worth preserving.
Replatforming feels like a design and development project, which is why the search consequences catch people by surprise. The visible work is picking a theme, migrating products, and testing payment flows. The invisible work is making sure that everything a search engine already knew about the old store carries over to the new one. Skip that second layer and the transition quietly undoes years of accumulated ranking history.
The migration nobody budgets SEO time for
Migration timelines are usually built around the developer’s task list. Import the catalog, rebuild the templates, configure shipping, go live. Somewhere in that list there should be a line for URL mapping and redirect testing, but it rarely appears, because it does not produce anything you can see on screen. The store works. It just does not work for the search traffic that used to find it.
The result is that redirect planning gets treated as a post-launch cleanup task, something to circle back to once the urgent bugs are fixed. By then the damage is already in motion.
What happens if you launch before mapping your old URLs?
Every ranking a store holds is attached to a specific URL. When you change platforms, the URL patterns almost always change with them. Old product paths, collection paths, and blog paths get replaced by Shopify’s own structure. If you launch without a map connecting each old address to its new equivalent, every one of those old links now leads to a 404 page.
Search engines have those old URLs in their index. Customers have them bookmarked. Other websites link to them. On launch day, all of that points at nothing. The rankings do not transfer to the new pages automatically, because as far as the crawler is concerned, the old page vanished and a brand-new unrelated page appeared somewhere else.
Traffic in the danger zone
The first sign of trouble is usually not a sudden zero. It is a slide. Pages start dropping in position as the crawler encounters errors, and the traffic that depended on those positions thins out day by day. This decline can run for weeks before it bottoms out, which is what makes it so disorienting. The launch went fine, the store is live, and then the numbers keep sinking with no obvious cause on the front end.
When Google recrawls your new store
Crawlers do not revisit every page the moment you relaunch. They work through a store on their own schedule, and a full recrawl of a large catalog can take weeks. During that window the index is a mix of stale entries pointing at dead URLs and new entries that have not yet earned their standing. Rankings behave erratically because the search engine is working with incomplete and contradictory information about what your store actually is now.
Redirects speed this up by telling the crawler exactly where each page moved. Without them, the engine has to rediscover the whole store from scratch as if it had never seen it.
The content parity trap
Even with redirects in place, rankings can slip if the new pages do not carry the same substance as the old ones. A common casualty of migration is the product description, category copy, and metadata that never gets ported over cleanly. The page redirects correctly, but it now says less than it used to, or says it differently. Search engines ranked the old page partly on that content. Strip it out and the redirect leads to a weaker page that no longer deserves the position it inherited.
Did your redirects actually pass equity, or just avoid 404s?
Not all redirects are equal. A redirect that sends every old URL to the homepage technically eliminates the 404, but it passes almost no value, because the destination has nothing to do with the original page. Proper mapping is one-to-one: each old product to its matching new product, each old collection to its new collection. Verifying that they resolve as permanent redirects, and to the right target, is tedious enough that many stores lean on dedicated Shopify marketing partners to audit the whole map before launch rather than discover the gaps afterward. Getting this wrong is the difference between a brief dip and a genuine loss.
Recovering ground after a rocky switch
If the traffic has already fallen, recovery is possible but slower than prevention would have been. The steps are to pull a full list of the old indexed URLs, identify which ones are now returning errors, and build the redirects that should have existed from the start. Then restore the content that went missing and resubmit the store for crawling. Positions tend to return gradually as the crawler works through the corrected structure, though rebuilding is never as fast as holding ground you never lost.
Planning a migration that protects what you built
The stores that come through a replatform without a traffic collapse are the ones that treated URL mapping as a launch requirement, not an afterthought. They exported the old URLs early, matched every one to a destination, tested the redirects on staging, and confirmed the content moved across intact. The pattern is consistent across every store that survives the switch: the work that protects rankings is boring, invisible, and done before anyone flips the store live rather than a month after the traffic has already gone.
