How to Migrate Off Wix or Squarespace Without Losing Google Rankings (2026)
TL;DR — migration phase by phase:
| Phase | What to do | Why it matters |
|---|---|---|
| Pre-migration | Crawl every URL; export GSC performance data | Redirect map needs to be complete, not approximate |
| URL mapping | Map every old path → new path before launch | Missed URLs become permanent ranking losses |
| Redirects | Server-side 301s for every URL, no chains | 301 passes full PageRank; 302 or no redirect does not |
| Go-live | Submit new sitemap; request indexing for top pages | Speeds up recrawl; reduces ranking gap window |
| Post-launch | Daily GSC monitoring for 14 days | Catches broken redirects before they compound |
| Recovery window | Expect 2–4 weeks of volatility | Normal with proper redirects; not a sign something is wrong |
A platform migration done correctly is one of the lower-risk SEO events. Done without proper preparation, it is one of the most damaging.
Before You Touch Anything: Build a Baseline
The single most common cause of permanent ranking loss in platform migrations is a missing redirect — a URL that existed, had backlinks or ranking history, and quietly became a 404 on the new site because no one remembered it existed.
The fix is a full pre-migration crawl.
Use a site crawler (Screaming Frog’s free tier covers up to 500 URLs; Sitebulb has a 14-day trial) to export every URL on your current domain with its status code. Run the crawl from the domain root, not just the URLs you know about. Platform site builders accumulate orphan pages — old service pages, deleted blog posts that are still indexed, tag archive pages — that do not appear in navigation but do appear in Google’s index.
At the same time, export your Google Search Console Performance data:
- GSC → Performance → Web
- Set the date range to the last 3 months
- Click the Pages tab
- Export the full table
This export shows you which pages Google is actually serving to searchers. Pages with non-zero impressions are your high-priority redirect targets — these are the URLs where a missing 301 directly costs you search traffic.
Cross-reference your crawl export against the GSC export. If a URL appears in GSC with impressions but is missing from your crawl, it is likely an orphan page with no internal links — easy to miss, potentially expensive to lose.
How Wix and Squarespace Structure URLs (and Why It Creates Redirect Traps)
Both Wix and Squarespace use URL structures that differ from the conventions most CMS platforms use. If you are migrating to WordPress, or to any other platform, these differences create redirect traps that cause ranking loss even when the content is fully replicated.
| Page type | Wix path | Squarespace path | WordPress default |
|---|---|---|---|
| Blog post | /post/article-slug | /blog/article-slug (under the blog collection) | /blog/article-slug or /article-slug |
| Blog index | /blog | /blog (collection name) | /blog |
| Product page | /product-page/name or /product/1234 | /shop/p/product-name | /product/product-name |
| Standard page | /about (or numeric in older sites) | /about (auto-slugged from page title) | /about |
The single most expensive trap is the Wix blog path: posts live at /post/, not /blog/. The detail below is what catches people.
Wix:
- Blog index lives at
/blog - Individual blog posts live at
/post/article-slug— not/blog/article-slug - This is the most common Wix migration mistake: WordPress defaults to
/blog/article-slug, so developers redirect the homepage and the blog index but forget/post/*entirely. Every Wix post URL becomes a 404 on the new site. - Some Wix dynamic pages use numeric IDs (
/product/1234) rather than keyword slugs.
Squarespace:
- Product URLs include
/p/before the slug (/shop/p/product-name) - Page slugs are auto-generated from page titles when you create them — “About Me” becomes
/about-me, but customized slugs may not match what a standard CMS would generate - Collection pages (blog, portfolio) use the collection name as the base path
Build your URL mapping spreadsheet before you start configuring the new platform. One column: old URL. One column: new URL. No row left blank. This document is the source of truth for your redirect implementation.
301 Redirects: What Actually Passes Rankings in 2026
Google’s documentation confirms that properly implemented 301 redirects pass the full PageRank (link equity) from the old URL to the new one. The older SEO myth about 301 redirects causing a 15% PageRank “tax” was based on older infrastructure; Google dropped that penalty years ago.
However, “properly implemented” is doing heavy lifting in that statement. Four things make a 301 fail to transfer signals:
1. Wrong redirect type. A 302 (temporary) redirect tells Google not to consolidate signals to the destination — keep both URLs as separate entities. For a permanent migration, use 301 or 308 everywhere, not 302.
2. Chains. If your old platform already had redirects in place (for example, Squarespace had redirected /old-page → /new-page and now your new site needs to redirect /new-page → /final-page), the chain is old-URL → old-redirect → new-URL. Collapse every chain to a single hop: old-URL → final-destination. Chains slow crawl processing and reduce signal transfer efficiency.
3. JavaScript or meta refresh redirects. These are not treated as 301s. Googlebot handles JavaScript, but 301s implemented via JavaScript are processed on a different, slower crawl cycle and do not reliably consolidate rankings. Use server-side redirects.
4. Keeping redirects active long enough. Google recommends keeping redirects in place for at least 180 days; one year is more conservative and appropriate for a permanent migration. Removing redirects too early causes re-fractured link equity.
What to Expect: The Ranking Volatility Window
With correct redirects, a temporary traffic dip of 10–20% for 2–4 weeks is normal and expected after a platform migration. This happens because:
- Googlebot needs to recrawl the new URLs and reprocess the redirects
- Index consolidation takes time — the old URLs do not immediately drop out of the index while the new ones rank
- Behavioral signals (click-through rate, engagement) reset briefly as the new URLs accumulate their own history
Full recovery typically lands in the 4–8 week window for most sites. If your traffic recovers to within 5–10% of your pre-migration baseline by week 8 and trends upward from there, the migration was successful.
Two situations extend that window:
YMYL content (health, legal, finance): Google applies higher scrutiny to E-E-A-T signals when reestablishing trust in a new technical configuration. Expect 3–6 months for full recovery if your site covers medical advice, financial guidance, or legal information.
Simultaneous redesign + content rewrite: If you changed URLs, rewrote content, and redesigned navigation all at once, there is no clean way to diagnose what caused any ranking change. If you see a larger or more persistent drop than expected, see our guide on why Google rankings drop and how to diagnose them.
Post-Migration: What to Watch in Google Search Console
On go-live day:
- Submit your new XML sitemap at GSC → Sitemaps
- Use the URL Inspection Tool to request indexing for your 5–10 most valuable pages directly
- If your domain also changed (not just the platform), use GSC → Settings → Change of Address to notify Google — this is only for domain changes, not platform-only migrations on the same domain
For the first 14 days, check GSC daily. Look for:
- Coverage errors: Pages moving from “Indexed” to “Not indexed” or “Soft 404” indicate a redirect problem on that specific URL. Check whether the redirect is implemented, is a 301 (not 302), and resolves to the correct destination.
- Impression collapse on specific pages: If a page had 500 impressions/week before migration and drops to zero post-launch, find that URL in your redirect map and verify it. Zero impressions means Google stopped evaluating it for queries entirely.
- Impression drop across all pages: A broad drop suggests a crawl issue — check robots.txt, verify the new domain is not inadvertently blocking Googlebot, confirm the sitemap is submitted and valid.
After the first two weeks, shift to weekly monitoring. For a structured weekly review approach, see the GSC weekly checklist for small business owners.
If specific pages remain at zero impressions for more than 4–6 weeks after migration, review the guidance on indexed pages that aren’t ranking — the cause may be deeper than the migration.
The Mistakes That Cause Permanent (Not Temporary) Ranking Loss
Temporary volatility is expected and acceptable. These mistakes cause ranking loss that does not recover:
Incomplete URL mapping. Any URL in Google’s index that becomes a 404 loses its accumulated link equity immediately. If that URL had backlinks, those links now point to a dead page. Even after you fix the redirect later, the recovery is not guaranteed — Google may have already devalued those external links.
Migrating and redesigning simultaneously. Changing URL structure, rewriting headings, replacing content, and shifting navigation all at once makes it impossible to identify what caused a ranking change. If you must redesign, do it in a separate phase after migration rankings have stabilized.
Broken internal links. When you switch platforms, the link format often changes. If a Squarespace page had an internal link to /about-me and the new site uses /about, any page that linked internally to the old path now has a broken link. Run a broken-link crawl on the new site before going live.
Lost metadata. Title tags, meta descriptions, and schema markup may not transfer automatically from Wix or Squarespace. Verify that the new platform is serving the correct title tag and meta description for every page. A blank or duplicate title tag is a meaningful ranking signal regression.
Removing redirects too soon. After 6 months, it’s tempting to remove redirect rules to clean up the config. Do not. Keep every redirect active for at least one year. External backlinks from other websites continue to point to old URLs indefinitely — removing redirects turns those links into 404s permanently.
For a deeper look at the technical side of keeping a site healthy post-migration, see our technical SEO guide for small businesses.
FAQ
How long do rankings take to recover after a platform migration? With proper 301 redirects and no structural content changes, most sites see a 10–20% traffic dip for 2–4 weeks. Full recovery typically lands in 4–8 weeks. YMYL sites (health, finance, legal) often take 3–6 months. Improvements made immediately after migration may not fully register until Google’s next major core update.
Do I need the GSC Change of Address tool? Only if your domain name is also changing — for example, moving from example.wixsite.com to example.com, or rebranding to a new domain during the same migration. If the domain stays the same and you are only switching platforms, the Change of Address tool does not apply. Use correct 301 redirects and sitemap submission instead.
Why do Wix URLs specifically cause redirect problems?
Wix blog posts live at /post/article-slug, not /blog/article-slug. Developers migrating to WordPress often set up /blog/* redirects but forget to redirect /post/*. Every Wix blog post then becomes a 404 on the new site, and those posts lose their accumulated ranking history. A full pre-migration crawl is the only way to catch this before it causes permanent damage.
What if I use 302 redirects instead of 301? A 302 tells Google the move is temporary — do not consolidate ranking signals from the old URL to the new one. For a permanent platform migration, use 301 everywhere. There is no SEO benefit to using 302 for a move you intend to keep, and it introduces meaningful delay in signal consolidation.
Should I migrate platforms and redesign at the same time? Avoid combining them. Migrate first: replicate the same URL structure, content, and navigation on the new platform. Confirm rankings are stable over 4–6 weeks, then redesign. Isolating the migration lets you catch redirect errors before redesign changes contaminate the diagnosis.