"Squarespace website not converting" is a search that finds this site every so often, alongside "squarespace conversion tracking" and "conversion tracking squarespace". I suspect they're often the same person on different days. First they want to know why the site isn't working and then they realise they can't actually tell.
I don't think I've ever actually worked on a Squarespace site for a client. I've built websites in Squarespace, so I'm familiar with the platform, but they haven't been business websites. It's typically not a platform of the size that suits an experimentation programme, certainly not one that charges anywhere between £3,000 and £8,000 a month. You might be taking a few sales through it, and maybe some of you are doing great, but most Squarespace sites lack the traffic, the user base and the revenue to make that worthwhile.
So looking for Squarespace-specific advice is probably not as meaningful as looking for general advice that applies to multiple platforms, because they're really similar. Most of what follows would be the same on Wix or WordPress.
The one part that is specific to Squarespace is the tracking and that's the problem to fix first.
Step one: decide what a conversion is
On a Squarespace shop it's obvious: an order. Most Squarespace sites aren't shops though so a conversion is a form submission, a booking, a phone call, a newsletter signup, a click through to a booking platform.
Write down the one or two actions that really matter to the business or your website and everything else can follow from that.

Step two: track it
Squarespace has its own analytics panel, which is fine for traffic and sales on a shop but is pretty limited for anything else. For proper tracking most people connect Google Analytics 4, and here you've got two routes:
- The built-in integration. Squarespace has a field for your GA4 measurement ID in its settings.
- Google Tag Manager through Code Injection. This is more work, but it's a better route that lets you track form submissions, button clicks and purchases the way you want. Loves Data's guide walks through it: the Tag Manager container goes in the Header section of Code Injection, and for shops, a small script on the Order Confirmation Page section passes a transaction ID, value and currency through to a GA4 purchase event.
Code Injection isn't on every plan. Squarespace's help page lists it for Core, Plus and Advanced (so not Basic), and for "some legacy billing plans".
Beyondspace, a Squarespace specialist, says that means the old Business and Commerce plans have it but Personal does not.
For forms, the usual approach is to send people to a "thank-you" page after submitting and track views of that page as your conversion. It's crude but reliable. For bookings that happen on another platform (Acuity, a ticketing site), you'll need that platform's tracking or a cross-domain setup, and for a lot of people that's where the data fails and falls apart.
Then check it works. Submit a test enquiry, place a test order etc and watch it arrive in GA4's real-time report.
Two other things that make Squarespace numbers look worse than they are: consent banners (if people decline analytics cookies, you won't see them, which is right and proper, but means your conversion rate is calculated on a subset) and spam/bot form submissions inflating your count.
There is another option, which is cookieless analytics. I use Umami on this website, the one you’re on right now, and it’s really, really good. It gives me more accurate measurement as it's not dependent on cookie notices and it also protects your privacy.
I’m not sending your data to Google, or to any other major tech company who may or may not do things with it, sell it to somebody else, or sell access to you to somebody else. So I’m offering you a better experience, and I still get to see how my website performs, what people do on it and how they use it, without identifying anybody individually and while respecting their right to privacy.
Plausible and Simple Analytics do the same kind of job. You add any of them with a script, so on Squarespace that means Code Injection again.
Step three: find out why it isn't converting
Once you can measure, these are the usual suspects, roughly in the order I'd check them. None of them is a Squarespace problem, and they're the same on any platform.
- People can't tell what you do or what it costs. Template sites often lead with a beautiful photo and a vague headline. If the price, the area you cover or the next step isn't clear in the first screen, that's somewhere to try something.
- Your prices are unclear or misleading. Baymard's checkout research finds that of shoppers who abandoned during checkout, 40% left because extra costs (delivery, tax, fees) were too high. Show delivery costs early. In the UK, compulsory fees left out of the headline price are now illegal as well as off-putting.
- The site is slow. When people use website builders like this they tend to upload photos straight from a camera, or just whatever is saved on their hard drive. That photo is typically really, really big, because you do want high-quality product shots available to you. You can always shrink them, but it’s really hard to make them larger without ruining the quality. So they’re massive, they’re heavy and they take forever to download. Most website owners would benefit from shrinking the file before uploading it. Squarespace’s own guidance is 2,500 pixels wide and no more than 500 KB. It converts what you upload to WebP for display, so you don’t need to change the format yourself, you just need to make the file smaller. Squoosh is a free tool that does it in your browser, and your images never leave your device.
- The form asks too much. Every field that is not essential (but is "nice to have") is another reason not to complete the form. Ask what you need to know in order to reply to this person and nothing more.
- There's no reason to trust you. Real reviews, real photos of real people doing real work, a real address, how long you've been around for.
- The traffic is wrong. If most visitors arrive from searches that don't match what you sell, no amount of design will fix this.

Step four: talk to people
One advantage of not having a huge amount of traffic, whether you’ve got a very high-value product with a small audience or you’re just starting out and growing the business, is that your audience is small enough to talk to individually if you want.

Testing is a way to measure the preferences and the behaviour of a lot of people all at once, in a really sortable and measurable way. With a much smaller audience it’s really, really hard to use the same method. But what you can do is literally just talk to those people, which is out of reach for experimenters with millions of customers. It would take forever to talk to millions of people, so we don’t.
You can speak to recent customers, or to people who enquired and didn’t end up buying, and ask them a load of questions about their experience:
- What stopped you buying, or nearly stopped you?
- Who did you compare us with?
- Why did you make the decision you made in the end?
- What were you looking for that you couldn’t find?
- What information did you look up, and when you found out what we do about it, was it good enough?
- What part of what we offer isn’t good enough?
With a small audience you can get that directly. There’s no real reason to hide behind an A/B testing platform.
And then test, if you can
Squarespace has no built-in A/B testing, and with the traffic most Squarespace sites get, a proper A/B test would take months anyway.
For most of them the sensible move is to fix the obvious problems, measure for a few weeks, and compare against the same period last year.
There's more on what's possible in our guide to Squarespace CRO.
Sources
- How To Add Google Analytics 4 To Squarespace, Loves Data, updated 2 February 2025
- Using code injection, Squarespace Help Center
- Which Squarespace plans include Code Injection in 2025?, Beyondspace
- Cart abandonment rate statistics, Baymard Institute, updated 28 October 2026
- Formatting your images for display on the web, Squarespace Help Center
