I ran an SEO audit on a jewellery store last week. Beautiful products. Wonderful photography. A brand story that would make you want to buy something on the spot. The site looked professional, polished, well-designed.
It scored 31 on Google's performance test.
Not out of 50. Out of 100. And the owner had no idea there was a problem, because from her perspective, the website looked great. It loaded fine on her fast office Wi-Fi. Her customers said they liked the design. Everything seemed to be working.
But it was built on Squarespace. And that, right there, was the problem.
The numbers nobody shows you
There is this notion -- quite widespread, actually -- that website builders have "gotten good enough" for business use. Wix runs television commercials. Squarespace sponsors every podcast. GoDaddy has been around so long it feels like infrastructure. And the pitch is always the same: you don't need a developer, you don't need to spend thousands, just drag and drop and you are online.
What they do not mention is what happens after you publish.
DebugBear ran a performance benchmark on default sites built with major website builders. The results are, let's say, illuminating. Squarespace scored 31 on mobile Lighthouse with an LCP (Largest Contentful Paint -- basically how long until the page looks loaded) of 8.79 seconds. Weebly scored 39. GoDaddy came in at 63. Wix managed 72, which sounds acceptable until you realize that a properly built custom site routinely scores above 90 with an LCP under 2 seconds.
Why does this matter? Because Google has been quite explicit about it. Page speed is a ranking factor. Core Web Vitals are a ranking factor. And according to Google's own research, when a page takes 5 seconds to load instead of 1, the probability that someone leaves before seeing anything increases by 90 percent. Each additional second in that first five-second window reduces conversions by roughly 4.4 percent.
The average page that ranks on page one of Google loads in 1.65 seconds. Your Squarespace site takes 8.79. One does not need a mathematics degree to see the problem here.
But the real issue isn't Google anymore
Here is where this becomes more than just another "speed matters" article. Because the truth is, Google can actually handle website builders reasonably well. Google uses a headless Chromium browser to render JavaScript, which means it can see your content even when it is loaded dynamically through client-side code. It has been doing this for years. Google, in this regard, is sophisticated.
ChatGPT is not. Perplexity is not. Claude is not. Google's own AI Overviews work differently from traditional search.
And this is the part that should genuinely concern you.
AI search tools -- the ones that an increasing number of people use every day to find businesses, compare services, get recommendations -- do not render JavaScript. GPTBot, the crawler that feeds ChatGPT's search feature, works more or less like a curl request. It fetches the raw HTML and reads whatever it finds there. It does not execute scripts. It does not wait for your Wix page to finish loading its 484 kilobytes of JavaScript across 66 HTTP requests.
What does it see instead? Often, very little. A loading spinner. An empty div. Perhaps some meta tags if you are fortunate.
Your product descriptions, your service pages, your pricing information, your reviews, your carefully written about page -- if any of this content is injected into the page via JavaScript (and on most builder platforms, it is), then AI crawlers simply cannot see it. Your website, as far as ChatGPT and Perplexity are concerned, might as well not exist.
This is not a theoretical concern. We have audited dozens of builder sites for AI search visibility over the past few months. The pattern is consistent. Sites built on Wix, Squarespace, and similar platforms score dramatically lower on GEO (Generative Engine Optimization) readiness than sites built with server-rendered HTML. The content is there for human visitors, but it is invisible to the machines that are increasingly deciding which businesses get recommended.
The code bloat problem nobody talks about
There is something almost absurd about how website builders generate code. When you add a simple text paragraph to a Wix page, the platform does not just render a paragraph tag. It loads the CSS and JavaScript capable of handling a video background, an image slider, a contact form, an animation sequence, and a dozen other features -- all at once, whether you use them or not.
This is the architectural trade-off that makes drag-and-drop possible. The builder does not know in advance which features you will use, so it loads everything preemptively. The result is a page that carries the weight of every possible widget even when it displays nothing more than your business name and phone number.
A custom-built page with the same content might weigh 50 to 100 kilobytes. The builder version weighs 800 to 1,000 kilobytes. Ten times heavier, for the same information. And every kilobyte adds latency, especially on mobile connections, which is where more than 60 percent of web traffic comes from now.
You cannot optimize this away. You cannot install a speed plugin. You cannot compress what the builder insists on loading. The bloat is structural.
The SEO controls you don't have
Speed is one dimension, but there are others that are less visible and equally damaging.
Robots.txt is the file that tells search engine crawlers how to navigate your site. On some builder plans, you cannot edit it at all. Squarespace locks certain SEO configuration files for what they call "security reasons." If Google or an AI crawler is doing something counterproductive on your site -- crawling pages you do not want indexed, ignoring pages you do -- you may not have the ability to fix it.
Schema markup is the structured data that helps search engines understand what your content actually is. Is this page a product? A service? A local business? An FAQ? Schema is how you tell Google and AI systems the answer. Most website builders offer limited schema support at best. You cannot implement custom schema types, you cannot add organization-level structured data, you cannot create the kind of rich, machine-readable content that AI systems increasingly depend on for generating citations and recommendations.
Internal linking -- the architecture of how your pages connect to each other -- is another area where builders impose constraints. You have limited control over breadcrumbs, no ability to create programmatic internal links, and the site structure is often flat when it should be hierarchical. For SEO, site architecture matters enormously. For AI search, where crawlers follow links to understand relationships between topics and build entity graphs, it matters even more.
These are not obscure technical details. They are the mechanisms through which search engines -- both traditional and AI-powered -- decide whether your site is authoritative, well-organized, and worth recommending. Losing control over them is not a minor inconvenience. It is a competitive disadvantage that compounds over time.
The cost illusion
The marketing for website builders is quite clever in this respect. Twelve dollars per month. Twenty-five dollars per month for the "business" plan. Forty dollars if you want e-commerce. Compared to hiring a web developer who charges several thousand dollars, the economics seem obvious.
But there is a longer calculation that people rarely do.
Over three years, a $25/month builder plan costs $900. Add the custom domain, the business email, the SSL certificate that is not included in the base plan, the premium templates, the apps and integrations you need -- and you are closer to $1,500 or $2,000. Over five years, you are approaching the cost of a professional website.
Except the professional website loads in 1.5 seconds instead of 8. It appears in AI search results. It gives you full control over your SEO. It does not lock your content in a proprietary format that you cannot export if you decide to leave.
And that last point -- the leaving part -- is where the real cost hides. Because when you eventually outgrow a website builder (and businesses that grow do outgrow them), you do not get to take your site with you. Wix pages are not standard HTML files you can move to another host. Squarespace designs do not export to WordPress. You are rebuilding from zero, and the time and money you invested in the builder platform does not transfer. Industry estimates put the switching cost at 150 to 200 percent of what you were paying annually -- effectively an exit tax for wanting something better.
When builders actually make sense
It would not be honest to pretend that website builders have no legitimate use. They do.
If you are testing a business idea and need a landing page up this afternoon, a builder is fine. If you run a hobby blog and traffic is not a concern, builders work perfectly well. If you need a simple portfolio site to show at networking events, the convenience is real and the SEO limitations are irrelevant.
The problem is not that website builders exist. The problem is that serious businesses -- companies that depend on being found online, that compete for customers in their market, that need their website to actually generate leads and revenue -- are using tools designed for casual use and expecting professional results.
A jewellery store competing against other jewellery stores in Google and ChatGPT search. A law firm trying to attract clients who ask Perplexity for recommendations. A plumbing company that needs to appear when someone searches "plumber near me" on their phone. These businesses need every advantage they can get, and a website builder is actively taking advantages away.
What to do instead
The alternative does not have to be expensive or complicated. A well-built WordPress site on proper hosting (not WordPress.com, which has its own set of builder-like limitations) gives you full control over performance, SEO, schema markup, and server-rendered HTML that AI crawlers can actually read. The initial investment is higher, but the ongoing cost is often lower and the ceiling for performance and visibility is dramatically higher.
If your budget allows it, a custom-built site using modern frameworks with server-side rendering is the gold standard. Fast, lightweight, fully optimized for both Google and AI search, and completely under your control.
The middle ground -- and this works for many businesses -- is a headless CMS with a simple static frontend. The content management is still user-friendly, but the output is clean, fast HTML that scores 95+ on Lighthouse and is fully visible to every crawler on the internet.
Whatever you choose, the first step is understanding where you stand right now. Run your website through a performance test. Check your AI search visibility score. Look at what crawlers actually see when they visit your pages. The numbers might surprise you, and not in a pleasant way.
Because the competition for online visibility is not getting easier. Google is showing fewer organic results. AI search tools are becoming a primary discovery channel. And the businesses that will thrive are the ones whose websites are built to perform -- not just to look good on a laptop screen over fast Wi-Fi.