Who owns your website? Probably not who you think.
You paid for it, so it's yours. That's the assumption almost every business owner makes, and under US copyright law it is usually wrong. Here's what the law actually says, what you can check in ten minutes, and what to do if someone else is holding your site.
Paying for a website does not automatically make you the owner of it. Under US copyright law the person who creates a work owns the copyright by default, and that stays true no matter how much you paid, unless there is a signed written agreement transferring it to you. Your website is also not one thing — it's four, and each is owned separately. The good news: everything below is checkable in about ten minutes, and fixable in most cases.
- The default rule is the opposite of what you'd assume
- Why "work for hire" is the wrong words for a website
- Your website is four separate things
- The "free website" trap, and how it springs
- How to check what you actually own, in ten minutes
- If you're already locked out
- The clause to look for before you hire anyone
The default rule is the opposite of what you'd assume
Here is the sentence that surprises almost everyone: under US copyright law, the person who creates a work is presumed to own it — not the person who paid for it.
That's the default. A designer builds your site, you pay the invoice in full, and unless something specific was signed, the copyright in the design, the layout, the code and the graphics stays with the designer. What you have instead is an implied, non-exclusive licence to use what was made for you.[1]
Payment alone does not transfer ownership. Legal commentary on this is blunt about it: some people believe that paying for work, without a written agreement or an employment relationship, gives them the copyright. It does not.[2]
There are exactly two ways ownership sits with the business paying instead of the person creating. Either the work was made by an employee within the scope of their job — which a hired designer is not — or there's a signed written agreement that meets some specific conditions.[2]
Most small business websites were built with an emailed quote, a deposit, and a handshake. No signed agreement, no transfer. Which means the majority of local business owners reading this technically do not own the site they think they own.
In practice this almost never comes up. The site gets built, everyone's happy, nobody thinks about copyright again. It surfaces at exactly one moment: when the relationship ends.
Why "work for hire" is the wrong words for a website
This part matters even if you did sign something, and it's where a lot of well-meaning contracts fall over.
"Work made for hire" is a specific legal term, not a general phrase. For commissioned work it only applies when the work falls into one of nine listed categories in the Copyright Act and both parties sign a written agreement saying so, executed before the work is created.[2]
Websites and logos are not on that list.
So a contract that says "this website is a work made for hire" may simply not do what it's meant to do. The instrument that actually works for a website is a copyright assignment — a clause where the creator assigns all right, title and interest in the work to you.[3]
Two more details worth knowing. Courts have consistently rejected attempts to declare work-for-hire status after the fact — you can't fix it retroactively.[2] And if your designer subcontracted part of the job to someone else without the right paperwork in place, ownership can sit with a third party you've never spoken to.[1]
A useful thing to ask. If you're getting quotes, ask whoever you're considering whether their agreement uses a work-for-hire clause or a copyright assignment. It's a small question with a revealing answer — most people in this trade have never thought about the difference.
Your website is four separate things
"Do I own my website" is really four questions, and it's common to own some of these and not others. This is why people get caught out — they check one and assume the rest.
The domain name
You don't own a domain outright — you hold a registration, renewed on a cycle. What matters is whose name and email sit in the registrant field. If your designer registered it under their own account, they control it, and that's the single most damaging thing to discover late.
The hosting
Where the site actually lives. If it's inside your designer's reseller account or a proprietary platform, you can't move it without their cooperation — and on some proprietary systems you can't move it at all, because the site doesn't exist as files you could take anywhere.
The design, code and content
The copyright question above. Photos you supplied are yours. Photos the designer licensed from a stock library may be licensed to them, for that project only — which is a quiet trap when you go to reuse an image somewhere else.
The accounts and logins
Google Business Profile, analytics, business email, any advertising accounts. These are frequently created under the agency's own login rather than added to yours — which means your customer reviews, your search data and your business email are sitting inside someone else's account.
Owning the copyright to a design does you very little good if the domain is in someone else's name. Owning the domain doesn't help if the site is trapped on a platform you can't export from. You need all four.
One honest caveat while we're here. Nobody owns everything. You will never own the server operating system, you don't own the content management system itself, and a lot of the underlying code in any modern site is open building blocks that belong to nobody in particular. That's fine and normal. What you should own is the part that's specifically yours: your domain, your content, the design and code written for you, and every account with your business's name on it.
The "free website" trap, and how it springs
This is the arrangement that produces most of the horror stories, and it's marketed as a favour.
The pitch uses phrases like "start for free," "lease to own," "low monthly payments," and often "your site will be on our proprietary platform," said as though that were a feature.[7] A business owner gets a professional-looking site with nothing due up front, bundled into a monthly marketing fee. On the surface it's a bargain.
A proprietary platform is one built by the marketing company itself. If your site is built on it, it has to be hosted there — there is nowhere to take it, because it doesn't exist as files that work anywhere else.[7]
The trap springs the moment you try to leave. The pattern reported over and over: you ask for your files and you're met with a large fee or a flat refusal. Stop paying and the site can simply be pulled, with no way to recover it.[8] Some contracts include an ownership clause saying the site becomes yours only after a certain date and certain conditions — leave before then and there's an exit fee.[7]
And it isn't hypothetical. Publicly posted contract language exists in which a vendor is named the sole owner of the URL, the domain and the website, with the client described as simply leasing it.[9] That's not a loophole someone found. That's the deal, written down, agreed to.
The tell that separates a fair monthly plan from a lease
To be fair about it: a monthly fee is not itself a warning sign. Hosting costs money, updates take time, and a maintenance plan is a normal, honest thing to sell. I sell one.
The distinction is what the monthly payment is for.
- Fine: a monthly fee for hosting, updates, security, backups and changes — on a site you already own outright, that you could take elsewhere tomorrow.
- Not fine: monthly payments toward owning the website, especially where the contract doesn't separately name hosting. That usually means you're renting space on someone's platform and the site is the hook.[8]
One question sorts it: "If I cancel next month, what happens to my website?" If the answer is "it stays up, you keep everything, here are your logins," you're fine. If it's "it comes down" or "there's a fee," you're leasing, whatever the invoice calls it.
What it actually costs you when it goes wrong
The obvious loss is the site. The expensive loss is everything attached to it. Starting again on a new domain, or rebuilding from nothing, means the search rankings and authority the old site accumulated go with it.[8] Years of being findable, gone, and rebuilt over months rather than days.
That's why this is worth ten minutes of checking today rather than discovering it on the day you want to leave.
How to check what you actually own, in ten minutes
None of this requires a lawyer. Do these four checks today.
| Check | How | What you want to see |
|---|---|---|
| Your domain | Search "ICANN lookup" and enter your domain | Your name, your business, your email as registrant. Privacy protection can hide this publicly — if so, log into the registrar and check there. |
| Your hosting | Try logging in yourself, without asking anyone | You have working credentials and the account is in your name and billed to your card. |
| Your Google profile | Sign in at google.com/business with your own account | You appear as an Owner, not a Manager. Owners can remove Managers. Managers cannot remove Owners. |
| Your agreement | Find whatever you signed and search it for "assign" | A clause assigning copyright in the deliverables to you. Not just "work for hire," and not silence. |
The Google Business Profile one catches people constantly. Being a Manager feels like access, and it is — right up until the Owner removes you. If an agency created your profile and made themselves the Owner, they hold your reviews and your local visibility, which for most local businesses is worth more than the website.
If you're already locked out
This happens more than people admit, because it's embarrassing. It shouldn't be — the arrangement was designed to make it possible.
A useful first move: separate the money question from the ownership question. If there's a genuine unpaid invoice, that's a debt, and it's resolved as a debt. It isn't a reason for anyone to hold your business's identity.
Document everything before you make contact
Current WHOIS record, every invoice and payment, every email and text, and anything showing the domain associated with your business — old business cards, ads, letterhead. ICANN's own guidance on hijacked domains emphasises documentation, including registrar correspondence, renewal notices and payment records.[5] Do this first, because it makes everything after it faster.
Go to the registrar, not to ICANN
Use ICANN Lookup to find which registrar holds the domain, then contact that registrar directly. Where registrant details were changed without authorisation, the registrar may be able to open a dispute under the Transfer Dispute Resolution Policy.[4] This is the fastest route when it works.
Know what ICANN can and can't do
ICANN is clear that it does not have contractual authority to make a registrar transfer a domain back to you — even if it was taken through unauthorised access to your account.[4] It also cannot investigate illegal activity or give legal advice.[6] A complaint to ICANN is not the lever people assume it is.
Understand where UDRP does and doesn't apply
The Uniform Domain-Name Dispute-Resolution Policy is an arbitration process, but it exists for trademark disputes. To win you must show the domain matches a mark you have rights in, that the holder has no legitimate interest, and that it was registered and used in bad faith. If your business name isn't a registered trademark, this is usually not the route.[6]
If it's still stuck, this is a lawyer's job
ICANN's own guidance lists the remaining options as reaching an agreement with the current holder, waiting for the registration to lapse, or filing a lawsuit.[6] A court order may ultimately be required. This is not the moment for a DIY approach.
The honest summary: recovery is possible but slow, and it's far more expensive than prevention ever was. Which is the entire argument for getting this right at the start, with whoever you hire next.
The clause to look for before you hire anyone
You don't need a lawyer to write your next website agreement. You need to check that four things are in it, in writing.
- The domain is registered in your name, in an account you control, with your email as the registrant contact.
- Copyright in the deliverables is assigned to you on final payment. Assigned — not licensed, and not described only as "work for hire."
- You receive every login in writing at launch, and you are the Owner of your Google Business Profile, not a Manager.
- There is no fee to leave. No transfer fee, no release fee, no charge to hand over what's already yours.
If someone won't put those four in writing, that tells you what you need to know before you've spent anything.
One disclaimer worth stating plainly: I build websites, I'm not an attorney, and nothing here is legal advice. This is general information about how ownership normally works, drawn from published legal commentary and ICANN's own documentation. If you're in an active dispute, talk to an intellectual property lawyer — ICANN says the same thing in its own guidance.
- Nicolosi, P. Who Owns My Website? Phil Nicolosi Law. Discussion of the presumption of creator ownership under US copyright law and the resulting implied non-exclusive licence.
- Sierra IP Law. Works for Hire — Who Owns the Copyrights in Your Logo or other IP. On the two statutory routes to work-for-hire status, the nine enumerated categories, the requirement that the agreement be signed before creation, and courts' rejection of retroactive designation.
- Isaboke Law. Copyright Ownership Issues with Remote Workers and Contractors. On assignment clauses as the operative instrument for commissioned work outside the nine categories.
- ICANN. About Unauthorized Transfers and Changes of Registrant. icann.org
- ICANN. Documentation is Key to Recovering Hijacked Domain Names. ICANN Blog. icann.org
- ICANN. About Lost Domain Names and Dispute Resolution Options. icann.org
- RYNO Strategic Solutions. Who Owns My Website? Understanding Website Ownership 101. On "free website" pitches, proprietary platforms and ownership-clause traps.
- Hot Lizard Designs. Do You Really Own Your Website? Three Common Ownership Traps. On sites remaining available only while hosting fees are paid, and the loss of accumulated search authority when a site is lost.
- Law Insider. Website Ownership Clause Samples. Publicly filed contract language naming a vendor as sole owner of the URL, domain and website, with the client leasing.
Find out what you own before you need to know.
Send me your domain and I'll check who it's registered to, whether your Google profile is in your control, and what you could take with you. Free, no obligation, ten minutes.
