Website Builder Export: What Actually Leaves Each Platform
1 blog page — the ceiling of Squarespace's export the number that matters here
By Stan K.
Squarespace's export ships one blog page and hotlinks your images to a CDN that goes dark when you cancel. Webflow's export needs a $19/mo Workspace and empties the CMS. Wix publishes no site export at all. Plus the 301-map and 500-URL crawl checklist to run before you cancel anything.
Lock-in is not a feeling; it is an export specification. Every website builder will let you leave — the question is what survives the trip. We verified each platform’s export reality against official documentation on 2026-11-13, and the honest summary is: Squarespace exports a blog, Webflow exports a design system, and Wix does not publish an export at all. Here is each one, with the pre-cancel checklist that protects your SEO.
Squarespace: one blog, hotlinked images, and a store that stays behind
Squarespace’s export is a WordPress .xml file, and it only runs from a published, publicly available site — you cannot export from a trial. What the XML contains, per the official help article: one blog page, including all of its posts and up to 1,000 comments per post. If your site has more than one blog, only one exports. Layout pages, text blocks, and basic galleries make the trip.
What does not: store and product pages, portfolio pages, custom CSS, page-specific headers, footers and sidebars, drafts — all explicitly listed under content that doesn’t export. Products leave through a separate CSV capped at 10,000 products, and the CSV drops product image alt text and featured/variant images on the floor.
Then the trap that hurts most: images are not in the export. The XML only references them as hotlinks to images.squarespace-cdn.com, and Squarespace’s own documentation says it directly — the image links stop working after you cancel your site. An import into self-hosted WordPress may pull references instead of files, and every one of those references becomes a broken image on the day your plan dies. The fix is mechanical: download or sideload every image into the new host before canceling, not after.
Webflow: a paid Workspace, clean code, and an empty CMS
Webflow’s code export requires a paid Workspace plan — Core at $19/mo or Growth at $49/mo, billed yearly — which is separate from and additional to your site plan. That is the entry fee. What you get is genuinely good: a ZIP of semantic HTML, CSS, JS with interactions, and — the opposite of Squarespace — your uploaded images are included.
But the export is a design system, not a website. Collection items do not export; dynamic lists render empty states and you get “empty Collection template .html files only” (CMS data can be pulled separately as CSV and rewired). The native features break on arrival: forms, site search, password pages, user accounts, the e-commerce checkout, and localizations beyond the primary locale are all documented as not working in an export. You keep the front end and rebuild everything that moves.
Wix: no site export, and we mark it honestly
Wix is the bluntest lock on the market: there is no site export. We attempted to verify the specifics against Wix’s help center and could not — it is client-rendered and returned nothing to our crawler — so we publish only the structural fact and mark the rest unverified: Wix documents no way to download your site as files, and no design, layout, or code survives a departure. Data can leave (content-level exports), but the site does not; leaving Wix means rebuilding. If you build there, price the rebuild into the decision on day one.
Lock-in also wears a payments costume. Shopify charges third-party transaction fees of 2% on Basic (1% Grow, 0.6% Advanced, 0.2% Plus) if you don’t use Shopify Payments as your primary gateway — layered on top of the gateway’s own rate. On $120k/year of sales, that 2% is $2,400/year of pure platform fee (our arithmetic from the verified rate). One verified relief: with Shopify Payments active, PayPal transactions are exempt from the third-party fee.
The SEO migration: crawl first, 301 everything, then cancel
The ranking risk in any migration is quiet URL and metadata drift, not the platform change itself. The verified specifics: Squarespace blog post URLs always begin with the blog page’s slug — /blog/ is merely the default and is changeable — and product URLs in 7.1 follow store-slug/p/product-name, so /shop/p/… only if your store page is slug-named “shop.” These are defaults, not laws, which means you must read your actual URLs, not assume the template.
The order of operations matters because the source dies at cancel:
- Crawl before cancel. Screaming Frog’s free tier crawls up to 500 URLs — export every URL, H1, title, meta description, alt text, and status code while the old site is still live.
- Build a 1-to-1 301 map for every URL that has ever ranked. Redirect chains and wholesale path redesigns are how migrations lose 20–50% of organic traffic.
- Preserve metadata by hand. Builders auto-generate sitemaps, canonicals, and structured data; a static or manual rebuild can silently strip them or reset canonicals to a staging URL. Diff the crawl against the new site before switching.
- Move the images (Squarespace especially) — then, and only then, cancel.
The exit-cost table
| Platform | What exports (official docs) | What dies on arrival | Extra cost to leave |
|---|---|---|---|
| Squarespace | WordPress XML: 1 blog, posts + up to 1,000 comments/post; product CSV (10,000 max) | store pages, portfolio, CSS, headers/footers, alt text, all images (CDN hotlinks die at cancel) | $0 export; your labor + image rescue |
| Webflow | ZIP: HTML/CSS/JS + uploaded images | CMS items (empty templates), forms, search, accounts, ecommerce, localizations | Workspace Core $19/mo or Growth $49/mo (yearly), on top of site plan |
| Wix | nothing verified beyond data-level export — no site export | the entire site: design, layout, code | full rebuild |
Before you pick a builder at all, check what its free tier and first paid plan actually contain — that ladder is verified here. And if the export reality is pushing you toward owning your stack, we ran the numbers both ways: self-hosted WordPress versus static at $11.81/year. The plan-by-plan tables live in the Website builders hub.