Wix and Squarespace SEO: where the platform stops helping

Builder sites we take over almost always have their SEO settings filled in correctly. The ceiling is real, but it sits somewhere else entirely, and plenty of businesses never reach it.

On this page

When a business hands us a site built on Wix or Squarespace, the first thing we do is go through the search settings. And they're almost always fine. Titles written, descriptions written, alt text present more often than not, sitemap generating, HTTPS on, redirects in place from the last time someone changed a page name.

That surprised me the first few times. The received wisdom is that these platforms are bad at SEO, and if that were still true you'd expect the settings panel to be empty or missing. It isn't. Both platforms have spent years closing that gap, and the version of the complaint that was fair in about 2016 isn't the one to repeat now.

So the ceiling is real, but it isn't where most people point. Here's where we actually run into it.

Weight you can't take off

The clearest limit is speed on a phone, and it's a limit of a particular kind: you can't remove what you didn't add.

A builder template arrives carrying the machinery that makes the editor work. Animation libraries, layout scripts, font loading, the drag-and-drop plumbing. Most of it runs whether your page uses it or not, and none of it is yours to delete. You can compress your images and trim your sections and you should, but there's a floor underneath that, and on a mid-range Android phone on patchy reception that floor is where a lot of sites sit.

Google's Core Web Vitals are the measurement, and they're not the deciding factor in ranking that people sometimes claim. They matter more for the person deciding whether to wait, which we went through in what a slow site costs you. Either way, if the slow part of your page is the template rather than your content, you've found something you can't fix from inside the platform.

Addresses that don't want to move

Builders make some decisions early and hold onto them. Collection and blog URLs tend to sit under a fixed prefix. Changing a page's address later is possible on both platforms, but it comes with the usual cost of moving anything on the web, and the tooling for handling that at scale is thinner than it looks.

For a fifteen page business site this never comes up. For a site trying to build out service pages crossed with locations, where you want a structure that reads sensibly and links properly, it becomes a daily irritation. The structure ends up shaped by what the platform allows rather than what your business actually sells, and that's the sort of constraint you only notice a year in.

Markup beyond the built-in types

Both platforms output structured data for the obvious things: articles, products, events, local business details. That covers most of what most sites need.

Past that you're relying on code injection, which is supported but sits outside the editor, and which nobody else in the business can maintain. We've picked up a couple of sites where a previous developer had bolted extra markup on that way, and it had drifted out of sync with the visible page months earlier. Markup that contradicts the page is worse than no markup. Google's guidance on JavaScript and search is the polite version of the same point: anything injected after the fact is one more thing that has to survive a render.

The labour of many similar pages

This is the one that decides it for most of the businesses we work with.

If your search strategy needs forty pages that share a structure but differ in content, a builder makes you assemble each one by hand in a visual editor. It's not that you can't. It's that you won't, not consistently, not at eleven at night, and the pages that don't get made are the ones that would have earned the enquiries.

On a custom build those pages come from content files with a shared layout, so making the forty-first is a five minute job. That difference sounds technical and is entirely practical: it changes how much you actually publish.

What limits do Wix and Squarespace publish for redirects and code?

Both platforms publish limits that matter for a site with many pages or a move to another platform. The table records what each help page says, as at November 2026.

LimitWixSquarespace
Redirects"A maximum of 5,000 redirects per Wix site."URL mappings field is capped at 400 KB, "usually around 2500 redirect lines", processed from top to bottom
Redirecting the homepageNot possible with the URL Redirect Manager. You can redirect one domain to anotherNot possible to redirect away from the homepage path "/". You can redirect to it
Redirect types301301 and 302
URL changesWix automatically creates a 301 redirect when you update a page's URL slug, but not for Wix Blog pages, which need a manual redirectSet manually in URL mappings
Custom codePossible, outside the visual editorCode injection is available on the Core, Plus and Advanced plans and some legacy plans. Squarespace support will not help add or troubleshoot custom code
SourceWix: set up a 301 redirectSquarespace URL mappings and code injection

A 5,000 or roughly 2,500 line cap is plenty for a fifteen page site and can bite on a site that has published hundreds of pages and then moves. The practical limit most owners hit first is the one in the earlier sections: you cannot remove the platform's own scripts, and structured data past the built-in types depends on code you maintain yourself.

What does moving a site off Wix look like, step by step?

