Most owners don't think about who owns their website until the day they need something from it. The site breaks, or the domain is about to expire, and the person who built it has stopped answering. That's when they find out the domain is in the developer's name and nobody knows the password to anything.
This is fixable, and it's far easier to fix before there's a problem. This guide covers what you should own, what to put in your contract, what support to expect after launch, and what to do if your developer is already gone. It's practical guidance, not legal advice, so for anything involving a real dispute, talk to a business attorney. If you haven't hired anyone yet, our questions to ask a web developer before hiring will help you raise all of this upfront.
The 5 things you must own
"The website" isn't one thing. It's several pieces, often held in different places by different companies, and you can own some of them without owning others. Here's what to check, starting with the one that hurts most to lose.
01Your domain
This is the most important one. Your domain is your address online, and it's tied to your email, your search visibility, and every printed card and truck wrap. It should be registered to your business, in a registrar account you can log in to. If someone else holds it, you can lose the name even if everything else is in order.
02Your hosting
Hosting is where the site's files live. Being on a developer's server isn't automatically bad, since managed hosting works that way. What matters is the exit: you should be able to get a full copy of the site and move it elsewhere without anyone's permission. If you pay a host directly, the account should be in your name, with your billing details.
03Your code and design
This covers the site's code, design files, and any custom graphics made for you. It's the piece the law doesn't hand you automatically, so it needs a clause in your contract. Be aware that some parts may be licensed rather than owned, like a commercial theme or stock photos. That's normal, as long as you know which parts they are and the licenses stay with you.
04Your content
Your text, photos, logo, customer testimonials, and any form submissions or customer data belong to your business. Keep your own originals somewhere outside the website. Content that exists only inside a site you can't log in to is much harder to reuse than people expect.
05Your accounts
Google Analytics, Search Console, Google Business Profile, your email provider, your domain's DNS, and any payment or booking tools all need to be owned by you. Your developer can be added as a user, and removed when the work is done. Years of analytics history and a verified business listing are hard to replace if they sit in someone else's account.
Your platform affects this too. On a builder like Wix or Squarespace, you can own your domain and your content, but the site itself generally can't be moved elsewhere as a working copy. That's not a reason to avoid builders, just something to know going in. Our guide to custom vs template websites covers that choice.
Ownership clauses for your contract
Paying the invoice doesn't by itself make the work yours. In the US, copyright in commissioned code and design generally stays with the person or company who created it unless a signed agreement transfers it. Most reasonable developers will happily agree to a transfer, but it has to be written down. Here's what to look for, in plain language, and your attorney can turn it into the right wording.
Assignment of rights
A statement that on final payment, all rights to the custom code, design, and content created for the project transfer to your business. Look for an actual transfer, not just permission to use the site.
Third-party components
A list of anything licensed from someone else, such as themes, plugins, fonts, and stock images, along with who holds each license and who pays to renew it.
Accounts in your name
A requirement that the domain, hosting, analytics, and other project accounts are registered to your business, or transferred to it by a named date.
Handoff deliverables
What you'll receive at the end: a complete copy of the site files, a list of accounts, and access to everything. Tie it to the final payment so it's not an afterthought.
Warranty period
How long the developer will fix defects in the delivered work at no charge, and what counts as a defect. If it's not in writing, assume it doesn't exist.
What happens if either side walks away
How unfinished work is paid for and handed over if the project ends early. This is the clause people skip, and the one that matters most when things go wrong.
A common and fair arrangement is that ownership transfers on final payment. A developer who won't commit to any transfer at all, or who gets vague when you ask, is telling you something. For more on weighing the proposals themselves, see how to compare website quotes.
After launch: warranty vs support
A lot of post-launch arguments come from one misunderstanding: the owner assumes the developer will keep the site working forever, and the developer considers the job done at launch. These are really two separate things, and it helps to agree on both before the project starts.
| Warranty | Support / maintenance | |
|---|---|---|
| What it is | A promise that the delivered work functions as agreed | Ongoing paid work that keeps the site healthy |
| When it applies | A limited period after launch | Month to month, or as long as the agreement runs |
| Typical example | The contact form never sent any emails | Installing updates, running backups, editing a page |
| New features | Not covered | Sometimes included, usually billed separately |
| What to get in writing | Length of the period and what counts as a defect | Scope, response times, and how to cancel |
Websites do break after launch without anyone doing anything wrong: software needs updates, third-party tools change, and a browser update can expose an old problem. So when a site breaks months later, it's usually a support issue, not a warranty one. The thing to avoid is having no plan at all. Someone needs to be responsible, whether that's you, your developer, or a care plan. For what that work involves and how to budget for it, see our breakdown of website maintenance costs.
Developer disappeared? Recovery steps
If you're reading this because it has already happened, don't panic, and don't start changing things yet. The order matters here: protect what can be lost first, then collect your evidence, and only then start reclaiming accounts.
- 01
Check what's about to expire
Run your domain through ICANN's lookup tool at lookup.icann.org and note the expiration date. An expired domain can take the website and email down together, and it's the one problem with a hard deadline, so it comes first. If you can identify the hosting company, check whether its bill is current too.
- 02
Build your paper trail
Search your email for the developer's name, your domain, and words like "invoice," "hosting," and "login." Gather your contract, invoices, and proof of payment, plus your business registration documents. Registrars and hosts will want evidence that you're the rightful owner, and you'll be asked for it repeatedly.
- 03
Save a copy of the site now
Before anything changes, save what's visible while it's still online. A site-copy tool can capture the pages, and the Internet Archive's Wayback Machine may already have older versions. This won't give you a working back end, but your text and images will be safe, and it gives you a reference for any rebuild.
- 04
Make one clear final request
Send a short, polite written message to every address you have: you need the logins, the domain transferred, and the site files by a specific date. Keep the tone neutral. People do go quiet because of illness, a closed business, or simple embarrassment, and a calm note often gets a better response than a threat. It also documents that you tried.
- 05
Go to the registrar and host directly
Contact the companies themselves and ask about their account recovery process. Each has its own, and results depend on whose name is on the account. If you're listed as the registrant, you're in a strong position. If the developer is listed and won't respond, ICANN's registrant resources explain the options, and you may need legal help.
- 06
Reclaim the listings and tools you can
Google Business Profile has a process for requesting ownership of a listing someone else manages. Search Console can be verified again through your domain once you control DNS. If an old analytics account can't be recovered, start a new one today. You'll lose the history, but every week without tracking is lost too.
- 07
Decide: repair or rebuild
If you've got the files and the domain, a new developer can usually take over. If you've only got the domain, you can still point it to a new site. Have someone review what's there before you pay for repairs, because an old, unmaintained site can cost more to rescue than to replace. Our guide on when to redesign can help you make that call.
One caution: be careful when a stranger offers to "recover" your site or domain for a fee, especially if they contacted you first. Only share logins with someone you've checked out, and change those passwords afterward. If you're picking a replacement, our comparison of freelancers, agencies, and DIY covers who to trust with the job. And if the rebuild route looks more sensible, see when it's time to redesign.
The handoff checklist
Use this at the end of a new project, or run through it today with your current site. Anything you can't check off is worth raising now, while your developer is still answering emails. For the full list of what a project should deliver, see what's included in a professional website.
- 01The domain is registered to your business, and you've logged in to the registrar yourself.
- 02Auto-renew is on, using a current card and an email address that won't change.
- 03You have an owner or admin login for hosting, or a written process for getting a full site copy.
- 04You've received a complete copy of the site files, and you've confirmed it opens.
- 05Design files, logos, and original images are stored somewhere you control.
- 06You have a list of third-party licenses, with renewal dates and who pays for them.
- 07Google Analytics, Search Console, and Google Business Profile list you as owner.
- 08Business email is on an account you control, not one tied to the developer.
- 09Passwords live in your own password manager, with two-factor authentication on key accounts.
- 10You know where backups are stored, and how to request a restore.
- 11You have the contract, warranty terms, and the name of who to contact when something breaks.
- 12Once support ends, the developer's access is reduced or removed.
How we handle ownership
At Nous Frame, you own the code and the accounts. We build custom, hand-coded sites with no templates or page builders, so there's no proprietary builder holding your site in place. Hosting and maintenance are separate care plans, so you can see exactly what you're paying for after launch.
If you've inherited a site you can't get into, or you just want to know where you stand, send us the address and tell us what you've got access to. We'll tell you plainly what's recoverable and what we'd do next.
Frequently asked questions
Who legally owns my website if I paid a developer to build it?
Paying for a website doesn't automatically transfer ownership of everything in it. In the US, copyright in custom code and design generally starts with whoever created it, and a freelancer or agency usually keeps it unless a signed written agreement assigns it to you. That's why the contract matters. For your specific situation, especially if there's a dispute, ask a business attorney.
How do I find out who controls my domain?
Look up your domain with ICANN's free lookup tool at lookup.icann.org. It shows the registrar, the expiration date, and sometimes the registrant, although contact details are often hidden for privacy. The real test is simple: can you log in to the registrar account yourself and see the domain listed? If you can't, treat it as a problem to fix now, not later.
What do I do if my web developer disappeared?
Start by checking that the site and domain aren't about to expire, then search old emails and invoices for the accounts involved. Save a copy of the live site, and try a final written request to the developer. After that, go to the registrar and hosting company directly with proof of your business identity and ask about their account recovery process. If you can't recover the site files, the live site can usually be used as a reference for a rebuild.
What's the difference between a website warranty and a maintenance plan?
A warranty covers defects in the work you paid for, for a limited period after launch: a form that never worked, a layout that breaks on phones. A maintenance plan is ongoing paid work that keeps the site healthy afterward: updates, backups, monitoring, and edits. A warranty doesn't cover new features, and a maintenance plan shouldn't be billed to fix something that was delivered broken.
Can a developer hold my website hostage?
They can make it very difficult if the domain, hosting, or code sits in accounts only they control, and whether they're entitled to withhold anything depends on your contract and any unpaid invoices. Don't escalate first: get what you can in writing, and contact the registrar and host. If the developer refuses, or the domain is registered in their name, it's worth talking to a business attorney.
Locked out of your own website, or want one you'll actually own? Tell us what's going on and we'll give you a straight answer.