Move a Squarespace Site to an AI-Built Site
Move a Squarespace site to an AI-built site: what Squarespace's export really contains, what you must rebuild, and a redirect map that protects rankings.
To move a Squarespace site to an AI-built site, begin with an inventory of what leaves the old platform, not with the new design. Squarespace's export is narrower than most people assume, and the gap between what exports and what you have is your rebuild list.
The second job is protecting the traffic you already earn. That depends on one table: every old URL, matched to its new home.
What the Squarespace export contains
Squarespace's guide to exporting your site describes an .xml file in a WordPress-compatible format, intended for importing certain content types into WordPress. You do not have to use WordPress, the file is simply a structured copy of your content that an AI tool can read.
According to that guide, the export includes:
Layout pages
Text and image blocks
Gallery pages, in version 7.0
One blog page, with all of its posts and up to 1,000 comments per post
Text from embed and Instagram blocks, with minimal structure
And it does not include:
Other page types, such as album, cover, index, info, calendar, portfolio and store pages
Content in page-specific headers, footers and sidebars
More than one blog page
Dropdowns, audio blocks, video blocks and product blocks
Drafts, style settings and custom CSS
Linked PDFs may appear in the file but cannot be imported. The page I read may differ from your version of Squarespace, so open your own export before you plan around it.
Move a Squarespace site to an AI-built site, step 1: the inventory
Open your live site and list everything, then mark each item as exported or not. A simple table works:
Item | In the export? | Action |
|---|---|---|
Home, About, Contact pages | Yes | Import text, redo layout |
Blog (one blog page) | Yes | Import posts and comments |
Second blog | No | Copy by hand or by script |
Shop and product pages | No | Export products separately, rebuild checkout |
Videos and audio | No | Re-upload, re-embed |
Footer and sidebar content | No | Rewrite |
Forms and email signup | Not listed | Recreate and reconnect |
Custom CSS and styles | No | Rebuild from your design |
Anything not clearly in the export goes on the manual list. Do this before you cancel anything.
Step 2: build the redirect map
This is the step that decides whether your rankings survive. A search engine indexed your old addresses. If the new site answers those addresses with an error, the pages disappear from results and the links pointing at them are wasted.
Ask the AI to read the export, list every URL, and produce a table like this:
Old URL | New URL | Type |
|---|---|---|
/about-us | /about | 301 |
/blog/2023/5/opening-hours-change | /blog/opening-hours-change | 301 |
/shop/linen-apron | /products/linen-apron | 301 |
/summer-sale | /offers | 301 |
/old-page-removed | (none) | 410 |
A 301 tells search engines the move is permanent. Pages that have no equivalent can return a clear not found or gone response, which is better than redirecting everything to the home page. Keep the dated blog address pattern in your map even if you change the format, because those are the addresses other sites link to.
Then test the map. Take your top 20 pages, which Search Console can list for you, and check each one on the new site before you switch the domain. Getting your AI app indexed by Google covers submitting the new site afterwards, and SEO for an AI-built app with no budget covers keeping it healthy.
Step 3: rebuild what did not export
Work in this order: pages with the most traffic first, then the contact route (a form that does not work is the costliest silent failure), then the rest. Keep the page titles, meta descriptions and headings from the old pages, since changing them at the same moment as the platform makes ranking changes impossible to diagnose. The structure of a good page is in prompting AI to write a landing page.
Step 4: move the domain last
Build and test the new site on a temporary address. When the redirect map passes, point your domain at the new site, following moving an AI-built app to a custom domain. Keep the Squarespace subscription active for a few weeks after, so you can compare, copy anything you missed and roll back if something is badly wrong.
What to watch for the first month
Search Console coverage reports for pages the new site cannot find
A drop in your top pages. Small movement is normal, a collapse means a broken redirect
Form submissions and email signups, checked by sending test ones yourself
Images that loaded from the old platform's address and now fail
If your site is also how people find you locally, local SEO with AI lists the listings and details to update. The overall build process sits in how to build an app with AI.
Frequently asked questions
Can I export everything from Squarespace?
No. Squarespace's export covers certain page types, text and image blocks, galleries and one blog. It leaves out store pages, product blocks, audio and video blocks, drafts, style settings and custom CSS.
Will moving my site hurt my Google rankings?
It can if old URLs stop working. A 301 redirect for each old address, tested before launch, and unchanged titles and headings greatly reduce the risk.
How long should I keep my old Squarespace site?
A few weeks after launch is sensible. It lets you compare pages, retrieve anything you missed and check what the old site did before you cancel.
Do I need WordPress to use the Squarespace export file?
No. The file is in a WordPress-compatible format, but it is just structured content. Any tool that can read it can use it, and you can ask an AI assistant to inspect it.
How did this land?
About the author

Growth & SEO Lead
Manuele covers distribution: SEO, content strategy, and how AI-built products find their first thousand users. He tests everything he recommends.


