You can pay for a website, use it for years, and still discover that the domain is registered to someone else, the analytics live in a former employee's account, or the only copy of the site is sitting on a vendor's server. Those problems usually surface at the worst possible moment: a redesign, a staff change, a billing dispute, or an urgent outage.
“Ownership” does not mean doing every technical task yourself. It means your business holds the durable assets and can grant a trusted partner the access they need. If that relationship ends, the website should keep working and the handoff should be boring.
Website ownership is a stack.
A website is not one account. It is a connected stack of identity, routing, infrastructure, content, and measurement. Losing control of any one layer can make the others harder to use.
The 12-point ownership checklist.
Use this during a new build, a redesign, or a vendor review. “Yes” means your company has verified access—not that someone remembers a password might exist.
Domain registration
Your company is listed as the registrant where applicable, controls renewal, and can sign in to the registrar.
DNS management
You know where DNS is hosted, have account access, and have a recent record of the live entries.
Business email
Email administration belongs to the company—not an agency account or one employee's personal login.
Hosting & billing
The hosting account, renewal method, service tier, and cancellation/export path are documented.
CMS administration
At least two company-controlled administrators can sign in, and individual users have appropriate roles.
Source code
You have a current copy or repository and know what is required to build and deploy it.
Design & media files
Logos, editable design files, licensed fonts, and original photos are stored with usage rights noted.
Analytics & search
Your company is an owner in analytics and search tools; partners use named, removable access.
Forms & integrations
You know where submissions go and who owns scheduling, payments, CRM, chat, and email tools.
Backups & restore
You know what is backed up, how long it is retained, and who has tested the restore process.
Privacy & consent
Tracking, cookies, form notices, and data processors are inventoried so policies can reflect reality.
Offboarding plan
The contract states what you receive, the format, the timing, and how provider access will be removed.
Score the handoff—not the relationship.
A friendly relationship is valuable, but it is not a continuity plan. Give each group below zero, one, or two points: zero if you do not know, one if access depends on the vendor, and two if the business has verified control.
Illustrative ownership scorecard
This example shows how to visualize your own 10-point self-assessment. It is not a benchmark or measured customer result.
Ownership and access are different jobs.
The safest arrangement is usually company ownership with scoped partner access. That lets specialists do their work without making your business dependent on a shared password or an account you cannot see.
Your business owns
- Domain registration and renewal
- Primary billing relationship
- Analytics and search properties
- Source and final design deliverables
- Customer and form-submission data
Your partner receives
- Named, role-based user access
- Only the permissions needed
- A documented support window
- Revocable deployment access
- No shared owner passwords
There are legitimate exceptions. Some managed platforms bundle hosting, software, and support; some licensed assets cannot be transferred; and some providers use infrastructure shared across clients. The important thing is clarity. You should understand what is portable, what is licensed, what must be exported, and what would change if you left.
Run a 30-minute handoff drill.
- Open the accounts. Have an authorized company user sign in to the registrar, DNS, hosting, CMS, analytics, and search tools.
- Name the owner. Record the company-controlled email or group that owns each account. Avoid making one employee the only recovery path.
- Export the essentials. Save a current site backup, DNS record export or screenshot, source repository location, and an inventory of third-party tools.
- Check renewals. Record renewal dates, payment responsibility, and where notices are sent.
- Test one recovery path. Verify a backup can be restored or a static export can be opened. A backup you cannot use is only a theory.
- Remove stale access. Revoke former employees and old vendors after confirming nothing depends on their accounts.
This checklist is operational guidance, not legal advice. Contracts, ownership rights, privacy duties, and software licenses can vary. If the language in an agreement is unclear, ask a qualified professional to review it before you sign.
Want a cleaner handoff?
SiteMilk builds modern websites with a clear ownership path, practical documentation, and scoped access that your business can revoke.
Talk to the Milkman →