wix to wordpress: rebuild inventory, redirect map, monitor

web · 2026-10-13 · 6 min

yes — by rebuilding, not migrating. wix states it plainly: sites run on proprietary tech on wix servers; there's no export. WPBeginner documents the RSS/manual path and what it does NOT carry (design, structure, stores, bookings, galleries). hosts selling one-click migration sell hope with affiliate links. the vendor-neutral checklist: inventory, rebuild, redirect map, monitoring.

what transfers vs what doesn't

transfers: blog content via RSS, images (downloaded), text (copied), domain (transfer out — yours, keep it). does NOT: design, page structure, apps (stores, bookings, galleries), settings, SEO history. treat it as a rebuild project with a content head-start, budget half a new site, and you'll be right. treat it as an export and you'll be rebuilding twice.

the redirect map (where rankings survive or die)

list every old URL, map to its new counterpart (or nearest parent — never mass-redirect everything home). implement permanent server-side redirects (google: no PageRank loss on 301s, but expect weeks of fluctuation while recrawling). keep URL slugs identical where possible (less mapping, less risk). change ONE major thing at a time (google's explicit advice — CMS move plus redesign plus domain change in one deploy is how traffic disappears). monitor BOTH sites in console post-launch. google's move docs are the primary source — read them before touching anything.

deciding: move or stay?

move when: growth hits platform ceilings (ecommerce depth, integrations, ownership needs), total costs exceed owned alternatives (wix real costs), or the business outgrows rented simplicity. stay when: the site works, leads flow, and migration pain exceeds gains — migration for ideology alone is vandalism with a roadmap. compare honestly first: wix vs wordpress.

FAQ

will I lose google rankings?

temporarily, usually (fluctuation during recrawl is normal); permanently, only if redirects, content, or speed regress. identical content + mapped URLs + fast new site = recovery in weeks.

change of address tool in console?

only for domain/subdomain moves — NOT for CMS changes with same URLs. using it wrongly creates the problem it was built to solve.