Moving off Wix is mostly a matter of order: build and test the new site on a temporary address, copy the DNS records you need to keep, change the name servers at the registrar, then check forms, email and the secure padlock on the real domain. A recent move for a builder took one afternoon of switching, and the one real obstacle was a leftover DNS record.

  1. Find where the domain is registered and where its name servers point. For that builder the domain was registered at GoDaddy but its name servers pointed at Wix, so Wix answered every DNS question about it. Those are two accounts, and changing a setting inside Wix does nothing at the registrar. Check that DNSSEC is off at the registrar before the switch, because if it is on and the new name servers do not carry matching signing keys, the domain can fail to resolve for validating resolvers. Who actually owns your website covers how to find the registrant.
  2. Build and test the new site on a temporary address. The live domain does not change while you test. Test the quote form, the rating badge and the map, because a site that only looks right is not ready. Why contact form emails land in spam or never arrive explains why we test that the form delivers every time.
  3. Create the new DNS zone and decide which records to keep. For this domain the records worth keeping were the five Google mail (MX) records, the SPF text record and two Google site verification records. The mail records matter most because they are why the business's email arrives. The imported records that pointed at Wix, three A records on the main domain and a CNAME for www, had to go. Attaching the new site's custom domain failed with a conflict error until we deleted them, because the platform will not point a domain at two places at once.
  4. Change the name servers at the registrar. At GoDaddy we replaced the two Wix name servers with the two Cloudflare ones, which is the only change the registrar needs. The zone went active shortly after and the certificate was issued about six minutes later. Do not announce a move the instant the name servers change, since a visitor would see a browser warning until the certificate exists.
  5. Expect two sites for a while. Straight after the switch some resolvers, including our own machine and Google's public resolver, still answered with Wix's addresses. DNS answers are cached for a period set by the old records, and nothing clears every cache. You can still check the new site by requesting the page directly from the new host's address with the domain name attached. Leave the old site running for a couple of days. We learned the cost of removing the old target early on a later move, when a client on stale DNS saw an error page, written up in what to do when a host fails.
  6. Test the form on the real domain. Route enquiries to your own inbox first, confirm the success message and that the email service accepted the message, then change the delivery address to the client's inbox. That change caught us out: the platform builds the site into a generated configuration, and editing the settings file and redeploying shipped the old value, sending enquiries to the wrong inbox for three deploys until we ran a full rebuild. Settings that live outside the code, such as where enquiries go, are the first thing to check after any move.

Wix ranked the site for its pages, so the new URLs need to match or redirect. That move was a full rebuild with new service and suburb pages, and the advice for it is in redesigning your website without losing your rankings.

When the builder is the right answer

Plenty of times, honestly.

If you've got a handful of pages, you're not fighting anyone for search traffic, most of your work comes through referrals or your Google Business Profile, and you want to change your own opening hours on a Sunday, a builder does that job well and you should keep it. Moving off one costs money and time, and if search isn't where your customers come from, you'd be buying something you don't need. We've told people exactly that and left them where they were.

What tips the balance is usually one of three things. Search has become a real channel and you're stuck behind competitors who publish more. The site has grown past what the editor handles comfortably. Or the mobile speed has become embarrassing enough that you can feel it in the enquiry numbers.

Two things people blame on the platform that aren't the platform

Not being in Google at all is almost never a builder limitation. It's usually a setting or a page that never earned its place, which is the whole of that other post and worth ruling out before you conclude anything about your platform.

And thin content is thin content anywhere. Moving five short pages onto a faster stack gives you five short pages that load quickly. The rebuild raises your ceiling, it doesn't write your service pages for you, and anyone selling it as a ranking fix on its own is overpromising.

This week

Take the page that brings you the most enquiries, run it through PageSpeed Insights on the mobile setting, and look at what's actually loading. If the heavy items are your photos and your text, that's yours to fix and you can do it inside the platform this afternoon. If the bulk of it is scripts you never chose, that's the ceiling, and now you know where it sits.

If you'd rather have someone go through it properly, what a site audit covers explains the full check, and we'll do one for free whatever you're built on.

Common questions

Are Wix and Squarespace bad for SEO?
Not in the way people often claim. Both now handle titles, descriptions, alt text, sitemaps, HTTPS and redirects, and builder sites usually have those settings filled in correctly.
What are the SEO limitations of Wix and Squarespace?
Template code you cannot remove that slows pages on mobile, URL structures that are hard to change later, structured data limited to built-in types, and the manual work of building many similar pages one at a time in a visual editor.
Why is my Wix or Squarespace site slow on mobile?
Builder templates carry the scripts that make the editor work, such as animation libraries and layout code, and most of it runs whether your page uses it or not. You can compress images and trim sections, but there is a floor you cannot get under from inside the platform.
Should I move my website off Wix or Squarespace?
Not if you have a handful of pages, get most work through referrals or your Google Business Profile, and are not competing for search traffic. Moving makes sense when search becomes a real channel, the site outgrows the editor, or mobile speed is costing enquiries.
Will moving off a website builder improve my rankings?
Not on its own. Thin content stays thin on any platform, and a rebuild raises the ceiling without writing your service pages for you.
How can I tell if my website builder is holding back my SEO?
Run your top enquiry page through PageSpeed Insights on mobile and look at what is loading. If the weight is your photos and text you can fix it inside the platform, but if it is mostly scripts you never chose, you have hit the ceiling.

Want a website that turns readers into customers?

A custom site, hosting and upkeep for one monthly fee, with your leads and Google results in a dashboard you can check any time.