Squarespace to WordPress

How does a Squarespace site map onto WordPress?

A Squarespace site is a set of pages built from stacked sections, a blog or two, perhaps some galleries, and a handful of built-in commerce or scheduling features. WordPress has a direct home for most of that. Pages become pages built from native blocks, blog collections become posts with their dates and categories, and galleries become Gallery blocks filled with images from your own Media Library. What WordPress never receives is a copy of Squarespace markup inside a Custom HTML block, because that would give you pages nobody can edit comfortably.

The move works best with two sources side by side: the export file for structured content, and the live site as the visual reference for layouts.

Before you start: preparing the Squarespace side

• Make a list of every page, blog, gallery and product page, including anything not linked in navigation
• Run the export from your Squarespace settings, where your plan and site version offer it, and keep the file safe
• Save the site's fonts, colours and button styles from the design panel
• Note every form, newsletter block, scheduling embed and member area
• Record the URL of each blog post and page for redirect planning
• Capture desktop and mobile screenshots of the pages that matter most
• Set up a clean WordPress install on staging, away from your live domain

What does the Squarespace export cover, and what does it miss?

Squarespace can export some content in a WordPress-compatible format, and WordPress can import that file with its standard importer. In practice the file carries the content well and the layout poorly. Blog posts usually arrive with titles, text, dates, authors and categories intact. Basic pages arrive as text. Product pages, event pages, album pages and many block types are left out, and section layouts are flattened. Images frequently still point at Squarespace's servers after import, which matters later.

So import first, check what landed, and let the rebuild handle everything the file could not carry.

How do you rebuild Squarespace layouts as native blocks?

With content imported, install NibWP on the staging site. NibWP is a WordPress plugin that makes the site an MCP server, so an AI client such as Claude, ChatGPT or Cursor can build and edit pages directly. The MCP switch is off until you turn it on, it is locked to the domain where you enabled it, and each connected client has its own application password.

Sections and grid layouts

Point the agent at one live Squarespace page and ask it to rebuild the layout on the matching WordPress page as native blocks. A banner section becomes a Cover block, side-by-side content becomes Columns, image and text pairs become Media and Text blocks, and section background colours become Group blocks with styles from your palette. Newer Squarespace layouts place blocks on a flexible grid, so expect the agent to simplify tight overlaps into clean rows that also work on phones.

Galleries, summary blocks and index pages

Gallery sections become Gallery blocks. Summary blocks, which show recent posts or products, are best replaced with a Query Loop or Latest Posts block that updates by itself. Index pages, which stitch several pages into one, usually turn into a single long page or a parent page with children, and it is worth deciding which before the agent starts.

Fonts, colours and buttons

Squarespace templates come with a coordinated set of fonts, colours and button shapes, and visitors recognise your site by them. Recreate that set once as global styles before rebuilding pages in bulk. Share the font names and colour values from the design panel with the agent, along with a screenshot of your primary and secondary buttons, and ask it to define them in your theme's styles. Squarespace often applies different colour themes to different sections, so decide how many section styles you really need, perhaps a light one, a dark one and an accent one, and turn each into a reusable Group block pattern. Every later page then uses the same small set, which keeps the site consistent when you or a colleague add pages next year.

Ask for a short report at the end of each page listing anything it skipped, then fix those items while the page is fresh in your mind.

How do you stop images loading from Squarespace?

After an import, scan posts for image addresses that still point to Squarespace. Ask the agent to find every image that is not hosted on your WordPress site, download each one into the Media Library, and update the references in place. Check alt text while you are there. Only cancel the Squarespace plan once a search of the site finds no remaining external image links, otherwise images will break the day the old site goes offline.

Which Squarespace features need a replacement?

Treat payments, bookings and member data as human tasks. The agent can rebuild the pages around them, but you should configure and test the underlying services yourself.

How do you move the domain without losing traffic?

Keep blog slugs identical where possible, and add 301 redirects for every URL that changes. Squarespace blog posts often include a date or collection path in the address, so compare old and new patterns before launch. Copy page titles and SEO descriptions across, then submit your new sitemap. Point the domain at your new hosting last, after the staging review, and keep the Squarespace subscription running for a short overlap.

Can you choose a different target than blocks?

