Website ownership is not one thing. It’s four separate things that most business owners treat as a single topic — and the gap between them is where agencies build dependencies and clients get stuck.
Domain, hosting, code, and content: you need to own or fully control all four.
The Four Layers of Website Ownership
1. The domain name — yourcompany.com. Registered with a domain registrar (GoDaddy, Namecheap, Cloudflare, Google Domains). Whoever controls the registrar account controls the domain. This is non-negotiable: it must be in your name, in an account you access directly.
2. The hosting account — the server where your site files live. Whoever owns the hosting account can delete your site, restrict access, and control what gets deployed. Your hosting account should be in your name. The agency can have access to do their work, but they shouldn’t own the account.
3. The code and files — the WordPress theme, plugin files, custom code, images, and database. Legally, this is where ownership gets complicated. Under default US copyright law, code is owned by its creator unless a contract explicitly assigns it to you. If there’s no IP assignment clause in your contract, you may not legally own the code even if you’ve paid for it.
4. The content — text, images, data in your database, blog posts. Usually yours. But content stored in a proprietary format (like page builder blocks) is technically portable only as far as the tool itself allows.
Most business owners think they own their website because they paid for it. Paying for work doesn’t transfer ownership under copyright law. The contract has to say so.
How to Check What You Actually Own Right Now
Start with the domain. Go to a WHOIS lookup tool — ICANN’s at lookup.icann.org is reliable — and enter your domain. The registrant name should be your name or your company’s name. If it says your agency’s name, you don’t control it.
Next, check the hosting. Can you log in directly to your hosting provider’s control panel? Do you know who the hosting account is registered to? If your login goes through the agency, and the account is in their name, you’re a tenant, not an owner.
For code ownership, read your original contract. Look for an “intellectual property” or “ownership” clause. Does it say the code transfers to you on payment? Does it say anything at all? Silence on this point is not neutral — it defaults to the creator owning the work.
For content, this is usually fine. Text and images you provided are yours. Concern arises when content is stored in a proprietary block format that makes export difficult without the original tool.
Run an audit before you assume. Honest can give you a technical read on your site’s architecture — including flags for proprietary tooling that might create exit friction — without involving your current agency.
The Most Common Ownership Problems
Domain in the agency’s registrar account. Common with agencies that “handle everything” at setup. Ask for the transfer auth code (EPP code) and move your domain to your own registrar account. Any competent agency will help you do this without resistance. If there’s resistance, you’ve identified the problem.
Hosting account owned by the agency. Ask for the login credentials to the hosting account itself — not just FTP access to the files. If they won’t provide account-level access, the account is theirs. Start planning a migration.
No IP assignment in the contract. This is the hardest one to fix retroactively. You can ask the agency to sign a simple IP assignment document now. Most will agree because it costs them nothing if the relationship is in good standing. If they refuse, consult a contracts attorney.
Page builder lock-in. Your content is technically accessible but structurally dependent on the builder. This isn’t theft — it’s a tool limitation. But it means a clean migration requires rebuilding the page structure, not just exporting the content. Factor that into any future website cost estimate.
What Full Ownership Looks Like in Practice
Maria ran a regional landscaping company. When she hired her original agency in 2019, she hadn’t asked about ownership. The agency registered her domain, set up hosting in their account, and built the site with a page builder. In 2022, the agency raised their monthly retainer from $150 to $350. When Maria wanted to move to a different developer, she discovered:
- Her domain was registered under the agency’s GoDaddy account
- Her hosting was on the agency’s shared server
- Her site used a proprietary theme that the agency had built for multiple clients
Getting her files took three months of back-and-forth and a $600 “transfer fee” she paid to avoid further delay. The new build cost $8,500 because the old site wasn’t portable.
That’s what a failure of ownership documentation costs in real terms. The fix — four contract clauses and two account registrations in her name — would have taken an extra 20 minutes at the beginning of the project.
All custom WordPress development and WooCommerce builds at Designodin include full code and file transfer as a standard deliverable. The client gets everything: theme files, plugin files, database export, and all account credentials. No transfer fee. No dependency on us after launch.
How to Document Ownership Before Problems Start
If you’re starting a new web project, make sure these items are in place before launch:
- Domain registered in your name — or transfer it to your registrar account immediately after launch
- Hosting account in your name — agency can have access, not ownership
- IP assignment clause in the contract — explicit, not implied
- Admin credentials delivered at launch — WordPress admin, hosting control panel, domain registrar
- Files deliverable confirmed — theme files, plugins, database export, design files
If you’re reviewing an existing site, run through that checklist now. Don’t wait for a disagreement to discover the gaps.
What to Do If You Don’t Own Your Site
First, get the current state in writing. Email your agency and ask directly: who owns the domain registration, who owns the hosting account, and what are the terms for receiving all source files? An email creates a record.
If the answers reveal ownership problems, your options are:
- Negotiate a clean transfer now, before any relationship strain
- Commission a rebuild with proper ownership documentation
- If there’s a legal dispute about IP, consult a contracts attorney — an hour of their time costs less than a contested migration
The goal is to be in a position where losing your agency relationship — for any reason — doesn’t mean losing your website.
FAQ
If I built my own WordPress site, do I automatically own everything? Yes, if you used self-hosted WordPress (wordpress.org) on your own hosting account, you own the installation, the theme, and the content. The only exception is themes or plugins that have their own license restrictions, but those govern usage terms, not ownership of the site itself.
Does WordPress.com hosting create ownership issues? WordPress.com (not .org) is a hosted platform with usage terms that limit your control. If you’re on a paid plan, you can export your content. But the platform itself can change terms, suspend accounts, or restrict functionality. Self-hosted WordPress (.org) on your own hosting is the clean ownership path.
What’s the difference between a “license” and owning code? Ownership means you can do anything with the code — modify it, sell it, give it away, hire anyone to maintain it. A license grants you specific permissions to use the code under defined conditions. Proprietary licenses often restrict modification, redistribution, or use outside the original context. For a business website, you want ownership, not a license.
Can an agency legally put your site in their portfolio without permission? It depends on the contract. Many agency contracts include a clause granting the agency portfolio rights — the ability to display the work in their own marketing. This is standard practice. If you want to prevent it, negotiate that clause out before signing. After the fact, you’d need the agency’s agreement to remove it.
What happens to my WordPress site if the agency that built it goes out of business? If you own the domain and hosting accounts, nothing. The site continues to operate independent of the agency. If the agency owned your domain or hosting, you’d need to act quickly to recover access through the registrar or hosting provider’s account recovery process.
How do I transfer a domain if the agency won’t help? If the domain is in your name at their registrar account and they won’t release the auth code, contact the registrar’s support directly. They may be able to help if you can verify your identity as the registrant. If the domain is registered in the agency’s name, you’d need to initiate an ICANN dispute process or escalate through legal channels.