Home / Insights / Business Growth

Business Growth

Do You Own Your Website? The Lock-In Traps in Builders, Agencies, and Platforms

Ask most small-business owners “do you own your website?” and the answer is a confident yes. Then ask who holds the domain login, who owns the design files, and whether the site could move to another host next week. The confident yes gets quieter. So, who owns my website? It depends on four separate things, and lock-in hides in each of them.

Ownership is four things, not one

“The website” is really a bundle. Check each piece on its own:

  • The domain (yourbusiness.com): registered to a person or company, the registrant.
  • The hosting: the server that runs the site, and who holds the account.
  • The code and design: the files that make the site look and work the way it does.
  • The content: your text, photos, products, blog posts, and customer data.

You can be fully in control of one and completely locked out of another. Most horror stories come from a mismatch, such as a domain registered under the agency’s name or a design that cannot leave the platform it was built on.

Trap 1: Site builders rent you the site

Wix, Squarespace, and similar builders are fine for plenty of businesses, and a cheap builder is genuinely a reasonable choice for a side project or a simple brochure. But be clear about what you are buying: access, not an asset.

Wix says so plainly in its help center: your site must run on Wix’s servers, because the platform uses proprietary technology and relies on Wix’s services to operate. Squarespace’s export options cover site content as an XML file, plus products and contacts as CSV files. Images and uploaded videos cannot be exported in bulk, only one at a time from the asset library. The page layout and design do not come with you.

In practice, leaving a builder means rebuilding. That is not sinister, but it is a cost that never appears on the pricing page. If you are on a builder, the practical step is to keep your own copies of your text, photos, product data, and customer lists.

Trap 2: The agency that registered your domain

This one is the classic. An agency or freelancer “handles everything,” including registering your domain under their own account. The site runs fine until you part ways, and then you learn you are not the registrant of your own business name.

A quick check: look up your domain in a WHOIS/RDAP lookup and see who is listed as registrant (some registrars mask this, in which case log in to your registrar and confirm the account is yours). The domain should be in an account you control, with your email as the recovery address. Domains can be transferred between registrars, but the current holder has to unlock it and release the authorization code, which is easy to get if the relationship is good and painful if it is not.

Trap 3: Paying for the design is not the same as owning it

Here is the one that surprises people. Paying someone to build your site does not automatically make you the legal owner of the design and code. Per general copyright practice summarized by legal publishers, copyright starts with the person who created the work unless it is transferred, and a transfer must be in writing and signed to be valid. Website design does not fit neatly into the statutory “work made for hire” categories, so contracts typically pair a work-for-hire clause with a written assignment as a fallback.

This is general information, not legal advice, and it is worth having a lawyer read anything important. But the practical takeaway is simple: get the ownership terms in the contract, in writing, before work starts. Look for a clause that assigns the finished work to you on final payment.

Also watch for what is excluded. Many agreements say you own “the deliverables” but the agency keeps its “proprietary framework,” “custom plugins,” or “templates.” If the site cannot run without those pieces, and they are licensed to you month to month, you have a subscription, not a site.

Trap 4: Proprietary page builders and bundled tools

Some agencies build on a page builder or a proprietary theme framework that only they have licenses for. The site looks like yours, but the layout lives inside a tool you cannot open. When the license lapses or you leave, the front end may break or turn into a wall of shortcodes.

The alternative is standard code: plain HTML, CSS, and JavaScript on a standard platform that any competent developer can pick up. It is one of the reasons we build the way we do, which we cover in template vs. hand-coded websites. Standard code on standard hosting means the next developer, whoever it is, can read it.

Trap 5: Hosting and care you can’t leave

Bundled hosting is convenient, and there is a real argument for it: one party is accountable for backups, security, and uptime. That is how our care plans work, and they are cancel-anytime. The question to ask any provider, us included, is what happens on the way out: do you get a full copy of the files and database, and how long does the handover take? A provider that answers that clearly and in writing is one you can trust with the bundle.

A 10-minute ownership audit

  1. Domain: confirm the registrant and the account are yours, and that you know the login.
  2. Hosting: confirm you can name the provider and that the account is in your name or that you have a written handover clause.
  3. Admin access: make sure you have your own administrator login to the site, not a shared one.
  4. Contract: find the ownership or IP clause and check that it assigns the work to you, with no hidden exclusions.
  5. Backups: download a full backup of files, database, and media, and store it somewhere the provider cannot reach.
  6. Dependencies: list any paid plugins, themes, or builders the site needs, and whose name the licenses are under.

If every line checks out, you own your site in the way that matters. If two or three do not, better to find out now than the week you want to leave.

What “owned” should look like

A site you truly own is standard code on standard hosting, a domain in your own registrar account, admin logins that are yours, and a contract that says so in plain English. It is portable: a different developer could take it over on Monday. Anything less is not necessarily bad, but you should know which trade-offs you accepted and what they cost you to reverse.

Want a straight answer on where your current site stands? Book a free consultation and we’ll walk through the audit with you, whether or not you end up working with us.

Do You Own Your Website? The Lock-In Traps in Builders, Agencies, and Platforms

Keep reading

More insights.