Learn how to rebuild your existing Squarespace site in Webflow.
This article walks you through migrating an existing Squarespace site to Webflow. While Squarespace is great for getting a site up quickly, Webflow gives marketers, designers, and developers a single platform to build, manage, and optimize sites that drive business impact.
Note
There's no automated way to convert a Squarespace site into a Webflow site. Squarespace designs, layouts, and content can't be imported directly into Webflow. Migrating from Squarespace to Webflow is a rebuild, not a transfer. You'll recreate page layouts, styles, CMS structure, and interactions manually in Webflow, using your Squarespace site as a visual and structural reference.
High-level steps:
Complete the pre-migration audit checklist
Rebuild your site and reconfigure all Site Settings in Webflow
Lastly, set up your domains, redirects, and DNS settings to minimize downtime
Pre-migration audit checklist
Before you begin rebuilding in Webflow, perform a thorough audit of your current Squarespace setup. Check out Squarespace's help pages for detailed steps on how to do the following.
Pages
Inventory all pages (including landing pages, blog pages, legal/privacy pages, and error pages)
Note current URL paths, folder nesting, and any subdomain or language-based path (e.g., /es/, /fr-CA/)
Note all page transitions or animations
CMS, data, and assets
List all content types (e.g., blog posts, portfolio items, products)
Export your commerce products from Squarespace. You can use these to help populate your Webflow CMS.
Plan for images separately. Squarespace doesn't support bulk image export — you can only download individual images one at a time from the Asset library. Budget time for this step if your site is image-heavy.
Note current asset libraries (images, videos, downloads) including file names, asset locations, alt text, and any versioning or large asset usage
Fonts and typography
Audit all fonts used in your Squarespace site, including custom fonts and Adobe Fonts
Confirm that you have the appropriate licenses to use each font in Webflow
Document font sizes, line heights, letter spacing, and responsive typography rules so you can accurately rebuild your type system in Webflow
Domains
Identify your primary domain and any additional domains or subdomains in use
Document domain-level routing needs for locales (e.g., es.domain.com)
Note whether your domain is registered through Squarespace or a third-party registrar — this affects how you'll handle the DNS cutover
SEO and redirects
Create a list of all current URLs with their meta titles, meta descriptions, Open Graph tags, and canonical tags
Note any existing redirects, SEO settings for different locales, and schema data
Document your analytics and tracking setup (Google Analytics, Google Search Console, tag manager, etc.)
For multilingual pages, document your current hreflang implementation
Forms, integrations, and custom code
List all forms and their endpoints (e.g., CRM, email marketing tool)
Note any Squarespace extensions, embedded tools, analytics, scripts, and third-party widgets
List all custom code snippets embedded in your site (in the head, body, or footer)
Note any dynamic behavior outside of Squarespace's built-in tools (e.g., external APIs)
Note any well-known files for transfer
Components, templates, and interactions
Identify global design elements (e.g., navbars, footers, cards, announcement bars, promotional pop-ups)
Record reusable layout patterns
Note interactive elements: hover states, animations, and any custom code embeds
Process and performance
Plan your DNS cutover (i.e., changing your DNS settings from Squarespace to Webflow), staging workflows, and publishing window. You’ll want to migrate DNS only after you've completed all other migration steps and you're ready to publish, to minimize site downtime.
Document existing performance or SEO issues you want to address during migration (e.g., large image files, slow scripts)
Set up your Webflow site
Once you've completed your audit and planning, you can start building the foundation in Webflow.
Create a new site in your Webflow Workspace
Choose the right Site plan based on your traffic, CMS scale, and feature needs
If you need localization, go to Site settings > Localization, set your primary locale and additional locales, and decide on your URL strategy (subdirectory vs. subdomain vs. separate domain)
Create a CMS architecture that maps to your Squarespace content structure
Build your global style guide: define your color palette, typography, spacing, utility classes, and reusable components
Set up integrations, forms, and custom code embeds
Migrate content and structure
Now you're ready to move content and build the new site in Webflow.
Rebuild each static page in Webflow, matching layouts and responsive behavior
Create CMS Collections and import content via CSV or manually
Upload and organize assets in the Webflow Asset panel: images, videos, downloads, and icons. Make sure every image has alt text and is optimized (compressed, correct format).
-
For each locale (if applicable):
Duplicate or set up localized variants of pages and CMS items. Use Webflow’s built-in machine translation to accelerate localization, then review and refine translations manually to ensure accuracy and brand consistency.
Ensure slugs, meta tags (title/description), and asset alt text are localized
Configure localized SEO settings including titles, descriptions, Open Graph data
Rebuild Squarespace animations and interactions using Webflow Interactions with GSAP or custom code
Re‑implement global components (navigation, footer, banners, callouts)
Re-build forms and integrate with tools (e.g., Zapier, HubSpot) as needed
Configure analytics: place tracking scripts and tag managers in Site settings > Custom code or page settings as needed
Use the Audit panel to optimize SEO and accessibility
Publish your staging version and run a full QA across breakpoints and locales
In Site settings > Publishing, add your custom domain, subdomain(s), and configure DNS. Learn how to update DNS records when migrating a live site to Webflow.
Note
Webflow AI can help at multiple stages: generating placeholder copy for static pages or CMS items, suggesting titles, meta descriptions, and alt text, and translating content during localization setup.
Redirects, SEO, and publishing
To preserve search rankings and prevent 404 errors:
Important
Redirects should be added before your domain cutover to prevent traffic loss during launch.
Once ready:
Push your site live and monitor in Google Search Console
Verify that your localized versions are indexed properly
Test locale switching, redirects, and canonical structure
Submit your new sitemap (if changed) to Google Search Console and other search engines, then monitor for indexing errors or 404 spikes
After launch: what to monitor
Post-launch, monitor the following:
Traffic and search engine indexing
Redirects and crawl errors
Form submissions and conversion metrics
SEO metrics by locale and landing page
Load times and core web vitals
Locale switching functionality