Website & Development
Who Owns My Website? Lock-in and Access to Code, Domain and Hosting
Copy for AI
You own your website in principle, but only what’s in your name.
As the paying client, website ownership should sit with you.
In practice it depends on the contract and on whose name each account is registered under.
The verdict: a website is five separate parts, and each can end up with a different party. Secure every part in your company’s name before the first invoice.
Below: which parts exist, where lock-in arises, and what to secure so you stay free to move, renew or switch supplier.
Why this happens without bad intent
Most agencies don’t mean harm. But ownership that no one explicitly arranges often lands in the wrong name by accident.
You only notice at the worst moment: when you want to leave.
For example, say your agency stops trading or your designer stops answering.
If the accounts are in their name, your site is suddenly out of reach.
That scenario is more common than it sounds.
Our piece on a web designer who disappeared after launch walks through it.
Ownership is a fixed part of any build.
Our guide to having a B2B website built covers the rest.
What does “owning your website” actually mean?
It means you can reach every part of the site without anyone’s permission.
That covers keeping it running, changing it and moving it.
So the question has no single answer.
The five layers of a website
A website consists of at least five separate layers:
- The domain name: your address, plus the DNS settings
- Source code and design files: HTML, CSS, custom code or the platform project
- Content and CMS structure: your texts, images and page setup
- Hosting: the servers or platform subscription the site runs on
- Connected accounts: analytics, Search Console, email, forms, paid plugins and licenses
Here’s who should hold each layer:
The layers are independent
You can own the source code but have no access to the hosting.
Or have the domain in your name, while the CMS content sits in an account only the agency can reach.
Rule of thumb: true ownership means you control all five, or can reach them without obstruction.
Which part of website ownership matters most?
The domain name, because lock-in hurts most there and is easiest to avoid.
The registrant is the legal owner
A domain has a registered holder, the registrant.
That holder is legally the owner, not whoever manages it.
If your agency registers the domain “just for you” in its own name, you’re stuck there.
When you move, you need their cooperation for the transfer code. Without it, you’re going nowhere.
The simple rule for domains
Your domain sits in your company’s name, in a registrar account your company holds the login for.
Letting an agency manage it is fine.
But your organization appears as registrant and account owner.
Picking a new name? Our guide to choosing a domain name for your business covers the basics.
Your measurement history comes second
The same principle applies to your data.
Put Google Analytics and Google Search Console on an account your company owns.
Give the agency access as a user, not the other way around.
That history is hard to rebuild. Here’s what a single property holds for our own site:
Our own Search Console for customerimpact.be, last 28 days, October 2026. Lose access to the property and you lose this history.
That’s 1.21 million impressions in 28 days, tied to one property.
If the work moves, you keep the history only if the property is yours.
It’s exactly what makes the difference in a later website migration without ranking loss.
Where does website ownership lock-in sit per platform?
In poorly arranged access, not in the platform itself.
The form does differ per type of build.
It’s fair to name those differences without declaring a winner.
Open CMS such as WordPress
In theory you have everything in hand: your codebase, database and files, on hosting you choose.
The lock-in sits in the accounts around it. Check three things:
- Who has the admin login?
- Whose hosting account is it on?
- Who owns the paid plugin and theme licenses?
Without those, you own a site you can’t move.
The software itself is free and open, as the project’s homepage shows:
WordPress.org, October 2026. The code is open; the lock-in risk sits in the accounts around it.
Visual platform such as Webflow
You get ease of use and hosted infrastructure, but ownership is divided differently.
Webflow sells design, CMS and hosting as one platform:
Webflow’s homepage, October 2026. The site lives in a workspace, so that workspace should be yours.
You can export the front-end code, but only on a paid Workspace plan, not on a Site plan.
That export leaves out the CMS content, user accounts and localized pages.
Forms and site search stop working too.
Webflow’s own pricing page confirms that dynamic CMS items and pages can’t be exported (checked 4 November 2026).
So the real question is: does the project sit in a workspace in your company’s name?
Then you can hand over management without rebuilding.
Custom or headless
You usually have the most control over the code.
But you depend on documentation and on access to the repository and separate services.
Without the Git repository, environment variables and a readable handover, custom code is a black box.
Considering decoupled layers? Our explanation of how a headless CMS works shows where ownership and dependency lie.
Access decides, not technology
So the conclusion isn’t “choose platform X to avoid lock-in”.
On every platform, your access decides whether you’re free.
Which option fits depends on your team, growth plans and how often you want to change things yourself.
That’s how we approach website development: platform-independent, with the right tool per case.
Our piece on CMS vendor lock-in goes deeper.
What needs to be in the contract?
Ownership and access, in writing, before the first invoice.
Negotiating afterwards about something you’ve already paid for puts you in a weak position.
The five clauses
A good agreement doesn’t have to be long. It covers these points:
- Ownership of the delivered work. Source code, design files and content become your property after payment, not merely “licensed”.
- Accounts in your name. Domain, hosting, CMS, analytics and paid tools sit on company accounts. The agency works as a user.
- An exit clause. What you get when the collaboration ends, in what form, and within what timeframe.
- Documentation and handover. Where everything is, how you deploy, which services are connected.
- No hostage-taking in a dispute. You keep access to your live site and data, even during an invoice discussion.
For the exit clause, list what you’ll receive:
- an export of the content
- the complete codebase
- a database dump
- a list of all accounts and licenses
Our guide to a website contract and SLA covers the service side of the same agreement.
Check who’s an owner in Search Console
Search Console separates owners from users. Only property owners can add or remove users, so your company should hold at least one owner seat.
Check it under Settings, then Users and permissions:
The agency can work fine as a full user.
It can view the data but can’t manage users.
There’s room for everyone: a property allows up to 100 non-owner users, per the same Google help page.
Our experience: with us, the client owns everything: content, links and accounts. That’s how it should work with any supplier.
Good agencies don’t mind
An agency that thinks along with you has no problem with this.
Clear ownership agreements are a sign of trust.
And trust is what a good B2B relationship runs on.
Also arrange it internally. Good website governance sets out who in your own company owns the site.
It’s the same logic that decides whether visitors believe you: see building trust on your B2B website.
What should you receive at handover?
A concrete package per layer, not a promise that “everything is yours”.
Use this as a checklist when a project ends or a supplier changes.
Domain and DNS
- registrar account login in your company’s name
- an export or screenshot of every DNS record
- the renewal date and payment method
For example, say the mail records live only in the agency’s DNS panel.
Move the domain without them and email stops.
Code, design and content
- access to the Git repository, or the platform project in your workspace
- environment variables and a deploy note
- the design files in their original format
- a content export plus the media library
Watch out: a CMS export without the images is half an export. Ask for both.
Hosting and connected accounts
- hosting account owned and billed by you
- a list of every tool, with role and login owner
- paid plugin and theme licenses moved to your account
For example, say a premium plugin license sits on the agency’s account.
When they stop renewing it, updates and support stop too.
Our experience: we hear the horror stories about suppliers nobody can hold to account. We’re often the team companies call once it has gone wrong.
The fix is almost always the same: an inventory first, then accounts moved one by one.
How do you get your ownership back if it went wrong?
Start with a calm inventory, not a conflict.
Step 1: Map the five layers
List the five layers and find out, per layer, whose name and which account it sits under.
Often it isn’t so bad. It’s a matter of having access transferred, or getting yourself added as owner.
Step 2: Move the domain
Request the transfer code, also called the auth code or EPP code.
Then move the domain to a registrar account in your company’s name.
Under ICANN’s transfer rules, the registrar must give that code to the registrant within 5 calendar days.
Changing the registrant name, organization or email can lock transfers for 60 days. So plan the order:
Watch out: don’t change the registrant details right before a planned transfer. You could wait two months.
A registrar may also refuse a transfer within 60 days of the first registration or of a previous transfer, ICANN’s FAQ adds.
Step 3: Secure analytics and Search Console
While you still get cooperation, have yourself added as administrator in Google Analytics and as owner in Search Console.
Our GA4 guide explains the account structure.
Step 4: Rescue the content
Even if you can’t export the old site, you can usually retrieve the texts and images. Then you rebuild them elsewhere.
Keep regular copies anyway. Our guide to website backups shows what to store.
Step 5: Plan a rebuild properly
If a move becomes a new build, plan it properly right away so you don’t lose positions.
A well-thought-out website redesign process takes that continuity into account.
The most valuable things to lose aren’t the code, which can be rebuilt.
They’re your domain and your measurement history.
Protect those two first and the rest follows.
Frequently asked questions
Who owns my website if an agency built it?
Legally it depends on your contract and on whose name the accounts are in.
Make sure the contract transfers the code, design and content to you after payment.
Who owns my domain name?
The registered holder, the registrant. If the agency registered it in its own name, it legally holds the domain until you transfer it.
How fast can I get my domain transfer code?
Under ICANN rules for generic domains, the registrar must give the registrant the code within 5 calendar days of the request.
Can I take my Webflow site to another platform?
Partly.
The export gives you static HTML and CSS, but not the CMS content.
So you rebuild the dynamic side elsewhere.
The short summary
Owning your website means reaching five parts without obstruction: domain, code and design files, CMS content, hosting and connected accounts.
Secure your domain and analytics first, put ownership and an exit clause in writing, and arrange a clean handover.
Already worried about a web developer lock-in?
Contact us and we’ll map your five layers with you, so you know what’s yours.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.