Yes, you can move a website from Wix to WordPress without losing SEO. The catch is that Wix has no full-site export button. You rebuild the site on WordPress, keep or map every URL Google has indexed, put permanent 301 redirects on the WordPress side, and check Google Search Console daily for the first few weeks after launch. When traffic drops after a Wix to WordPress move, the most common cause is missed URLs. WordPress itself is rarely the problem.
I've done this with another closed builder. In 2025 I moved the Aura Clips agency site from Framer to WordPress and rebuilt it on Bricks Builder, with service templates, a blog, GA4 and Google Tag Manager. Wix and Framer share the same problem: your design and content sit inside an editor you can't take with you. So the process barely changes. Here's how I'd run it for a Wix site.
Can you export a Wix site to WordPress?
Only partly. Blog posts can come across through the blog's RSS feed and Wix Stores products through a CSV export. Pages, layouts and forms have to be rebuilt in WordPress.
Wix doesn't have a blog export feature, and Superblog points out that Wix's own help centre lists it as a feature request. The workaround is the RSS feed. Namecheap explains that you find it by adding /blog-feed.xml to your domain, and WPBeginner walks through importing it with WordPress's RSS importer. Everything else gets rebuilt.
| Wix content | How it moves to WordPress | What to watch |
|---|---|---|
| Blog posts | RSS feed, then the WordPress RSS importer | Check the post count matches. Images can still be loading from Wix's servers, and categories and tags often don't come across |
| Pages | Rebuilt in WordPress (Bricks, Elementor or a custom theme), copy pasted in | Keep headings and body copy the same at launch |
| Images | Downloaded, compressed, re-uploaded | Alt text, sensible file names, sizes |
| Wix Stores products | CSV export, then WooCommerce import | Check variants, prices and images by hand |
| Forms | Rebuilt | Notification emails, CRM or Google Sheets connections |
| SEO titles and descriptions | Copied page by page into Rank Math or Yoast | Don't let them fall back to the defaults |
| Domain and email | DNS change or domain transfer | Keep your MX records exactly as they are |
People underestimate that email row. If your Google Workspace or Microsoft 365 mail runs on a domain managed in Wix, the DNS change has to copy every MX, SPF and DKIM record. Get one wrong and mail stops arriving. I cover how to do it safely in moving a WordPress site to a new host without downtime, and it's part of my hosting migration and DNS service.
How much does a Wix to WordPress migration cost?
Published market prices for a professional Wix to WordPress migration run from about $500 to $5,000. What you pay for is the rebuild: templates, blog size, store products and integrations.
FatLab puts professional Wix to WordPress migrations at $1,000 to $5,000 and says the price comes from the labour of rebuilding, not the size of the site. At the low end, Boon Digital Solutions lists its Wix migrations from $500.
| Option | What you get | Main risk |
|---|---|---|
| DIY with RSS import and a theme | Blog posts moved, pages rebuilt by you | Missed URLs and redirects, and it takes far longer than planned |
| Automated migration tool | Content copied across | Layouts still need rebuilding, and you still have to map the URLs |
| Freelance developer | Rebuild, redirects, launch and Search Console checks | Quality depends on their migration process |
| Agency | The same, plus design and project management | Higher cost and more layers between you and the person doing the work |
What moves the price:
- Number of unique templates. Five page layouts cost far less than fifteen.
- Blog size. Fifty posts import in minutes. Fixing their images and internal links takes hours.
- Store. Products, variants, shipping rules and payments add real scope.
- Integrations. Bookings, member areas, CRMs and forms each have to be rebuilt.
- Design. Copying the current look is cheaper than a redesign. Doing a redesign in the same project also makes any SEO change harder to diagnose.
How do you map Wix URLs before the move?
Before you build anything in WordPress, list every Wix URL Google knows about in one spreadsheet, with an old URL column and a new URL column. This map is what protects your rankings. Skip it and you're guessing.
Pull the list from five places:
- Export the indexed pages from the Search Console Pages report.
- Export pages with clicks from the Performance report, using the longest date range you have.
- Download your Wix sitemap from /sitemap.xml.
- Crawl the live site with a tool like Screaming Frog.
- Check the Links report for pages other sites link to.
Wix uses fixed prefixes. Per Wix's blog URL guide, blog posts live under /post/, and Wix's URL structure settings show store products under /product-page/.
| Old Wix URL | New WordPress URL | Action |
|---|---|---|
| /about-us | /about-us/ | Same path, nothing to do |
| /post/how-to-choose-a-venue | /post/how-to-choose-a-venue/ | Keep the prefix with a custom permalink |
| /product-page/blue-lamp | /product/blue-lamp/ | 301 redirect |
| /copy-of-services | /services/ | 301 redirect to the real page |
| /old-promo-2022 | /offers/ | 301 to the closest match, or let it 404 if there isn't one |
Here's the easy win. In WordPress, set the post permalink structure to /post/%postname%/. Your Wix blog URLs stay as they are, WordPress adds the trailing slash with its own redirect, and most of your redirect list disappears.
Where do the 301 redirects go?
On WordPress or your web server, not in Wix. A plugin like Redirection or your SEO plugin's redirect manager is fine for most sites. For large lists, use server rules.
Wix redirects stop working at launch
Once your domain points to WordPress, Wix never sees those requests, so redirects in the Wix URL Redirect Manager no longer apply. Every redirect has to live on WordPress or your server.
Google's site move guidance recommends server-side permanent redirects. Google has also said 301s should stay in place for at least a year. Don't delete them once traffic settles.
The rules I stick to:
- Redirect to the closest match, not the homepage. Google's site move guidance warns that sending many old URLs to one irrelevant page, such as the homepage, can be treated as a soft 404.
- No chains. Old URL to final URL in one hop. Update internal links so they point straight at the new URLs.
- Test every row. Run the old URLs through a bulk status checker before and after launch. Each one should return a 301 to a page that returns 200.
How do you rebuild a Wix site on Bricks Builder?
I'd rebuild a Wix site on Bricks Builder with a small set of templates, keeping every page's content identical to Wix at launch, the same way I handled the Aura Clips Framer rebuild. Bricks outputs clean HTML, which makes good Core Web Vitals scores much easier to reach than on most page builders.
Templates and dynamic data in Bricks also mean a small team can run a lot of pages without touching layouts. On Aura Clips I built service templates and a blog template, so a new service page picks up the layout and the team only edits the content. GA4 and Tag Manager handled the analytics. I wrote up what moves and what gets rebuilt in the Framer to WordPress migration guide, and the same split applies to Wix.
The SEO rule I care most about: change the platform, not the content. At launch, keep each page's copy, H1, H2s, title tag and meta description the same as on Wix. Improve the content a few weeks later, once rankings have settled. Change everything at once and if traffic dips, you won't know which change caused it.
What should you check before switching DNS?
Before pointing the domain from Wix to WordPress, freeze content on Wix, compare staging with the live site, test every redirect, check tracking and forms, copy your email DNS records and make sure WordPress allows indexing.
- 1
Freeze content on Wix
No new posts or page edits after the final export, so nothing gets lost between the two sites.
- 2
Compare staging with the live site
Check every page in the URL map: copy, headings, title tags, meta descriptions, alt text and canonical tags.
- 3
Load and test redirects
Import the full redirect list and test it on staging with a hosts file override.
- 4
Check tracking and forms
Same GA4 property and tags, every form submitting and every notification arriving.
- 5
Switch DNS with email intact
Copy MX, SPF and DKIM records first, then point the A record and confirm SSL is issued.
- 6
Turn indexing on
Untick 'Discourage search engines' in WordPress and check that robots.txt doesn't block the site.
That last step trips up a lot of launches. A staging site that was rightly hidden from Google goes live still hidden, and nobody notices for a week. Before launch, also rebuild the structured data Wix added for you (the Schema Markup Generator helps), run a Lighthouse report and fix what it flags with the Page Speed Fix Planner, and run the new server through the Security Headers Checker to see what's missing.
What should you check in Search Console after launch?
Submit the new WordPress sitemap in Google Search Console and check the Pages report every day for 404s and redirect errors. If you verified a Domain property through DNS, it carries over to the new server, so you don't lose your history.
Then go through this list:
- Submit the new sitemap. Rank Math and Yoast both generate one. Remove the old Wix sitemap if it's still listed.
- Skip Change of Address if the domain is the same. Google's Change of Address tool is for moving to a new domain. Most Wix moves keep the domain.
- Watch the Pages report daily. "Not found (404)" shows the URLs your map missed. "Page with redirect" is expected for old Wix URLs. If "Crawled, currently not indexed" keeps growing, look closer.
- Inspect your top pages. Run URL Inspection on the 20 pages that bring the most clicks and request indexing for each.
- Compare performance. Put the 28 days after launch next to the 28 days before, page by page, for clicks and impressions.
- Check Core Web Vitals once field data comes in.
Some movement is normal while Google recrawls. Its site move documentation says it takes time for pages to move in the index. If clicks are still down after the first few weeks, work through my traffic drop recovery checklist, or get a second pair of eyes through my technical SEO service.
How long does a Wix to WordPress migration take?
For a brochure site with a handful of layouts, usually weeks, not months. A store, a big blog or custom integrations take longer. The timeline depends on templates and content much more than on page count.
What stretches it:
- Unique templates. Each new layout has to be built in WordPress and tested on mobile.
- Blog clean-up. Re-hosting images, fixing internal links and restoring categories after the RSS import.
- Store data. Checking variants, prices and images after the WooCommerce import.
- Integrations and forms. Bookings, CRMs and notification emails each need rebuilding and testing.
- Redirect testing. Every row in the URL map gets checked on staging and again after the DNS switch.
- Content sign-off. Slow feedback delays launch more often than the build does.
Don't plan on a weekend. FatLab notes that DIY Wix migrations tend to take several times longer than planned, and that matches what you'd expect once the redirect testing and image clean-up start. For typical timelines by project type, see how long it takes to build a website.
What should you ask a developer before hiring?
Ask how they'll build the URL map, where the redirects will live and how they'll test them, and what they'll do in Search Console after launch. The answers tell you if you're getting a proper migration or just a rebuild:
- Will you build a full URL map from Search Console and a crawl, or only from the sitemap?
- Where will the redirects live, and how will you test them?
- Will page copy, headings and meta tags stay the same at launch?
- How will you protect my email records during the DNS change?
- What will you check in Search Console after launch, and for how long?
- Who owns the hosting, domain and WordPress admin when the project ends?
If you get a vague answer to any of these, keep looking.
Ready to move off Wix?
Before you talk to anyone, export your Search Console Pages and Performance reports. That list of URLs is the real scope of the project. Then book a 20-minute call or read about my WordPress builds on Bricks, Elementor and Oxygen. I'll tell you what the move involves and where your rankings are at risk.
