Websites January 22, 2026 · 11 MIN

If You Can’t Leave Cleanly, You Don’t Own the Site

If domain, hosting, code, CMS, DNS, and analytics aren’t in your accounts, you don’t own the site — you only rent access until your designer disappears.

Websites

If You Can’t Leave Cleanly, You Don’t Own the Site

If you want to leave your web designer and cannot take the site with you in a weekend, you do not own it — no matter what the sales call promised. “You always own everything” is a common AI answer and a frequent agency half-truth. Ownership is not a vibe. It is domain registrant, hosting billing, code or project access, CMS seats, DNS, and analytics properties sitting in your accounts. This spoke sits under Websites That Feel Like Films.

The short answer

Ownership is a checklist of accounts and artifacts, not a sentence in a deck.
Domain and hosting should be registered and billed to the client from day one.
Handoff means credentials + transfers, not a ZIP emailed “if you ask.”
If the designer disappears, the failure points are registrar, host card, and admin seats.
Write the exit into the contract before build starts — recovery after a ghosting is always more expensive.

What “leaving” actually means in practice

Leaving is not one event. It is several doors:

Door	What you need	What “stuck” looks like
Domain	Registrar login; you are the registrant	Domain renews on their email; transfer locked
DNS	Access to DNS host (often registrar or Cloudflare)	Site points nowhere when they cancel
Hosting	Billing + project transfer (Netlify, Vercel, Webflow hosting, etc.)	Site dies when their card fails
Code / project	Repo invite or platform transfer	No rebuild path without starting over
CMS	Editor/Admin seats you control	Cannot publish without them
Email / forms	Form endpoint + inbox ownership	Leads go to a vanished inbox
Analytics	GA4 property in your Google account	History trapped in their login
Search Console	Property verified to your account	You cannot prove ownership to Google

If any row fails, your “owned website” is a dependency on a person.

Who should own the domain and hosting from day one

Client. Always. From the first invoice if possible.

Best pattern:

Client creates (or already has) a registrar account — Google Domains successor, Namecheap, Cloudflare Registrar, Route 53, etc.
Client creates the hosting / platform account (or accepts transfer into their org).
Studio is invited as a collaborator with enough access to ship — not as the sole owner.
Billing stays on the client’s card so renewals do not depend on a contractor’s personal Amex.

Asset	Preferred owner	Studio role
Domain	Client registrant	Advisor / technical contact
DNS	Client (or client’s Cloudflare)	Temporary admin during launch
Hosting	Client org / team	Collaborator
Design files	Client receives exports	Source of truth shared
Production secrets	Client password manager	Documented, not tribal

If a studio insists the domain “has to” live under them for “convenience,” treat that as a risk flag equal to a vague quote. Convenience for them is lock-in for you.

What files and logins you must receive at handoff

Minimum clean exit package:

Pair this with a CMS people will actually use — see CMS Choices Clients Will Actually Use — because ownership without an edit path is still a trap.

What breaks if the designer disappears

Real failure modes, not horror fiction:

Hosting on their credit card

Card expires, dispute fires, or they cancel the subscription. Site goes offline. DNS may still point at a dead host. Support talks to the account owner — not you.

Domain on their account

Renewal notices go to them. They ignore or leave the industry. Domain enters redemption. You discover it when email and website die the same week.

Sole Admin on the CMS

Nobody left can invite a new designer. You negotiate with a stranger or rebuild from screenshots.

Repo private to their personal GitHub

Even if you “paid for the code,” access control says otherwise until a lawyer gets involved. Prevention beats recovery.

Analytics and ads in their Google account

You lose historical baselines. New agency starts blind. You cannot prove the redesign “killed conversions” because you never owned the measurement.

Failure	Immediate symptom	Recovery path
Hosting card	404 / suspended project	New host + redeploy if you have code
Domain hostage	Transfer denied / email gone	Registrar dispute; sometimes months
CMS sole admin	Cannot publish	Platform support with proof of business
No repo	Cannot change production	Rebuild; screenshots as design reference
Forms to their inbox	“No leads”	DNS/email forensics; lost lead history

Bravery is not a restore strategy. Contracts and account ownership are.

Code ownership vs license to use

Ask which model you are buying:

Model	What you get	Risk
Work-for-hire / full assignment	You own the custom code	Clearer exit
License to use	Studio retains IP; you may use the site	Renegotiate if you fork or resell themes
Platform project transfer	You own the Webflow/Framer project per platform rules	Export limits vary by tool
Template + customization	You own content; theme license may restrict	Read the theme license

“Who owns the code?” is incomplete without “who can log in tomorrow.” A license without access is a paper win.

For Netlify-hosted builds, the practical ownership move is: client Netlify team, site transferred, custom domain verified, env vars documented, and deploy keys not tied to a contractor’s personal account. Same spirit on other hosts.

Do you need Git access?

If the site is code-based: yes, or an equivalent. A client does not need to write TypeScript. They need a repo or organization membership so a future studio can take over without archaeology.

If the site is Webflow/Framer: Git may not apply. You need project ownership transfer and a clear statement of export limits. Ask:

