Paying for a website and owning a website are two different things. Payment is a contract question. Ownership is a copyright question, a domain-registration question, and a stack of third-party license questions — and the gap between the two is where small businesses get stranded.
The gap usually stays invisible for years. It shows up the week you decide to change developers, move hosts, or rebuild. Suddenly the domain is registered under someone else’s email, the logo exists only as a flattened JPG, and the font on your homepage is licensed to a studio you no longer work with. None of that requires bad faith from anyone. It is simply what happens by default when nobody writes the ownership terms down.
Website ownership is five separate things, not one
The first useful move is to stop thinking about “the website” as one object. It is five assets, each with its own paper trail and its own way to go missing:
- The domain name — held at a registrar, controlled by whoever is listed as the registrant.
- The hosting account — where the files and database actually live, controlled by whoever holds the billing login.
- The site itself — the theme, custom code, database, and page content.
- The brand assets — logo source files, artwork, illustrations, and the editable originals behind them.
- The licenses — fonts, stock photography, premium plugins, and anything else rented from a third party.
The paperwork for each is different, and handling four of them well does not help much if the fifth is the one holding your site hostage.
The domain is the one that hurts most
Strictly speaking, nobody owns a domain name. You hold a registration for a fixed term and renew it. What matters is one field in that registration: the registrant, the legal holder. Administrative and technical contacts are conveniences; the registrant is control.
If your developer set the domain up on their own account and put their name in the registrant field, they hold the address your business answers to. Your email may route through it. Your Google Business Profile points at it. Every backlink you have ever earned points at it.
There is also a timing trap. Since December 1, 2016, ICANN’s transfer policy has applied a 60-day lock after any change to the registrant’s name, email, or organization. The lock does not block DNS edits or renewals — only a transfer to a different registrar. It exists to give the previous registrant time to notice a hijacking, which is a sound reason for it and a bad surprise to discover during launch week. Some registrars let you opt out, but only if you ask before submitting the change.
The practical test takes two minutes: log into the registrar yourself, right now, without asking anyone for the password. If you cannot, you do not control your domain, regardless of who has been paying the renewal invoice.
Getting this right up front is what makes a clean move possible later. When Interfaith Community Services launched The ROCk, the new homelessness-response campus in Santa Fe, the build included a domain migration and a full 301 redirect map — a transition that goes smoothly precisely because registrar and hosting access sit with the organization rather than a vendor.
What copyright law actually says about your website’s code
Under United States copyright law, the person who creates a work owns the copyright in it unless a specific exception applies. A freelance designer or development shop is an independent contractor, not an employee — so by default, they own the copyright in the custom theme, the templates, the CSS, and the original artwork. Paying for the project is not the same as being assigned the rights to it.
The clause most contracts reach for is “work made for hire.” For commissioned work, that phrase has a narrow legal meaning: 17 U.S.C. § 101 lists exactly nine categories of specially ordered work that can qualify, and both parties have to sign a written agreement designating it as such before the work begins. The nine cover things like translations, compilations, instructional texts, and contributions to collective works.
Software is not on the list. Code is treated as a literary work for copyright purposes, and literary works are not among the nine — so a work-for-hire clause covering your website’s code often does not accomplish what everyone in the room assumed it did.
The clause that does work is a plain assignment of copyright — language transferring the rights in the deliverables to the client, typically effective on final payment. It is one paragraph. Ask for it in the proposal stage, when it is a formality, rather than in a dispute, when it is leverage.
Fonts are rented, and the lease is in someone’s name
Typefaces are the quietest ownership problem in branding, because a font file is licensed rather than owned. You buy permission to use it under stated conditions, and those conditions are narrower than most people expect. A desktop license lets someone install a font and set your logo in it. It generally does not include the right to self-host that font on a website — webfont licenses are sold separately, and are frequently priced in tiers by monthly page views. A studio also cannot spread one webfont license across several clients’ domains. If your brand’s typeface is licensed to your designer rather than to your business, it does not travel with you when the relationship ends.
Same logic for stock photography and premium plugins, whose license keys are tied to an account and an email address. Ask for the receipts, and check that the name on them is your business.
Do I own my website if I paid for it?
Not automatically. Paying an invoice settles the contract; it does not by itself transfer copyright, move a domain registration, or reassign a font license. In the United States, an independent contractor owns the copyright in work they create unless a signed agreement assigns it to you. A well-run project does leave the client owning the content they supplied and the custom work built for their business once the final invoice clears — but that comes from a written assignment clause and accounts registered in the client’s name, not from the payment alone.
A 30-minute ownership audit
You do not need a lawyer to find out where you stand — just half an hour and a password manager. Work through these in order.
- Log into your registrar. Confirm the registrant name and email are yours, the auto-renew is on, and the card on file is one you still have.
- Log into your host. Confirm the account is billed to your business and that you can reach the control panel, files, and database without a middleman.
- Log into WordPress as an administrator. Check that at least one administrator account belongs to someone still at your company.
- Find your logo source files. Vector originals, not just exported PNGs. If all you have is a flattened image, that is a gap worth closing while the designer who made it still remembers the project.
- Collect the license receipts. Fonts, stock images, premium plugins. Note whose name each one is in.
- Check your analytics and Search Console properties. Verify you hold owner-level access, not just view access.
Anything you cannot log into yourself is a dependency. Write it down, and fix the easy ones this month. The expensive time to find one is the week you need it gone.
What to ask for on the next project
Four lines in a proposal prevent nearly all of this: the domain is registered to the client, the hosting is billed to the client, copyright in the deliverables is assigned to the client on final payment, and third-party licenses are purchased in the client’s name. A designer planning to keep working with you has no reason to object. One who does object has told you something useful for free.
Patrick Iverson is a brand strategist and custom WordPress developer in Santa Fe, New Mexico, running an independent practice here since 2001 and building on WordPress since 2003. If you are not certain what you currently own — or you are about to sign for a new site and would rather settle the ownership terms before the work starts than after — that is a short conversation worth having early.
