Fenway Web, at fenwayweb.com, is a web design, development and SEO studio with published pricing. Whatever studio or freelancer a business works with, one principle protects it more than almost any other: the business should own its website. That sounds obvious, but many small businesses discover during a dispute, a staff change or a move to a new provider that their domain, hosting account or site files are registered to someone else. This guide explains the main pieces of a website, why ownership matters and how to put each piece in the business’s name.
The Pieces of a Website
A typical website depends on several separate elements, often provided by different companies:
Advertisement
- The domain name, such as example.com, registered through a domain registrar.
- DNS settings, which direct the domain to the right servers for the website and email.
- Hosting, the servers where the website’s files and database live.
- The website files and database, including code, themes, images and content.
- The content management system, such as WordPress or another platform, with its administrator accounts.
- Related accounts, such as email, analytics, search console, ad accounts, payment processors and social profiles.
- Licenses for premium themes, plugins, fonts and images.
Each piece needs a clear owner and documented access.
Why Ownership Matters
When a developer, agency or former employee controls one of these pieces, the business is exposed. Common problems include:
- A domain expires because renewal notices went to someone who left.
- A business cannot move to a new provider because the old one holds the hosting account.
- A relationship ends badly, and access is withheld.
- The site’s source files or design assets were never delivered.
- Licenses tied to a developer’s account stop working when that account lapses.
Owning the core accounts does not mean doing all the technical work. It means the business holds the keys and grants access to the people it hires.
1. Domain Names
The domain is the most important piece, because it is the business’s address online and is often tied to email. Best practices include:
- Register the domain in the business’s name, with the business listed as the registrant.
- Use a business email address that multiple people can access, rather than a single employee’s personal address, for the registrar account.
- Turn on auto-renewal and keep payment details current.
- Enable two-factor authentication on the registrar account.
- Turn on registrar lock to help prevent unauthorized transfers.
- Keep a record of the registrar, expiration date and account details.
If a developer needs to change DNS settings, the owner can grant delegated access or make changes on request rather than handing over the account.
Advertisement
2. Hosting Accounts
Hosting arrangements vary. Some businesses hold their own hosting account and give developers access. Others use hosting managed by a studio as part of a service plan. Either can work, provided the terms are clear. If a provider hosts the site, the business should know:
- Where the site is hosted and under what account.
- How to obtain a full copy of the site files and database at any time.
- What happens to the site if the service ends.
- Whether backups are included and how to access them.
Where possible, the business should hold the hosting account directly, or at least have a written agreement guaranteeing access to its data.
3. Source Files and Content
A website is more than what appears in the browser. Source files may include custom code, theme files, design mockups, logos in original formats, photographs and written content. Ownership of these materials depends partly on contracts and intellectual property law.
Before work begins, the business and the developer should agree in writing on:
- Who owns the finished website and its custom code.
- Whether design files and original assets will be delivered.
- How third-party components, such as licensed themes or stock images, are handled.
- Any rights the developer keeps, such as using the work in a portfolio or reusing general-purpose code.
At the end of a project, request a complete package: a full backup, source files, design files and documentation.
4. Administrator Access
The business should have its own administrator account in the content management system, not just an editor login. Each person who works on the site should have a separate account with the minimum permissions needed. When someone leaves or a contract ends, their access should be removed promptly.
5. Connected Accounts
Analytics, search console, advertising, email marketing and payment accounts should also be owned by the business, with others added as users. This preserves historical data and avoids losing years of insight when a provider changes.
6. Licenses
Premium plugins, themes and fonts often require licenses for updates and support. Ideally, licenses should be purchased in the business’s name or transferred to it, with renewal dates tracked.
Build an Ownership Record
A simple document, stored securely, can make a big difference. It should list each service, the provider, the account owner, renewal dates and who has access. Passwords belong in a secure password manager, not in a shared spreadsheet or email.
If You Do Not Own Everything Today
Many businesses find gaps when they first check. Most can be resolved through a polite request to the current provider: transferring a domain, adding the business as an account owner or delivering files. Approach the conversation early and in writing, before a crisis.
The Takeaway
A business should hold the keys to its own website: the domain, hosting or a guaranteed copy of the site, the source files, administrator access and connected accounts. Good providers welcome this arrangement, because it builds trust and makes the relationship about service rather than control.
Quick check: Whose name should a business’s domain be registered in?
- The web developer’s
- The business’s
- Whichever employee set it up
Show answer
B. Registering the domain to the business, with shared access and auto-renewal, prevents lockouts and accidental expiration.