Short answer
Keep the domain registration, DNS, hosting, business email, analytics, Search Console, Business Profile, website files, backups, and recovery information documented under business-controlled access whenever practical. Then make the contract clear about ownership, licenses, and handoff responsibilities.
Access, control, possession, and ownership are not the same thing.
You can possess a copy of a website without controlling the hosting account. You can control a domain account without owning every piece of licensed software used on the site. You can have administrator access to analytics without being the account owner.
Those distinctions are why "Do I own my website?" is not always answered by one yes or no.
This Field Note is operational guidance, not legal advice. Intellectual-property rights, licenses, and contractual ownership depend on the agreement and the assets involved.
Start with the domain.
The business should know which registrar holds the domain name, which account controls it, how renewal works, and who receives recovery notices. The domain is the address customers and search engines rely on. Losing access to it can disrupt the website, business email, and other connected services.
A designer may help configure the domain. That is different from making the designer's personal account the only place it can be managed.
Document DNS and hosting separately.
The registrar and the host can be the same company, but they are not the same function. DNS determines where different services point. Hosting is where the website itself runs.
Keep a simple record of:
- the registrar
- the DNS provider
- the hosting provider
- the primary administrator
- renewal or billing responsibility
- recovery methods
Analytics and search accounts should survive the vendor relationship.
Google Analytics, Search Console, Tag Manager, Business Profile, advertising accounts, and similar systems build history over time. If a designer, marketer, or agency creates them, the business should still have appropriate ownership or administrative access.
Do not casually replace a working analytics property simply because a new vendor arrives. Historical data is useful.
Ask what files actually exist.
The answer depends on the platform. A static website may have source files that can be handed over directly. A hosted builder may rely on an account rather than a traditional folder of deployable files. A custom store may combine theme code, product data, apps, and platform configuration.
A useful handoff explains what can be exported, what remains platform-dependent, and which assets or licenses have restrictions.
Know which assets are licensed rather than owned outright.
Fonts, stock photography, plugins, themes, SaaS tools, music, and other assets can have licenses that restrict transfer or future use. The agreement should identify anything the business cannot freely move to another vendor.
This is also why a vague promise such as "you own everything" can be less useful than a clear list of what is included, what is licensed, and what account controls each item.
A clean handoff should leave the business less dependent, not more confused.
STATICMETHOD's Client Vault™ is designed around that practical problem. Project files, brand assets, PDFs, links, credentials, documentation, and recommendations are organized in one place so the business is not hunting through old text threads six months later.
Before hiring any provider, ask how the handoff works. A polished launch matters. So does being able to operate after it.