The mechanic that decides every migration's outcome
A migration is the process of telling Google that the content at URL A is now at URL B. The signal is sent via HTTP 301 redirect from every old URL to its new equivalent. When the signal is complete and consistent, Google transfers the ranking equity from URL A to URL B over a recrawl window of weeks to months. When the signal is incomplete — old URLs that 404, redirects that loop, redirects that point at the wrong destination — the ranking equity is lost. The platform-specific details around content import are secondary. The redirect map is the lever.
The traffic curve every migration shows (the honest version)
Days 1 to 21 after cutover show a 10 to 25 percent organic traffic drop as Googlebot starts recrawling every URL and reranking the new site. Days 21 to 60 stabilise at the lower level — sometimes 30 to 50 percent below pre-migration baseline — while Search Console catches up and Google's algorithm reweights the new structure. Days 60 to 180 recover toward and past baseline as the cleaner SEO install compounds. The recovery curve is steeper when the operator ships better schema, faster page speed, and tighter heading hierarchy on the new site than the old.
Per-platform specifics — what each source platform gives and takes
Squarespace's import tools cover Wix, WordPress, Shopify, Big Cartel, Tumblr, and Blogger natively. Showit, Webflow, ghost, and most other platforms are manual rebuilds. Each source platform has a distinct loss profile: Wix loses apps and animations; WordPress loses plugins and Yoast/SEOPress structured data; Shopify loses theme customisations and apps; Showit loses everything that was not text and images. The redirect-mapping work is the same in every case. The content-port work is platform-specific.
The 301 redirect pattern that every migration uses
Every Squarespace migration uses URL Mappings as the redirect mechanism. The pattern is: one row per source URL, one destination URL per row, status code 301, and the entire CSV submitted via Settings > Advanced > URL Mappings. Wildcards work for repetitive patterns (every /wp-content/uploads/* redirects to /static/old-uploads-archive/* for example) but the cleanest migrations explicit-map every important URL row by row. The pattern is mechanical; the discipline is in completeness.
What survives every migration
Domain authority, backlinks to redirected URLs, content that maps cleanly, Search Console history, and the customer relationship to the brand all survive a competent migration. The Google Search Console property has to be re-verified for the new platform, but the historical data and the manual actions history carry over when the change-of-address request is filed correctly. Indexed content with stable URLs survives unconditionally. Backlinks survive when their target URL has a working 301 redirect.
What does not survive without manual work
Structured data (Yoast schema on WordPress, JSON-LD apps on Wix, native rich result blocks on Shopify) does not transfer. Custom 404 pages, custom meta titles and descriptions, alt text on images, Open Graph images, hreflang tags, and any platform-specific SEO settings are re-authored on the new site or they are lost. Internal links pointing at the old URLs become 301 chains until updated; the redirects work but the link equity passes through an extra hop that is slightly weaker than a direct link.
The pre-cutover checklist
Before pointing DNS at Squarespace, verify the new site against the following list. Every page has the correct meta title and meta description. Every image has alt text. Every blog post has a JSON-LD Article block installed via Code Injection. Every page redirects from its legacy URL via URL Mappings. The sitemap is accessible at /sitemap.xml. The robots.txt is configured correctly (AI checkbox state matches the strategy). The Google Search Console verification is ready to be filed for the Squarespace site on cutover day. A custom 404 page is in place to catch unmapped legacy URLs gracefully.