

There's a pattern that is repeated quite often in migrations to Shopify: the technical project runs well, the design looks beautiful, the catalog migrates correctly, the checkout works. And three months later, organic traffic is down 30–40%.
Why? Because managing SEO in a migration is not about adding redirects at the end of the project. It is a discipline that starts before the project, that accompanies every technical decision during the project, and that requires monitoring and adjustment for months after launch.
This article is different from the generic "do 301s and update the sitemap". It specifically discusses the particularities of SEO of Shopify: its limitations, its specific behaviors, and what needs to be done before, during, and after a migration from any platform.
Before we get into the migration process, it's important to understand how Shopify works from an SEO standpoint. There are aspects that are different from most platforms and that, if not known, can cause unexpected problems.
On Shopify, the directory structure for the main sections of the store isn't configurable:
You can't root your products (/product-name), or use a structure like /store/category/product. This restriction affects all Shopify stores regardless of plan.
If you were coming from a platform with a different URL structure, you'll need 301 redirects for all pages that change URLs. There's no way around this.
This is the most important behavior to understand. On Shopify, a product is accessible from multiple URLs:
Both URLs serve the same content. Shopify handles this with automatic canonical tags that always point to /products/product-name, which in theory solves the duplicate content problem for Google.
However, you need to verify that canonicals are being generated correctly in the theme you are using, especially in third-party themes or in highly customized themes. A misconfigured canonical can cause Google to index collection URLs instead of product URLs, or to ignore pages that should be indexed.
How to verify: Use Google Search Console to check which URLs are indexed. You can also use GSC's URL inspection tool to verify the canonical that Google is using for any specific page.
On standard Shopify (any non-Plus plan), the robots.txt file is automatically generated by the platform and isn't fully editable. You can add directives through a robots.txt.liquid template in the Shopify Online Store 2.0, but with limitations.
For most stores, the robots.txt generated by Shopify is correct. But if you came from a platform where you had specific directives, blocking certain bot directories, managing faceted URL parameters, etc., you can replicate the exact same behavior.
Shopify automatically generates a sitemap.xml that includes products, collections, pages, and blog posts. This is convenient, but it has limitations:
For most stores, this isn't a problem. For stores with large catalogs where you want to control exactly what's indexed, it may require additional solutions.
Shopify allows you to edit the meta and meta titles of all products, collections, and pages directly from the admin. However, page titles have a default format that includes the store name as a suffix (ex: "Product Name – Store Name").
You can modify this behavior in the theme code, but it requires access to the theme and knowledge of Liquid.
SEO audit of the current site
Before migrating anything, you need a complete picture of what you have:
URL mapping
Create a spreadsheet with two columns: old URL → new URL in Shopify. This isn't optional; it's the basis for all the redirect work that comes next. For stores with hundreds or thousands of pages, this process can take days, but it's necessary.
Keyword analysis and structure
Take advantage of the migration to review the information architecture. Will Shopify's collection structure represent the current taxonomy well? Are there opportunities to improve the structure that migration allows you to implement?
Configuring the Collection Structure
Collections on Shopify are the equivalent of categories on other platforms. The collection structure directly affects SEO because:
Optimization of migrated metadata
If you migrate the meta titles & descriptions from the previous platform, you don't assume that they are correct in Shopify. They need to be validated because:
Structured Data Configuration (Schema.org)
Modern Shopify themes include basic structured data (Product schema, BreadcrumbList, etc.). But you need to verify that they are correctly implemented for your product type. Product reviews, pricing, stock availability: all of this data appears in search results if the schema is set up correctly.
Blog configuration and content redirection
If you come from a platform with an active blog and indexed content, blog migration requires special attention:
301 Redirect Implementation
Shopify has a native redirect management tool in the admin (/admin/redirects). For a small number of redirects, that's enough. For hundreds or thousands, it uses bulk import via CSV or a specialized app.
Redirect priority:
Checks before activating the new domain:
Tool update:
SEO monitoring in the first 8 weeks
The first weeks after launch are the period of greatest SEO risk. Set up alerts in Google Search Console to detect:
Request re-crawling of the most important pages
Use GSC's URL inspection tool to request indexing of the most important pages. Google will crawl them faster than waiting for organic crawling.
Post-release canonicalization management
Once your store is in production, check with GSC which URLs Google is choosing as canonical. In some cases, Google may be using a different URL than the one you're declaring as canonical. This is valuable information to make adjustments to.
If your collections have a lot of products and are paginated, the pagination URLs (/collections/name?page=2) generate potentially duplicate or unhelpful content to index. Shopify handles this with rel="next" and rel="prev", but in older versions of the theme it may not be configured correctly.
In Shopify, if you enable the tag filter functionality in collections, URLs of type /collections/name/tag-name are generated for each active filter combination. Without proper management, this can generate hundreds of URLs with similar content or thin content.
The standard solution is to add noindex to these tag pages if they don't provide independent SEO value, or work with separate collections if each segmentation has enough search volume to justify its own URL.
Many Shopify themes include outdated or misconfigured structured data. Validate the schema with Google's rich results testing tool and correct it if necessary.
Shopify has functionality that automatically generates redirects when you change a product's slug from the admin. But this only applies to changes made within Shopify, not the initial migration from another platform. Migration redirects need to be created manually.
Before the project:
During the project:
At launch:
Post-launch:
A well-planned migration should result in minimal or no organic traffic drop in the long run. However, it is normal to see fluctuations during the first 4–8 weeks as Google re-crawls and re-indexes the site.
A temporary drop of 10–20% in the weeks immediately following launch is not necessarily a red flag. What does require immediate attention is a sustained drop that continues beyond 8 weeks or exceeds 30%.
The migrations with the greatest negative SEO impact are those that are characterized by: change of domain simultaneous to the change of platform, misconfigured or incomplete redirects, loss of content of category pages that had optimized text, and changes in the internal architecture of links.
SEO in a Shopify migration isn't an afterthought that's solved with a list of redirects. It's a process that starts weeks before the project, requires work throughout development, and needs constant follow-up in the months after launch.
The good news: with the right planning, it's entirely possible to make a migration to Shopify without significant loss of organic traffic, and in some cases (when the source platform had performance issues or poor information architecture) migration can be an opportunity to improve positioning. At La Tu Website , we're experts.
The key is to treat SEO as an integral part of the project, not as a last-minute task.
Shopify has the necessary technical foundations for good positioning: clean URLs, native HTTPS, reasonable load times, support for custom metadata, and structured data. Its limitations (fixed URL structure, robots.txt little configurable on standard plans) are manageable for most stores. It's not the most flexible platform from a technical SEO standpoint, but it's good enough to compete in most industries.
Full re-crawling can take anywhere from a few weeks to 2–3 months depending on the size of the site and how often Google crawled it previously. The most important pages (with a manual indexing request to GSC) are usually re-indexed in days. For a large store's full catalog, it can take months.
In general, no. If you can separate the two changes, the SEO impact of each is more manageable and easier to diagnose if something goes wrong. If the domain change is unavoidable, carefully plan the redirects and the change of direction process in GSC.
Modern Shopify themes include structured data for products (Product schema) and breadcrumbs (BreadcrumbList). However, the quality and completeness of these schemas varies between themes. You always need to validate them with Google's testing tool.
301 redirects transmit most of the link equity to the new URL. They do not transmit 100% (there is a small percentage of loss), but in practice the impact is minimal if the redirects are well configured. The important thing is that the redirects are direct (URL A → URL B) and not chained (URL A → URL B → URL C), which generate more loss of authority.
Both. A well-planned migration can be an opportunity for SEO improvement if the previous platform had performance issues (bad load times, crashing JS), poor information architecture, or misconfigured metadata. It's not uncommon for stores migrating from older Prestashop or WooCommerce installations with speed issues to see ranking improvements in the weeks following the migration.

Hello! drop us a line
SEO management in a migration is not about adding redirects at the end of the project