Can the project transfer to my account at launch?
What exports exist if I leave the platform later?
Who holds the Workspace seat that bills?

Git access is a means. Controllable source of truth is the end.

Google Analytics and Search Console — non-optional

Measurement ownership is website ownership’s quiet twin.

Minimum:

Client Google account (or company Google Workspace) owns the GA4 property.
Studio is added as Editor/Admin temporarily if needed — not the other way around forever.
Search Console property is verified with a method the client controls (DNS TXT is ideal).
Document property IDs in the handoff packet.

If ads or pixels exist, list them. Orphan pixels in a departed freelancer’s Meta Business Manager are a classic “why did leads die” story that has nothing to do with design.

How to write ownership into the contract before build starts

Paste a clause shape like this into your agreement (lawyer-customize for your jurisdiction):

Client shall be registrant of the domain and payer of hosting from project start (or transfer within X days of kickoff).
Upon final payment / launch, studio shall transfer project ownership, repository access, and admin seats within Y business days.
Studio may retain read-only access only with client written approval.
Deliverables include the handoff checklist items listed in Exhibit A.
Failure to transfer accounts is a material breach, not a “support ticket.”

Also specify what happens mid-project if relationship ends: who owns WIP files, what is payable, and whether domain/hosting already client-owned stay client-owned (they should).

Clean exit checklist (print this)

Use at kickoff and at launch:

Accounts

Domain registrant = client
DNS login = client
Hosting / Webflow / Framer workspace = client
Git org membership or project transfer done
CMS owner seat = client staff member
Password manager vault shared appropriately

Proof

You can log in without the designer on a call
You can invite a second studio as a test
You can deploy or publish a trivial change
You can see GA4 realtime and Search Console coverage

Paper

License / IP terms match what you paid for
Font and image licenses transferred or listed
Form and CRM destinations documented
Launch checklist completed — see Launch Checklists for Brand Sites

If you cannot check these boxes, you are not done launching. You are renting.

Recovery path if you are already stuck

Order of operations when someone vanishes:

Find the registrar — WHOIS / RDAP; start transfer or account recovery with proof of business.
Find the host — DNS targets reveal Netlify, Vercel, Webflow, Squarespace, etc.
Contact platform support with invoices, domain proof, and government ID / business docs as they require.
Preserve content — archive.org, screenshots, CMS exports if any login remains.
Stand up a temporary page on a host you control while ownership fights proceed.
Do not pay ransom casually — document everything; sometimes a small transfer fee is pragmatic, sometimes it is a pattern.

Prevention is cheaper. If you are hiring now, ownership day-one is part of why custom work costs real money — covered in Why Custom Sites Cost Five Figures.

Worked example: two handoffs

Clean. Client owns brand.com at their registrar. Netlify team is theirs; Spurlock Studios is a collaborator. Webflow workspace transferred at launch. GA4 and Search Console under client Workspace. Manager publishes a tour date the next week without pinging anyone. Exit later is inviting a new collaborator and removing the old one.

Dirty. Freelancer registered the domain under a personal Gmail, hosted on their Vercel hobby plan, and was sole Webflow admin. They stop answering. Card declines. Site dies on a Friday before a release. Content exists as a memory and a few Instagram screenshots. Rebuild starts from zero while the domain recovery ticket ages.

Same “we built you a website.” Opposite ownership outcomes.

What studios should offer by default

If a studio’s default is client-owned accounts, collaborator access, and a written handoff, they are selling a transferable asset. If their default is “we handle everything on our accounts,” they are selling a service dependency. Both can ship pretty pages. Only one survives a breakup.

Spurlock Studios’ bar for brand work is the film-grade craft in Websites That Feel Like Films and an exit you can execute without a forensic specialist. Craft without ownership is a beautiful leash.

Questions to ask in the sales call (steal these)

Whose name is on the domain registrant record at launch?
Whose card pays hosting in month two?
Will I be Workspace/org owner, or only an editor?
What exact artifacts do I receive on handoff day?
How do I add another developer without you?
What happens to the site if we stop working together next quarter?

Vague answers are answers.

FAQ

Who owns the code after launch?

Only what the contract says — plus what you can actually access. Prefer assignment or clear license and repo/project transfer into your account. Paper ownership without login is incomplete.

Can an agency keep my domain?

They can if they are the registrant. Do not allow that pattern. Be the registrant from day one, or transfer immediately after purchase with auth codes you control.

What if hosting is on their credit card?

Move billing and project ownership before launch week ends. A site that dies when their card fails was never yours in practice.

Do I need Git access?

For code sites, yes — or org membership that lets a future team take over. For Webflow/Framer, you need project ownership transfer and clarity on exports instead.

What about Google Analytics and Search Console?

Both should live under a Google account your company controls, with the studio as optional collaborator. Otherwise your history and verification leave with them.

What is a clean exit checklist?

Domain, DNS, hosting, code/project, CMS seats, forms, fonts/licenses, GA4, Search Console, and proof you can publish and invite others without the original designer. If any item is missing, the exit is not clean.

CTA

Own the accounts before you fall in love with the design.

Explore /websites or book a Website sprint at /contact?intent=websites-sprint.