Migrating to Wix Without Losing Rankings — A 12-Step Playbook
How to migrate from WordPress, Squarespace, or Shopify to Wix Studio without losing organic traffic. URL maps, 301s, schema parity, ranking monitoring.
A platform migration is the most dangerous SEO event short of getting hacked. Half the migrations we audit destroyed 20-50% of organic traffic in the first three months. Done well, the same migrations produce zero net loss. The 12-step playbook below is how we do it.
Step 1 — Snapshot the existing state
Before anything else: full crawl of the current site (Screaming Frog or similar), ranking baseline on top 100 keywords, traffic baseline for top 50 pages, full schema inventory, internal-link graph export. This is your reference. Migration "success" is measured against it.
Step 2 — Decide on URL preservation
Default: every existing URL keeps its path on the new Wix Studio site. Change a URL only if:
- The content has materially changed and a new slug describes it better.
- The existing slug has typos or non-semantic structure (e.g.,
?p=42). - The information architecture is changing.
When a URL changes, document it in the URL map (step 3) — never leave it to chance.
Step 3 — Build a 1:1 URL map
A spreadsheet:
| Old URL | New URL | Redirect type | Reason | |---------|---------|---------------|--------| | /old-path | /new-path | 301 | New IA | | /unchanged | /unchanged | none | Identical |
Every legacy URL appears. The map is signed off before any redirect goes live.
Step 4 — Rebuild schema parity
Inventory the schema on every legacy page. Reimplement equivalent or improved schema on every new page. Validate with Rich Results Test before launch.
We have audited sites whose previous CMS had Article + Person + Organization schema on every blog post. New site had nothing. Rankings dropped 30% in a month.
Step 5 — Preserve content + meta
Titles, meta descriptions, H1s, alt text — copy exactly or improve, never silently drop. We diff every page's meta layer before/after on a spreadsheet.
A "copywriter polish" on top of a migration is a common ranking killer. If you must refresh copy, do it as a separate engagement, not coupled with the migration.
Step 6 — Recreate the internal-link graph
Export every link from the legacy site (Screaming Frog has this). Reproduce the graph on the new site with the same anchor variety. New URLs replace old ones throughout the body content.
This is the most tedious step. It is also where most agencies cut corners. Don't.
Step 7 — Hreflang reciprocity (if multilingual)
If the site is multilingual, every page in every language must list every other language version. Test reciprocity with Screaming Frog's hreflang report.
Step 8 — Test the 301 plan in staging
Before switching DNS, test every old URL on the staging environment. Confirms the 301 plan deploys correctly. Catches typos in the map.
Step 9 — Pre-launch checklist
A 108-item checklist runs on staging:
- All URLs reachable.
- Schema validates on every page.
- Hreflang reciprocity confirmed.
- Sitemap generates correctly.
- Robots.txt allows indexing.
- CWV in the green on real devices.
- All CTAs functional.
- Forms submit correctly.
Tick every item with the client watching.
Step 10 — Switch DNS during low-traffic window
3am client local time is the standard. Submit the new sitemap to Search Console immediately. Validate the 301s are firing.
Step 11 — Watch for 30 days
Daily Search Console checks for:
- New crawl errors (404s, server errors).
- Coverage warnings.
- Manual actions (rare but check).
- Ranking drift on top 100 keywords.
Mid-flight fixes happen here. Most migrations recover any temporary drop within 14-21 days.
Step 12 — Final stabilisation report
30 days post-launch: a written comparison of pre- vs post-migration state. Rankings, traffic, conversion, CWV. If anything dropped, we own it and fix it.
What we never do
- Promise "zero risk" — temporary drift is normal during reindexing. We aim for net zero across the engagement.
- Couple migration with redesign + copy refresh + new strategy — each variable is a risk. Migrate first, polish later.
- Skip the URL map — there is no shortcut.
The bottom line
Migration to Wix Studio is genuinely low-risk if you treat it like a heart transplant — surgically, with discipline. Most migrations fail because the team treated it like a paint job.
Our 200+ migration case base averages +12% organic traffic gain in the six months after migration, because the new build is more disciplined than what it replaced. The migration itself is net-zero if you follow this playbook.