Website Builder Lock-In: Easy to Get In, Hard to Get Out

I have nothing against hosted website builders. They solved a real problem: getting a decent-looking site online without hiring anyone. What bothers me is how unevenly the doors are built. The way in is wide, bright and signposted. The way out is narrow, unlit and somewhere at the back.

I learned this the practical way, by being the person a client called when they wanted to leave.

The door in

Signing up for a hosted builder is designed to be effortless, and it is. You pick a template, change the words, connect a domain and pay a monthly fee. Hosting, security and updates are handled for you. For someone who needs a site this week, that is a good deal, and I understand why millions of people take it.

The trouble is that the decision is made at the moment when leaving is the last thing on anyone’s mind. Nobody setting up their first site asks what happens in three years when the business has grown, the template feels tight and the monthly fee has crept up.

The door out

When that day comes, the answer is often written in the platform’s own help pages. You just have to go looking.

Wix is unusually direct about it. Its help article on exporting says: “In order for your site to work properly, it needs to be hosted and operated on Wix’s servers.” It adds that its architecture “does not support external hosting since it uses Wix’s proprietary technology.” In plain words, the site you built cannot be moved. You can take your domain elsewhere and point it at a new site, but the site itself stays where it is. If you leave, you rebuild.

Squarespace goes further than that, but not as far as people expect. You can export some content as an XML file in WordPress format. Its help page lists what comes with it: regular pages, one blog with its posts, text and image blocks. It also lists what does not: other page types such as store, portfolio and index pages, content in headers, footers and sidebars, more than one blog, product, video and audio blocks, drafts, style settings and custom CSS. So you can take part of the furniture, but not the house.

None of this is hidden or illegal. It is simply a consequence of how these platforms are built. Your site is not a set of files you own. It is a configuration inside someone else’s system.

Why it is built this way

I do not think anyone sits in a meeting and decides to trap customers. The lock-in comes from the architecture. A hosted builder stores your site in its own format, on its own servers, rendered by its own code. There is no standard file to hand over because there never was one.

But the business effect is the same as if it had been designed on purpose. The harder it is to leave, the less a platform has to compete to keep you. Prices can rise, features can change, and the customer’s realistic options shrink to “stay” or “start again”.

What it costs when you want out

When a client asked me to move them off a hosted builder, the job was never a transfer. It was a rebuild with a copy-and-paste phase. Every page had to be recreated, every image downloaded and uploaded again, every form rebuilt, every redirect set up by hand so that the old addresses did not break and take the search traffic with them.

That work costs money, and it is money the owner would not have spent if the site had been portable in the first place. It also explains why so many people stay on platforms they no longer like. The cost of leaving is real, and it grows with every page they add.

The question to ask before you build

I give everyone the same advice, whether or not they ever work with me. Before you build on any platform, open its help centre and search for “export”. Read what it says. Then ask yourself one question: if I wanted to leave next year, what would I take with me?

If the honest answer is “my domain and some text”, you are renting. That may still be the right choice for you, but you should know it.

The alternative I build on, and the reason it sits at the centre of everything I make, is a standard WordPress site on hosting in the owner’s name. The files, the database and the domain are theirs. They can move the whole thing to another host, or give it to another developer, without asking me or anyone else. That is what I mean when I say the site is the client’s.