PublishedVerifiedEvery 6 weeksSources4 namedAuthored bySquareRank Team
Migrations · § 2.11.4 · How-to
Shopify to Squarespace SEO migration — products via CSV, schema rebuild, the URL map
Squarespace's Shopify importer1 accepts a Shopify product CSV export and creates Squarespace products from it. Product titles, descriptions, prices, images, variants, and tags transfer. Pages, blog posts, customer accounts, Shopify Apps, custom themes, and any non-product content do not transfer. A typical Shopify-to-Squarespace migration loses 30 to 50 percent of organic traffic in the first 60 to 90 days; commerce sites are higher-stakes than content sites because revenue depends on product page rankings during the recovery window. Plan accordingly: do not migrate in the run-up to Black Friday or any other high-revenue season.
This leaf is the Shopify-to-Squarespace playbook. It covers the CSV import, the URL pattern differences, the Product schema rebuild via Code Injection, the Shopify App loss list, and the cutover sequence for commerce specifically. The migrations hub covers the cross-platform context; the Ecommerce SEO cluster covers the post-migration commerce SEO work.
§01The importer
What Squarespace's Shopify importer ports
The importer reads Shopify's product CSV export — the file Shopify's admin Products > Export feature produces — and creates Squarespace products in Commerce. Product titles, descriptions (HTML formatting preserved), prices, weights, SKUs, tags, vendor names, product types, variant options, variant prices, and product images all transfer. Customer accounts, order history, abandoned carts, discount codes, gift cards, and Shopify Apps do not transfer. Customer data has to be exported separately from Shopify's customer panel and is imported into Squarespace's customer accounts manually.
Squarespace's documentation1 describes the importer scope: "The Shopify import tool transfers your products, including images, descriptions, prices, and variants." Pages, blog content, navigation, and theme customisations are explicitly out of scope and require a manual rebuild. The blog half, where it exists, follows the WordPress XML pattern via Shopify's blog export (if Shopify's native blog is used) or a manual rebuild (if a third-party blog app is used).
The Shopify migration profile
CSV
format for the product import. Shopify CSV export plus Squarespace import is the supported path.
Shopify uses a distinctive set of URL patterns: /products/product-handle for products, /collections/collection-handle for category pages, /collections/collection-handle/products/product-handle for category-scoped product URLs (the canonical product URL when collection context matters), /pages/about for content pages, and /blogs/news/post-handle for blog posts. Squarespace's commerce URL pattern is /shop/product-slug, /shop for the category-equivalent, and /blog/post-slug/ for blog posts. Every Shopify URL needs a redirect; the wildcard pattern compresses the product bulk.
The most complex Shopify-specific redirect: products served from collection paths. A Shopify product accessible at /products/red-blanket and at /collections/throws/products/red-blanket needs both URLs redirected to the same Squarespace destination. The collection-scoped URL is the canonical URL Shopify usually points at, but backlinks may use either pattern. Map both.
§03The redirect map
The Shopify-to-Squarespace 301 redirect map (sample)
The redirect map for Shopify is voluminous because every product, every collection, and every page needs a row. The wildcard pattern compresses the product portion to a single line. Below is the working pattern; CSV import via URL Mappings handles the bulk submission.
URL MappingsShopify-to-Squarespace redirect map
# Products — /products/[handle] to /shop/[handle]//products/[handle]->/shop/[handle]/301# Collection-scoped product URLs — same destination/collections/[anything]/products/[handle]->/shop/[handle]/301# Collection pages — point at Squarespace category pages or shop hub/collections/throws->/shop/category/throws/301/collections/pillows->/shop/category/pillows/301/collections/all->/shop/301# Static pages — /pages/[slug] to /[slug]//pages/about->/about/301/pages/contact->/contact/301/pages/shipping->/shipping/301# Blog posts — /blogs/[blog-handle]/[post-handle]/blogs/news/[handle]->/blog/[handle]/301# Account URLs — point at Squarespace account login/account->/account/301/account/login->/account/login/301# Cart and checkout — point at Squarespace equivalents/cart->/cart/301
The wildcard [handle] captures Shopify's product handle (slug) and substitutes it into the Squarespace destination URL. The handle is preserved by the CSV importer, so the wildcard produces correct destination URLs without per-product rows. The URL Mappings syntax leaf covers the wildcard pattern in detail.
§04Product schema
Product schema and rich results after the migration
Shopify sites typically emit Product structured data automatically via the active theme. After migration to Squarespace, the automatic emission is replaced with Squarespace Commerce's built-in Product schema (Commerce Basic+) — but the Squarespace block is partial and frequently needs Code Injection to add the brand, sku, aggregateRating, and review properties that Shopify's better themes were emitting. Plan to install Product schema via Code Injection on the top 20 product URLs first.
Google's Product schema documentation3 lists the required properties: name, image, description, sku, brand, and offers (with price and availability). The Squarespace Commerce default emission covers name, image, description, and offers; sku and brand often need to be added via Code Injection. The Pillar 3 Product schema leaf covers the per-product block.
§05Apps and themes
Shopify Apps and theme features that do not survive
The Shopify App marketplace is the deepest in commerce; most stores run 5 to 20 apps providing functionality from email marketing to upsell widgets to fulfilment integrations. None of those apps transfer. Replacement options on Squarespace: Klaviyo and Mailchimp integrate directly with Squarespace Commerce via official integrations; upsell widgets are typically replaced with manual Related Products configurations; fulfilment integrations (ShipStation, ShipBob) require reconfiguration on the Squarespace side; review apps need replacement embeds; abandoned-cart recovery emails are handled through Squarespace Commerce or a connected email service.
The replacement work is per-app, time-consuming, and uncovers Shopify-specific dependencies the operator did not realise they had until they are gone. Plan for 10 to 30 hours of app-replacement work on top of the product import and the URL mapping. For high-revenue stores, the migration timeline should include a soft-launch period (the new Squarespace site live on a subdomain or test URL) where the operator validates every commerce flow before DNS cutover.
§06The cutover
The cutover sequence for commerce specifically
Commerce cutovers are higher-stakes than content cutovers because every minute of broken checkout is lost revenue. The recommended sequence: build the staging Squarespace store fully (products, pages, theme, schema, redirects); run a full end-to-end purchase test on the staging URL using a real card with the merchant account that will live on production; cutover DNS during a low-traffic window (typically Saturday morning); monitor purchase completion rates for the first 48 hours; have a rollback plan documented in case checkout breaks.
The single most common cutover bug: payment processor switching. Shopify Payments does not transfer to Squarespace; the new store needs Stripe or Square configured on the Commerce side. Run a real-card test transaction on the staging store before cutover. Test refund flow too — Squarespace's refund interface is different enough from Shopify's that operators occasionally botch the first post-cutover refund. The Ecommerce SEO cluster covers the broader commerce-on-Squarespace setup.
