The short answer
Direct answer
Wix's own SEO tools are capable — the 2025 Web Almanac puts mobile Core Web Vitals pass rates at 74% for Wix and 45% for WordPress — but a classic Wix site still has to run on Wix's servers, and WordPress's official export is content, not a portable website. Stay if a brochure already fits a template and the cash cost of staying is lower. Leave when you need code you can host independently, a flow custom code cannot reach, or more redirect control than the manager allows.
If you are not sure which builder you are on, the Wix / Squarespace checker shows the evidence from the live site.
The seven limits
Each item below is a documented platform limit, not a taste complaint. Self-hosted WordPress will often let you change the code; the hold-back there is the usual stack, not a failing of the owner.
1. A classic Wix site has to run on Wix's servers
You cannot export a classic Wix site and host the live Wix site elsewhere as working Wix technology. Wix is explicit that this is a SaaS limit, and that the content you build still belongs to you.
The limit. “Since Wix is a SaaS solution, your site must run on Wix’s servers… The reason you can't use another host for your Wix site is that the SaaS architecture does not support external hosting.”
Source: Exporting or Embedding Your Wix Site Elsewhere (updated 5 October 2026, read 18 November 2026)
What to do about it. Keep the domain, copy, photos, and the URLs that already rank. Treat a move as a rebuild of the front, not a lift-and-shift of the live Wix site.
2. Wix CMS export is a CSV of collection content, not a codebase
You can take items and fields to Sheets or Excel. You cannot take the site as code this way.
The limit. Wix's CMS export writes a CSV of collection content for another application such as Google Sheets or Excel — the entire collection, a filtered set, or field names only.
Source: CMS: Exporting Content from Your Collection (updated 10 November 2026, read 18 November 2026)
What to do about it. Export the collections before you cancel. Use that file as inventory. It is not a portable website.
3. Dashboard custom code cannot fix app or layout problems from the inside
Custom code added from the dashboard is browser-only. It has no access to Wix APIs or to Stores, Bookings, or Pricing Plans. It cannot rely on stable class names or IDs — Wix generates them dynamically, and they may break on republish — and it has no guaranteed DOM compatibility with the Wix rendering engine. For Wix Harmony sites, site code is not supported at all, so this limited custom-code path is one of the main extension options.
The limit. “Custom code can't interact with Wix page elements, data collections, backend methods, or business solutions like Stores, Bookings, or Pricing Plans.” CSS or JavaScript that targets generated class names and IDs “may break when a site is re-published or updated.”
Source: About Custom Code (read 18 November 2026)
What to do about it. If the job is a third-party snippet, custom CSS, or JSON-LD, dashboard custom code can still help. For Organization or LocalBusiness JSON-LD you can paste yourself, use the schema generator. If the job is a booking or store flow that has to live inside Wix's own apps, this path will not reach it.
4. Redirects have hard limits
The URL Redirect Manager allows a maximum of 5,000 redirects per Wix site. You cannot create a 301 from the homepage in that manager. Wix Blog slug changes do not get automatic redirects — you have to add them by hand.
The limit. FAQ: “You can create a maximum of 5,000 redirects per Wix site.” and “it is not possible to create a 301 redirect from your homepage using the URL Redirect Manager.” The same FAQ states the Blog exception. Wix's SEO guide repeats the cap: “There is a hard cap of 5,000 redirects per site, but that amount should cover most use cases.”
Source: Setting Up a 301 Redirect for a Page on Your Site (updated 16 November 2026, read 18 November 2026)
Also: Wix SEO guide (updated 22 January 2024, read 18 November 2026).
What to do about it. If you are well under the cap and do not need a homepage 301 in the manager, this is not a reason to leave. If you do need a larger map, or you want to see whether old URLs still resolve after a change, use the redirect checker.
5. Even Studio Two's “export to code” is not full independence
The feature is in beta. A site with dynamic pages cannot be exported. Widgets from installed apps (other than Editor React Components) fail in preview and in the build. Member login does not work on an exported site. Lightboxes do not appear on the running site.
The limit. Wix's own wording: “Hosting is independent of Wix, but the running site isn't. It loads fonts and media from Wix and calls Wix APIs for any business features on the page. Think of an exported site as a frontend you host for a site Wix still runs.”
Source: About Exporting Your Site to Code (read 18 November 2026)
What to do about it. Treat Studio Two export as a way to work on a frontend you still host against Wix, not as a portable codebase you can walk away with.
6. WordPress's official export is content, not a portable website
Tools → Export writes a WXR/XML file of posts, pages, custom post types, comments, custom fields, categories, tags, taxonomies, and users. It does not export the theme or plugins. Leaving WordPress is still a rebuild of the front.
The limit. The WXR file “will contain your posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users.” Theme and plugin code are not in that list.
Source: Tools Export screen (updated 8 June 2024, read 18 November 2026)
What to do about it. Export the WXR before you move. Keep the URLs that matter. Plan to replace the theme and plugins, not to port them.
7. A typical WordPress + page-builder stack is hard to fix without changing how the site is built
This is not a claim that WordPress forbids a fix — self-hosted WordPress will usually let you change the code. The 2025 Web Almanac is the source for what happens at scale.
The limit. Mobile Core Web Vitals pass rate is 45% for WordPress vs 74% for Wix. Elementor is on 43% of mobile page-builder sites (Figure 12.6), down from about 56% in 2024. A custom front is one way to fix the stack. It is not the only way.
Source: CMS | 2025 | The Web Almanac (updated 16 January 2026, read 18 November 2026). Published 15 January 2026.
What to do about it. If you own the hosting and can change the theme, start there. If the page builder is the product, swapping the front is a rebuild, not a settings tweak.
Who should stay on Wix
Wix is a capable host for a lot of sites. Stay if the facts below describe you. Performance and SEO tooling are not, on their own, a reason to leave.
- The site is a brochure, menu, or catalog that already fits a Wix template, and the owner wants to edit it themselves.
- The cash cost of staying is lower. Our Wix & Squarespace cost calculator already says builders are cheaper in cash.
- Real-user performance is not the reason to leave. HTTP Archive's 2025 Web Almanac CMS chapter (published 15 January 2026, last updated 16 January 2026, almanac.httparchive.org/en/2025/cms, Figure 12.8) puts mobile Core Web Vitals pass rates at 74% for Wix (the figure description says Wix rose from 55%) and 45% for WordPress. Duda leads at 85%, TYPO3 at 79%. Figure 12.9: mobile LCP good-rate is 81% for Wix and 53% for WordPress. Figure 12.10: mobile CLS good-rate is 95% for Wix in 2025 (about 86% in 2024) versus “around the 84% mark” for WordPress. Median Lighthouse performance (Figure 12.12): Wix 87 desktop / 64 mobile; WordPress 63 desktop / 41 mobile. Median Lighthouse SEO (Figure 12.13): Wix 100, WordPress 92.
- The site is well under the 5,000-redirect cap, does not need a homepage 301 in the redirect manager, and does not need a portable codebase or a booking/store flow that Wix custom code cannot reach (see items 3–5).
| Measure | Wix | WordPress |
|---|---|---|
| Mobile CWV pass rate (Fig. 12.8) | 74% (from 55%) | 45% |
| Mobile LCP good-rate (Fig. 12.9) | 81% | 53% |
| Mobile CLS good-rate (Fig. 12.10) | 95% (about 86% in 2024) | around the 84% mark |
| Median Lighthouse performance (Fig. 12.12) | 87 desktop / 64 mobile | 63 desktop / 41 mobile |
| Median Lighthouse SEO (Fig. 12.13) | 100 | 92 |
When WordPress is fine
Self-hosted WordPress usually lets you change the code. The hold-back is the typical stack — a page builder, a pile of plugins, a theme you do not own — not the owner. If you can edit the theme, drop a builder, and host the files yourself, you already have an escape hatch that classic Wix does not. Official export is still content, not a portable website, so leaving WordPress for a custom front is a rebuild either way.
When to leave
Leave when at least one of these is true:
- You need code you can host independently.
- You need a flow that custom code and the app marketplace cannot do cleanly.
- You need more redirect or URL control than the manager allows.
- You have outgrown the template.
No page here promises rankings or traffic after a move.
Before you decide, score the live site against the website design checklist.
Comparing options? See our fair guide to Wix and Squarespace alternatives.
For the how-to, read Moving from Wix or Squarespace to a custom website.
Outgrown your platform? Nuvora builds custom websites you can take with you, for $500/month, first month paid upfront, with full ownership after 24 months.
Sources
Re-opened 18 November 2026. Update dates are the ones printed on each page.
- Exporting or Embedding Your Wix Site Elsewhere, updated 5 October 2026, read 18 November 2026.
- CMS: Exporting Content from Your Collection, updated 10 November 2026, read 18 November 2026.
- About Custom Code, read 18 November 2026.
- Setting Up a 301 Redirect for a Page on Your Site, updated 16 November 2026, read 18 November 2026.
- Wix SEO guide, updated 22 January 2024, read 18 November 2026.
- About Exporting Your Site to Code, read 18 November 2026.
- Tools Export screen, updated 8 June 2024, read 18 November 2026.
- CMS | 2025 | The Web Almanac — published 15 January 2026, updated 16 January 2026, read 18 November 2026.
- CMS | 2024 | The Web Almanac, read 18 November 2026.