A new developer asks an accounting firm for three things: the domain login, the hosting account and a WordPress administrator account. The owner has years of paid invoices but none of the logins. The old agency says the site sits inside a shared account and cannot be handed over that afternoon. A small update planned for the end of the month stops before it starts. Paying for the website did not give the business working control of it.
Website ownership is not one sentence in a contract. It is the practical ability to renew the domain, access the hosting, appoint administrators, copy the site, use the content and keep email connected. If any of those actions require an agency’s permission, the handover is not clean, even when every invoice has been paid.
A business website is a chain of separate assets and accounts. The domain points visitors to the site. Hosting stores the files and database. The content management system controls who can edit the pages, while email depends on records attached to the same domain. A contract that says the business owns ‘the website’ can still leave those parts unclear.
Each part can be controlled by a different company. An agency may manage the registrar, rent server space and use software under its own licence. That can work well until the arrangement is hidden and the business wants to move.
| Asset | What practical control looks like | Common gap |
|---|---|---|
| Domain | The business can enter the registrar account, renew the registration and approve a transfer. | The domain sits under an agency email address or a former employee’s account. |
| Hosting | The business knows the host, has authorised access and can obtain a current backup. | The site sits in a shared agency account with no agreed exit process. |
| Website files | A complete copy of the site files and database can be supplied in a usable form. | Only page content is exportable, while the working site cannot be copied. |
| Content and design | The contract states what original work transfers, what is licensed and what belongs to a third party. | Payment is treated as proof of ownership without the contract saying what was transferred. |
| Email and DNS | The mail service and domain records are documented, with access held by the business or an authorised provider. | A website move risks breaking email because nobody has the current records. |
Control does not require the owner to manage every account each week. Many businesses prefer an agency to handle renewals, updates and hosting. A sound arrangement allows that convenience without making the agency the only party able to act.
A website ownership check should take about ten minutes when the records are in order. Start with access, not the wording on an old proposal. An account that the business cannot enter is not under useful control. A missing answer is also an answer because it shows where the handover depends on someone else.
Open the accounts rather than accepting screenshots. Confirm the login works, the recovery email belongs to the business and another authorised person can be added. Record the result where a manager can reach it without asking the agency.
Do not put every password in one unprotected document. Use a business password manager, turn on two-factor authentication where it is available and give each supplier a separate account. Shared passwords make departures harder to trace and easier to mishandle.
A website rarely vanishes the moment an agency stops answering. The more common problem is that ordinary work becomes impossible. A domain cannot be renewed, a new developer cannot be added, a broken form cannot be traced or a hosting company will only discuss the account with the person named on it. The site remains visible while the business loses the ability to change it.
Shared hosting creates another practical limit. An agency may hold many sites inside one account, so handing over the master login would expose other clients. The agency may need to create a separate backup or move the site into a new account. The time, cost and responsibility should be explained before the relationship ends.
Paid software can stay behind. A theme, plugin, font or booking tool may be licensed through the agency rather than sold to the business. The site may keep running, but updates can stop when the licence is removed. A fair handover identifies replacements before anything expires.
A fair arrangement gives the business control of the essential assets and gives the agency enough access to do its job. The domain account should identify the business as the customer or registered holder, with a business-controlled recovery email. The business should also have its own administrator account inside the website. The agency can use separate credentials that can be changed or removed later.
Managed hosting can still be a sensible choice. The contract should state how a backup is supplied, whether migration work is charged and how much notice is needed. It should also separate original work from third-party licences. Clear limits are more useful than a promise that the client ‘owns everything’.
No lock-in should let the business leave with its domain, content and site history. It does not make every subscription transferable. The business should know what can move and what must be replaced.
A fair handover does not mean every licence transfers. It means the business knows what can move, what cannot and what must be replaced.
Ownership makes a move possible, but the move still needs planning. Start with a tested site copy, then change the domain records and monitor both servers. Google notes that crawl rate may change for a short time, so keep the old hosting until the new site is working properly.
A redesign or platform change carries more risk because page addresses, content and internal links may change. Keep the pages that already earn traffic, map every changed address to its replacement and retain Search Console and analytics verification. The separate CJ Digital article on rebuilding a website without losing Google rankings covers that process in detail.
A handover should be short enough to use and complete enough to act on. It is a current register of the accounts, files and licences needed to run or move the site.
Domain. Registrar name, account login, renewal date, recovery email and transfer process.
Review the register yearly and whenever a staff member or supplier leaves. Renewal details and two-factor authentication numbers often remain tied to people after their role changes. Updating them then is easier than proving control during an urgent transfer.
Settle website ownership before the first invoice, not during the last week of a strained relationship. Put the accounts, intellectual property terms, licences, backups and exit process in writing. Ask who holds each login and what the business receives when the service ends. Clear terms protect both sides.
Start by requesting the domain, hosting, administrator and email details already attached to the site. Where the record is incomplete, a website support review with CJ Digital can document the gaps, secure the right access and plan a clean transfer before the next renewal or rebuild.
Payment alone does not settle every part of website ownership. The contract, account access, copyright terms and third-party licences decide what the business controls and what it may move.
Yes. A designer or agency can manage the domain, but the business should know the registrar, control the recovery contact and have a written path to transfer or take over the account.
Yes. The business should hold its own Administrator account, while the agency uses a separate account. That keeps full access available without sharing one password between several people.
No. Domain registration and web hosting are separate services, although domain records connect the address to the host. A hosting move should not require the business to surrender its domain account.
Yes, if the domain records for email are missed or changed incorrectly. Record the mail service and its domain settings before any registrar or hosting move, then test email during the change.
