You paid for a website, it launched, and customers can find it. Then you ask for the domain login or a copy of the files and discover that everything sits inside your developer’s account. Suddenly, a routine update or change of provider feels like asking permission to use your own business.

So, who owns your website after it’s built? The honest answer is not one person automatically owns every part of a website. A site is a bundle of assets, accounts, contracts, and licenses. Your domain registration, custom code, written content, photographs, hosting account, software, and analytics can all have different owners or users.

For most small businesses, the practical goal is straightforward: your company should control the accounts and original assets it needs to operate, move, and improve the site. Your agreement should explain what transfers, what remains licensed, and what happens when the relationship ends.

This article gives you a plain-English way to check that control. It is general information, not legal advice; a Kentucky attorney should review a contract or ownership dispute involving meaningful money or intellectual property.

A Website Is a Collection of Separate Assets

People often talk about “the website” as one product. It is closer to a furnished storefront: the address, building, sign, fixtures, and customer records are connected but separate assets.

A typical business website includes:

  • A domain name registration
  • A hosting or website-platform account
  • Custom source code and database content
  • Page copy, blog posts, photos, videos, and logos
  • Themes, fonts, plugins, and stock media
  • Email, forms, scheduling, payment, and other connected services
  • Analytics and search-performance accounts
  • Design source files and brand materials

“Full ownership” is too vague unless the contract defines these parts. A useful agreement identifies each deliverable, who owns it before and after final payment, and which third-party terms still apply.

Your Domain Name: Control the Registration

Your domain is the address customers type and the address search engines associate with your site. Losing control of it can interrupt the website and business email at the same time.

A domain is not purchased forever. It is registered for a term through a registrar and renewed. ICANN explains that the registrant is the individual or entity that registers the name and manages it under a contract with the registrar. ICANN also describes the registrant as the party holding the rights to use, renew, restore, or transfer the domain while those rights remain active.

For a business website, the business or business owner should normally be the registrant and control the registrar account. The developer can receive delegated access when the registrar supports it. That lets the developer configure DNS without making the developer the only person who can renew or transfer the name.

Check these details now:

  • The registrar account uses an email address the business controls.
  • The registrant details identify the correct person or legal entity.
  • Two-factor authentication and recovery methods belong to the business.
  • Automatic renewal uses a current payment method.
  • At least one other trusted person knows where the account is documented.

ICANN requires registrants to keep contact information accurate, and ignored registration inquiries can lead to suspension or cancellation under registrar agreements. A domain controlled by a former employee, closed email address, or unreachable developer is an avoidable risk.

Copyright covers original expression such as written copy, photographs, graphics, and sufficiently original code. It does not protect a general idea like “a blue homepage for a roofing company.”

The U.S. Copyright Office says copyright initially belongs to the author when an original work is created and fixed, subject to exceptions such as qualifying works made for hire. That means paying an independent designer or photographer does not, by itself, settle every copyright question.

The Copyright Act also says a transfer of copyright ownership generally must be in writing and signed by the owner of the rights being transferred. Your contract should therefore use clear transfer or assignment language instead of relying on a handshake or an invoice marked “website.”

Work Made for Hire Is a Narrower Rule Than It Sounds

An employee’s work created within the scope of employment may qualify as a work made for hire. Commissioned work from an independent contractor is more limited: it must fit statutory conditions and include a signed written agreement. The Copyright Office’s work-made-for-hire guidance is a good reminder that simply calling every freelance project “work for hire” does not automatically make it so.

A well-written contract can handle this cleanly. It can state which original deliverables transfer to the client after full payment and separately grant any permissions needed for items that cannot or should not transfer.

Content You Supplied Has Its Own History

If your business wrote the page copy, took the photographs, and provided the logo, your developer should not claim ownership merely because those materials were uploaded to the site. Still, confirm that your business actually has the necessary rights.

A photograph from an employee, a logo created years ago by another freelancer, or manufacturer-provided product copy may have separate terms. “It was already on Facebook” is not proof that it is free to reuse. Keep original files, invoices, releases, and license records with the project documentation.

Custom Code, Templates, and Platforms Are Different

Custom code written specifically for your project can be assigned to you under the contract. But most websites also depend on code that was not created for your business.

WordPress, for example, is open-source software distributed under the GPLv2 or later. WordPress publishes its license and the freedoms it provides. You can use and modify the software under that license, but you did not buy ownership of WordPress itself.

The same distinction applies to themes, plugins, fonts, stock photos, and connected services. You may receive a license to use them, sometimes only while a subscription remains active. A developer cannot transfer more rights than the developer has.

Ask for a list that identifies:

  • Custom work that will be transferred to you
  • Open-source components and their licenses
  • Paid products, renewal dates, and account holders
  • Assets limited to one site, one company, or a particular term
  • Features that stop working if a subscription ends

