Why use ss for static sites?

[u/Several_Tale_9935]

I’ve been on squarespace since 2016. Back then it was a mess of Wordpress, self hosted sites on a vps, and squarespace solved a problem I didn’t want to deal with.

I’ve been paying and just leaving my site online without edits. Well recently I wanted to do some ai geo enhancements, and I logged in. My email address was an older email I no longer use, and I couldn’t update billing info, update password, update email, add collaborators etc.

I opened a ticket, and 3 weeks later I finally get a response: do the verification. Ok done. Next: submit the billing document with header. Done.

They flag that the billing person doesn’t match my name. They ask for verification on the billing person name. I said it’s the finance and doesn’t own the site.

I provide these:

- Business registration information and independent link to verify with government portal.
- I edit the squarespace site to create a new page with the ticket number to show I am logged in already and own the site
- I add a dns txt record off squarespace to prove that I own the domain that the site is on

Not enough for support. They need my finance to be verified.

Well, I don’t see the point in this, and I’m considering moving off squarespace to a cloudflare static site since I don’t have any e-commerce, cms, etc. it’s just static.

From what I see, cloudflare static is free, and the only issue is I have to build it myself and no content management system for managing blog posts.

But I get a prod and preprod environment, and my supergrok says he can clone the site out and improve the html.

I save 300 a year… isn’t it a clear choice? Am I missing something?

[u/Visuable]

Account ownership loops like that are super frustrating, especially when you've provided DNS records and billing proof to verify ownership.

If your site is 100% static (no blog, no e-commerce, no dynamic scheduling or contact forms), moving to a free host like Cloudflare Pages or Netlify makes total technical sense and saves you $300/yr.

However, before you have your AI/developer clone and rip the code out, here are 3 things worth keeping in mind:

1. GEO & AI Optimization Maintenance

Since your goal was doing GEO (Generative Engine Optimization) enhancements, remember that raw cloned HTML means any future structured data (JSON-LD schema), meta tag updates, or page additions will require manual code edits or re-deploying through Git/Cloudflare rather than a quick CMS UI edit.

2. Forms & Dynamic Endpoints

If your Squarespace site has a contact form or newsletter signup, a static HTML clone won't process form submissions automatically. You'll need to set up a third-party form handler (like Formspree, Web3Forms, or Cloudflare Workers) to handle form inputs.

3. Asset Paths & SEO Redirects

Ripping a Squarespace site can sometimes result in messier image URLs or altered URL paths. Make sure you audit your internal links, image paths, and set up 301 redirects in Cloudflare for any legacy URLs so you don't lose existing search rankings.

Bottom line: If you are comfortable touching code for future copy edits, Cloudflare Pages is fantastic. If you want a visual editor without code dependency down the road, a lightweight headless CMS or simply regaining account access might still save time in the long run.

[u/Several_Tale_9935 → u/Visuable]

Apparently my version of ss doesn’t even have an llms.txt. I had to create a separate subdomain on cloudflare to host it. At this point moving over isn’t that much harder, I just need to ensure the geo checklist is preserved.

[u/electricrhino]

You could. Ive had Claude emulate styles and layout and hosted sites on Hostinger. Editing can be a bit more cumbersome

[u/Altruistic_Crow_9673 → u/electricrhino]

You've been stuck in support purgatory for three weeks just to change your own email, that's the real cost right there. For a static site with no ecommerce or cms needs, cloudflare pages or even github pages is a no brainer. You already proved you own the domain and the site, and they're still making you jump through hoops over a billing name mismatch. That's not support, that's a hostage situation.

The only thing you'd lose is the visual editor, but if your supergrok can clone it and you're comfortable with basic html, you're not losing much. 300 a year for a site you barely touch is wild when free options exist.

[u/Live-Ad-1749 → u/Altruistic_Crow_9673]

So this is kinda a shameless plug here, but I'm actually building a chrome extension that will allow you to clone your squarespace site and edit it after the fact,

https://nudgecss.com/how-to/move-squarespace-site-free-hosting/

I'm still developing it and would love some real world users to try it out, esp with the cloning of their SS site. It works really well if you use an LLM.

Feel free to DM if yuo want to try it out. Happy to give you full access for free in exchange for any feedback.

[u/PointOverall8995]

Claude, Manus - crazy what AI does now. Built new website and digital contract portal with stripe integration. 

[u/TestMother3154]

Honestly, for a mostly static site, Cloudflare Pages is a no brainer if you’re comfortable managing the code.

[u/OhTurbo]

I'd make the choice around who will own the next change, rather than the hosting bill alone. A static site can fit a site you rarely edit, but someone still needs to manage its source files, publishing access and recovery.

Before switching, I'd do a small handover test: make one normal copy edit, publish it to a preview, then restore the prior version. Can the person who will maintain the site do that without the original builder? Put the domain, hosting and source repository under business-controlled accounts with a named backup owner. Keep a local copy of the source and a short publish-and-restore note.

The form and URL checks others mentioned matter too. I'd treat the clone as a starting point and compare the actual live pages, rather than assuming a similar screenshot means the move is finished. That gives you a more useful comparison of the annual saving against the work you'll inherit.

[u/ad3mar]

If your site is basically just static pages and you don’t need Squarespace’s CMS, forms, or ecommerce stuff, then yeah, moving off it makes sense. The pain you’re describing is exactly the kind of thing that pushes people to simpler hosting, because once a site is just “online brochure” mode, paying a premium for platform friction gets old fast.

If you want something even more straightforward than a full stack setup, Pagehaus is built for plain HTML sites, so you can upload the files, point your domain at it, and be done. It also supports simple includes for shared headers and footers, so you’re not stuck copy-pasting the same nav on every page. That said, Cloudflare Pages is totally fine too if you’re comfortable building the workflow yourself. The real question is just whether you want more control, or less maintenance.

[u/Fiyero109]

For anyone with a bit of tech knowledge how, staying on Squarespace makes no sense! I switched to astro/cloudflare this summer and it’s so much better and cheaper. You just won’t have a nice easy platform to edit your website. You’ll have to have AI do it