Choose the public pages to capture

Start with the live custom domain or published site address. Make a list of landing pages, blog articles, galleries and public product pages you need. Restricted member content and private editing views are not public HTML inputs.

Capture one representative page, review it, then try site scope. Compare the report with your page list so an unlinked article or missing gallery is identified before launch.

Test galleries and Squarespace services separately

Check image blocks, gallery controls and menus at several widths. Some media or scripts can still load from Squarespace; inspect those dependencies if your goal is to remove reliance on the original hosting.

Scheduling, form delivery, commerce and memberships need their own integrations. A copied booking button may still point to a working external service, while a copied member layout does not enforce access. Test the behavior you intend to keep.

Publish the static version without losing navigation

Open important article and gallery URLs directly on the new host. Compare page titles, descriptions and link destinations. Changing hosts does not by itself migrate the underlying content-management workflow.

Use a temporary deployment for test bookings, form submissions and purchase journeys. Switch your domain only after those flows work and the exported public content has been reviewed.

Edit, deploy and protect your search URLs

Keep the downloaded HTML, CSS and assets together. Store a copy in your own GitHub repository to track changes; a repository is source storage, so configuring a deployment is a separate step. You can publish static files to your own Cloudflare account or another compatible static host.

For changes through an AI agent, connect it to FNJ MCP and give it the intended site and a specific task. Review the draft and its preview before publishing. Use the agent prompt library for content, links and CMS tasks, and the deployment guide for the next steps.

Keep existing page paths when practical. Map changed URLs to their closest replacements with permanent redirects. Check titles, descriptions, canonical URLs and internal links on the final domain, then submit its sitemap in Search Console. These checks help search engines find the replacement pages; they do not guarantee unchanged rankings.

Google Search Central: moving a site with URL changes

Your Squarespace launch checklist

Open galleries and image blocks on phone and desktop.
Check event, scheduling, member and store links for remaining Squarespace dependencies.
Complete a test booking or purchase with your replacement service before changing the domain.

Do future Squarespace blog posts appear in my HTML export?

No. The export is a snapshot of captured public pages. Publish new content in your chosen code or CMS workflow; later changes in Squarespace do not automatically update it.

Export Squarespace to HTML: galleries, content and hosting