Yes. If you would rather work in Elementor, the HTML to Elementor guide uses the same page-by-page method. When you only need one or two pages moved from a live site, the live URL to WordPress guide is a lighter route. Teams that still have the original Figma designs can start from the Figma to WordPress guide, and saved page source fits the HTML to WordPress guide.

Is there a dedicated Squarespace converter?

The standard export and import path exists and covers posts reasonably well, and paid migration services take on whole sites. We have not found a WordPress MCP plugin with a workflow designed for Squarespace in particular. This guide combines the standard import with a general agent for the layouts, and the trade-off is time: every page is reviewed by a person. For a site you plan to keep editing for years, that review is usually worth it. You can compare other sources on the converters directory.

When your export file is ready, try NibWP free and rebuild your first layout on staging.

Troubleshooting

Squarespace gives you an export file that covers part of a site. These problems come from the gap between that file and a finished WordPress site.

The import brought posts but not images

The Squarespace export links to images rather than carrying them. Import the posts, then download the images you own and re-upload them, updating each reference. Check a sample of posts for broken images.

Blog formatting looks off

Squarespace blocks do not map one to one to WordPress blocks. Fix repeated problems such as extra spacing or odd headings in bulk, then review each post.

Gallery and portfolio pages are empty

These page types do not export fully. Rebuild them with gallery blocks, uploading the images again and adding alt text.

Store products did not move

Squarespace commerce data needs a separate migration to a plugin such as WooCommerce. Treat it as its own task and test checkout.

Fonts and spacing do not match

Squarespace styling is stored in its own settings. Read the values from the live site and set them in WordPress Global Styles.

Domain stays pointed at Squarespace

If the domain is managed by Squarespace, update DNS records to the new host after testing. Allow for propagation and keep the old site live until the new one responds.

When a page looks different after import, check the block types in the editor. Squarespace content often arrives as a few large blocks, and splitting them into smaller native blocks makes the page easier to edit. When you are unsure whether a fault comes from the import or the theme, switch to a default block theme for a moment; if the page looks right there, the theme is the cause, and you can fix it without redoing the import. Keep the export file and the original screenshots together, because they are the fastest way to settle an argument about what the old page looked like.

Doing it by hand vs with an AI agent

Squarespace sites are usually tidy, which helps a rebuild. This table shows where each approach fits.

Squarespace sites tend to be simple, so a careful rebuild is realistic. The agent saves effort on layout and uploads, while you keep control of the design decisions. Give yourself time for small fixes after the import. Spacing, image sizes and formatting rarely arrive perfect, and a calm second pass through every page turns a rough import into something you are happy to publish.

Checklist before you publish

Run this list on a staging copy and keep your Squarespace site online until you finish it.

• A Squarespace export was downloaded and kept
• Images were saved from your own library
• Galleries and portfolios were rebuilt
• Commerce data has its own plan
• Fonts, colors and spacing match the design
• Redirects are ready for changed URLs
• Forms were tested
• Mobile layout was checked
• A backup exists before launch
• The Squarespace site stays online until the switch is verified
• The import log showed no skipped items
• Alt text was added to the images that matter

Store the Squarespace export file with your notes. It is your backup if something is missed. If other people edit the site, agree roles before launch and give each person a separate login. It prevents accidental changes to templates and makes it clear who to ask when something looks different.

Glossary

Vocabulary for the move.

Export file: a file from Squarespace that contains pages and posts

Gallery block: a block that displays several images together

Global Styles: the WordPress panel for site-wide fonts, colors and spacing

DNS: the system that connects a domain name to a server

Plugin: software that adds features to WordPress

301 redirect: a permanent redirect from an old address

WordPress importer: the tool that reads an export file and creates posts and pages

Staging copy: a private version of the site used for testing

Common mistakes

Squarespace sites look simple, which makes the export feel more complete than it is. The mistakes below almost all come from trusting the export file to do more than it does.

• Trusting the export to be complete. It misses many layouts and images.
• Hotlinking images from Squarespace. They disappear when the plan ends.
• Forgetting the commerce side. A store move needs a plan, see Shopify to WooCommerce for a similar one.
• Pasting whole pages as HTML. It keeps the look but not the editability, as native blocks versus a Custom HTML block explains. A similar move is covered in Wix to WordPress.
• Cancelling Squarespace before the new site is live. Keep both until you are sure.
• Not reading the import log. Skipped items are easy to miss.

Open the export, read what it contains, and list what it does not. That list is your real to-do list for the rebuild.