This is not a reason to avoid third-party tools. Good tools can reduce cost and improve reliability. The point is to know which pieces are portable and which are tied to a platform or continuing fee.

Hosting Is Access, Not the Same as Ownership

Hosting is where the website runs. Paying a hosting bill does not automatically prove ownership of the content or code, and owning the code does not guarantee access to the hosting account.

Your business can own the hosting account and grant developer access, a developer can manage hosting as an ongoing service, or a hosted builder can bundle software and hosting.

The arrangement matters less than the exit terms. Before signing, ask whether you can receive a complete export, what that export includes, how long backups are retained, and what help is provided during a move. Some platform features cannot be carried to another system even when your text and images can.

If managed hosting is part of your agreement, clarify what happens after a missed payment or cancellation. A reasonable handoff clause should cover notice, final backups, credentials, outstanding invoices, and a defined transition period.

Own the Business Accounts Around the Website

A technically portable website can still leave you stuck if the connected accounts belong only to the developer. Your business should be the primary administrator or verified owner wherever practical, while outside providers receive the access level needed to do their work.

That includes:

  • Google Search Console
  • Google Analytics
  • Google Business Profile
  • Business email and domain DNS
  • Payment processors and online stores
  • Appointment, form, and customer-management services
  • Advertising accounts and pixels
  • Code repositories and deployment accounts

Google’s permission model shows why roles matter. In Search Console, an owner has full control while other users have narrower access. Your former provider should not be the only verified owner.

Use individual user accounts rather than sharing one password. Then access can be removed without changing the company’s primary login or losing history. Store recovery codes securely, turn on two-factor authentication, and review administrators at least annually.

What Your Web Design Contract Should Say

Ownership conversations are easiest before work begins. If you are comparing providers, add these points to your list of questions to ask a web designer before hiring.

Your written agreement should address:

  1. Deliverables: Name the pages, features, code, copy, graphics, and source files included.
  2. Transfer timing: State whether ownership transfers at creation, launch, or final payment.
  3. Preexisting materials: Identify frameworks, templates, reusable code, or tools the developer keeps.
  4. Third-party licenses: Explain who buys them, who renews them, and what restrictions apply.
  5. Accounts and credentials: Define who creates and controls the domain, hosting, analytics, forms, and integrations.
  6. Portability: Describe the files, database, or export you receive and any platform limitations.
  7. Termination and handoff: Set the notice, fees, timeline, backup, and transition responsibilities.
  8. Portfolio permission: Say whether the provider may display the finished work and brand name.
  9. Maintenance: Separate ownership from ongoing support, updates, hosting, and security duties.

Read the agreement and linked platform terms. If the proposal promises “you own your website,” ask the provider to point to the clause defining that promise.

Red Flags Before and After Launch

Managed service packages and closed platforms can be legitimate. The danger is learning their limits only when you want to leave.

Pause and ask more questions if a provider:

  • Registers your domain in its own name without a documented reason
  • Refuses to identify the hosting company or website platform
  • Will not explain whether custom code and design files transfer
  • Uses one shared account for every client
  • Promises ownership while prohibiting any export or outside developer access
  • Cannot list recurring licenses and renewal responsibilities
  • Has no written cancellation or handoff process

Price and ownership are separate. A subscription may be sensible when its limits are understood, while a custom build may offer more control but still use third-party services. Compare the arrangement, not labels like freelancer, agency, custom, or unlimited. Our guide to choosing a freelance web designer or agency explains other tradeoffs.

A Practical Website Ownership Checklist

If your website is already live, you do not need to start with a confrontation. Start with an inventory.

  • Find the signed proposal, contract, invoices, and platform terms.
  • Identify the domain registrar and confirm the registrant and recovery email.
  • List every service that bills monthly or annually.
  • Confirm your administrator access to hosting, the content system, analytics, and Search Console.
  • Download available site files, database exports, and original brand assets.
  • Record which themes, fonts, photos, and plugins are licensed.
  • Ask the provider to explain any missing access in writing.
  • Keep credentials and renewal details in a secure company-owned password manager.

If something is missing, ask for a normal handoff before assuming the worst. If the contract is unclear, the domain is disputed, or custom work is being withheld, get legal advice before taking action that could interrupt the site.

Control Matters More Than a Slogan

The best answer to “who owns my website after it’s built?” is not a one-word promise. It is a documented arrangement in which your business controls its domain and essential accounts, receives the agreed original deliverables, understands every important license, and has a realistic way to move or change providers.

That clarity protects both sides. You know what you are buying, the developer knows what remains reusable or licensed, and future changes become an orderly handoff instead of a rescue project.

If you want a website built with clear ownership, documented accounts, and no mystery about the handoff, request a quote from Custom Web Architecture. We’ll discuss the structure before the build begins so you know what you control on launch day.