Squarespace export vs. a static snapshot
Squarespace's export (Settings → Import & Export) is designed for moving content into WordPress. It covers blog posts and basic pages but not your template, custom CSS or most block types, and product pages aren't included. You'd have to rebuild the design by hand.
A static snapshot works the other way round: it captures the rendered site — the HTML and assets Squarespace serves to visitors — so your design comes with it. It's ideal for brochure sites, portfolios, event sites and archives that mostly present content.
What to plan for
- Commerce, scheduling and member areas run on Squarespace's backend and won't work on a static host.
- Forms and newsletter blocks post to Squarespace. Map them to a form service or your own endpoint before you switch.
- Image URLs point to Squarespace's CDN. The converter downloads the images it finds into your bundle, so the copy doesn't depend on your old account.
- Interactive blocks that rely on client-side scripts may need checking — the export captures server-delivered HTML. Preview the ZIP locally before switching DNS.
Moving your domain without losing traffic
Keep page paths identical where possible (Squarespace uses clean paths like /about, which carry over directly). Add 301 redirects for anything that changes, upload the generated sitemap.xml to Google Search Console, and keep your Squarespace plan active until the new host is verified.
How to do it with Static Converter
- 1Publish everything you want to keepUnpublished or password-protected pages can't be crawled.
- 2Add your Squarespace URLCreate a free account and add the live domain. Choose a full crawl.
- 3Convert and optimizeEnable WebP images and minification, and map any forms to a new endpoint.
- 4Deploy the ZIPUpload to Netlify, Cloudflare Pages, S3 or any host, then move your domain.