Not automatically, no. Ownership is decided by two things: whose name sits on the domain registration and the account logins, and what your written agreement says about who owns the work. Neither is automatic. If the domain is registered to your web company and the contract is silent on handover, you can pay a monthly fee for years and still leave with nothing but an invoice history.
Who owns my website if I leave my web designer?
Paying monthly for a website feels like ownership. It often isn’t. In a lot of small-business arrangements, the monthly fee buys you access to something the vendor owns and operates — a site built on their platform, hosted in their account, pointed at a domain registered under their name. The moment you stop paying, the arrangement ends the way a lease ends. The lights go off and the keys were never yours.
That is not always what is happening. Plenty of web companies register the domain in the client’s name from day one and hand over files without being asked. The problem is that you cannot tell which kind you are dealing with from the website, the proposal, or how friendly the salesperson was. You can only tell by looking at the registration record and reading the agreement.
Vendors have very little incentive to publish the answer. Nobody wins a new client by explaining what happens when the client leaves. So the question gets avoided, and owners end up circling it indirectly. On ContractorTalk, one thread about marketing vendors puts the frustration in plain language: “If you don’t know what your SEO firm is doing, at best you’re wasting your money.” Another thread is simply titled “tired of lead and seo fees.” Neither one names domain ownership. Both are describing the same underlying worry — that you are paying into something you do not control and cannot take with you.
The fix is unglamorous. Find out what you own right now, decide what you want to own, and get it written down before money changes hands.
The six assets that get argued about at the exit
“The website” is not one thing. It is a bundle of separate assets that can be split up, and at the exit they get split up. Knowing which piece is which tells you what is painful to lose and what is merely irritating.
1. The domain name. This is the asset that matters most and costs the least. It is your address. Lose it and every business card, truck wrap, directory listing, review profile link and years of accumulated search equity points at somebody else’s property. Everything else on this list can be rebuilt with effort. The domain cannot be rebuilt at all if the other side refuses to release it.
2. DNS and email routing. Less obvious, more disruptive. Whoever controls DNS controls where your website traffic goes and, frequently, where your company email goes. If your web company set up your email on their account, a messy exit can take your inbox down along with your site. Owners discover this in the worst possible week.
3. The site files and design. The templates, the code, the layout, the configuration. Whether you can take these depends on how the site was built and what the contract says about work product. A site built on a common content management system usually exports as a file and database package. A site built inside a vendor’s own system usually does not.
4. The written content and photography. Service pages, location pages, FAQs, the photos of your crew and your finished jobs. This is the part most owners assume is theirs and most contracts never mention. If you paid a copywriter through an agency, say so in writing: the copy and images are yours to use anywhere, including on a site someone else builds.
5. The tracking and advertising accounts. Google Analytics, Search Console, Google Ads, Meta Ads, call tracking. The account structure matters more than people expect. An ads account owned by the agency takes its spending history and audience data with it when you go, and you start a new account cold. Analytics history is the record you use to tell whether the next vendor is doing better or worse.
6. The Google Business Profile. For a local service business this is often a larger lead source than the website. It should be owned by an account you control, with the vendor added as a manager — not the other way round. Recovering a profile from an unresponsive manager is possible, but it is a process with waiting periods, and you do not want to run it during a dispute.
Rank them by how badly a loss hurts: domain and Google Business Profile first, lead data next, content and tracking history after that, site files last. Site files are usually the thing people argue about hardest and need least.
Is the domain actually in your name? How to check in ten minutes
Start with the public registration record. Search for a WHOIS or domain lookup tool, enter your domain, and read what comes back. You are looking for the registrar — the company the domain is registered through — and the registrant, which is the legal owner. If privacy protection is switched on you may see a proxy service instead of a name. That is normal and not in itself a red flag, but it means the public record won’t answer your question.
The record also lists administrative and technical contacts. People confuse these with ownership. They are not ownership. The registrant is the owner; an admin contact is just someone authorised to make changes. A vendor listed as admin contact on a domain registered to you is a reasonable setup. A vendor listed as registrant is not.
Next, and this is the step that actually settles it: log in to the registrar account yourself. Not a screenshot, not a PDF, not a verbal assurance on a call. If you have never had the login, that is your answer. Ask for the username and password, change the password while you are in there, and add your own email and phone as recovery contacts. The email address on the registrar account is the real key to the kingdom, because whoever receives password resets can take the domain back later.
While you are logged in, check two more things: whether the domain is locked against transfer, and when it expires. Add your own payment card so it cannot lapse because a former vendor stopped paying a renewal nobody remembered.
If the answer turns out to be “my web guy set it up and I’ve never seen it,” ask for the transfer authorization code in writing today, while the relationship is still friendly. Requesting it is not an announcement that you are leaving. It is basic housekeeping.
If the domain is registered to your web company and they refuse to release it, gather your invoices and any written statements about ownership, put the request in writing with a deadline, and escalate to the registrar’s dispute process. A domain registered to a vendor who was paid to register it for you is a dispute worth having, and it is far cheaper to prevent than to win.
Who owns the leads, the call recordings and the phone number?
This is the part most contracts skip entirely, and it is the part that costs the most to lose. A website can be rebuilt in weeks. The record of every person who has ever called, filled in a form, booked an appointment or asked for a quote cannot be rebuilt at all. It is history, and history only exists once.
The contact database. If your vendor runs a CRM or marketing system on your behalf, ask one question: can you export the contacts, the form submissions, the message history and the appointment records as a standard file, on request, without a fee? CSV is the answer you want. “We can send you a report” is not the same thing — a report is a summary, an export is the data. A database you can leave with is worth more than a design you can leave with.
Call recordings and voicemail. Recordings often sit inside a tracking platform on a vendor’s account and get deleted on a retention schedule when the account closes. If recordings matter to you — for training, for disputes, for checking how calls are actually handled — ask whether you can download the audio files in bulk, and whether retention is tied to your service continuing.
Tracking phone numbers. Yes, a tracking number can usually be ported to another provider, but only if two conditions hold. The number has to be portable in the first place, and the party on the account has to cooperate with the port request. Porting needs the account number, a billing PIN or passcode, and a recent bill — all held by whoever owns the account. If you have been advertising a tracking number on your vehicles and in directories for years, that number is effectively a second business address, and it should be in an account in your business name. Carriers are the slowest part of any exit, so a port request is the first thing you start, not the last.
Review profiles and the booking calendar. Reviews attach to the business profile, not the vendor, provided the profile is owned by your account. Booking calendars are the quiet risk: if appointments live in the vendor’s scheduling tool, confirm you can export upcoming bookings and past history before anything gets switched off, because customers who booked three weeks out do not know your vendor relationship ended.
Proprietary platform versus portable site: what ‘you can’t take it with you’ really means
It is worth being honest about this, because “you own everything” is sometimes a marketing line rather than a technical fact. Some things genuinely cannot transfer, and a vendor who says so plainly is being straight with you.
What legitimately stays behind: licensed software the vendor pays for, a proprietary platform they built and operate, third-party subscriptions bought under their account, and any automation or system they run across multiple clients. You did not buy that software. You bought the use of it, the same way you rent equipment rather than buy a factory. That is a defensible arrangement as long as it is stated clearly before you sign, not revealed at the exit.
What should always transfer, regardless of platform: the domain, the written content, the photography, the contact and lead data as an export, your tracking and advertising accounts, and your Google Business Profile. None of those are the vendor’s intellectual property. They are your business records and your identity, and no platform argument covers them.
The warning sign is a contract that uses the platform as cover for holding everything. It reads something like “all materials created during the engagement remain the property of the agency” with no carve-out for your domain, your data or your content. That single clause can turn a disagreement about service quality into a hostage situation. You end up unable to leave, not because the work was good, but because leaving is too expensive.
A reasonable standard sounds like this: the platform stays with the vendor, and you leave with the domain, the content, a working copy or export of the site, and every byte of customer data. If a vendor can agree to that sentence in writing, the proprietary platform is not a problem. If they cannot, the platform was never the real issue.
The questions to ask before you sign — and the answers that should worry you
Ask these on a call, then ask for the answers in the agreement. A good partner finds the questions reasonable. Watch how quickly the tone changes.
Whose name goes on the domain registration? Good answer: your legal business name, with the vendor added as a technical contact. Worrying answer: “we handle all that for you” — which is not an answer to the question asked.
Who holds the registrar login, and can I have it? Good answer: you do, from day one, with your email on the account. Worrying answer: “we keep it so nothing breaks.” Things break regardless; the only variable is who can fix them.
If I leave, do I get the site files and the content? Good answer: a specific description of what is delivered and in what format. Worrying answer: “we’d obviously work something out.” Obvious things belong in writing.
Can I export my contacts, form submissions and call history? In what format, how fast, and at what cost? Good answer: CSV on request, within a named number of business days, at no charge. Worrying answer: anything involving a fee, or “we can run you a report.”
Who owns the ad accounts, Analytics and Search Console? Good answer: accounts created under your ownership with the vendor granted access. Worrying answer: “we run everything through our agency account” with no transfer path.
Who owns the Google Business Profile? Good answer: you, with the vendor as a manager. Worrying answer: the vendor created it and is the primary owner.
What is the notice period, and what happens to the site during it? Good answer: a defined notice window, with the site live and the handover running in parallel. Worrying answer: vague language that lets the site come down the day you give notice.
Is there a cancellation fee, and is it tied to the site staying up? Good answer: no, or a clearly stated early-termination amount with the handover obligations intact either way. Worrying answer: a fee that functions as a ransom for your own content.
Where in the agreement does it say all of this? This is the question that matters. A promise on a sales call has exactly the weight of a promise on a sales call. If every answer above was excellent and none of it appears in the document, you have not bought any of it.
One more, for a vendor you are already with: ask them today, in an email, and keep the reply. A written answer from a current vendor is useful evidence later.
What a clean handover looks like in practice
A handover is a short, defined project, not a negotiation. Here is the sequence a competent one follows.
- Written notice. Email, dated, stating the end date and asking for the handover items by name.
- Phone porting starts first. Carriers move slowest, so request the account number, PIN and a recent bill at the same time you give notice.
- Domain transfer. The vendor unlocks the domain and sends the authorization code; you transfer it to a registrar account in your name, or they change the registrant to you at the existing registrar.
- File and data export. Site files and database, content and images, and a full contact and lead export delivered by a stated deadline.
- Account access transfers. Analytics, Search Console, ad accounts and the Google Business Profile reassigned to your ownership, with the vendor removed after you confirm access.
- Hosting cutoff. A final date agreed in writing, after the new site is live and tested — not before.
The whole thing should be measured in days, with one named person responsible on each side. If a vendor cannot describe this sequence when you ask, they have either never done it or never intended to.
What we put in writing — and why we’d rather answer this before you sign
On a built-and-run engagement here, the terms are stated up front rather than discovered later. The domain is registered in the client’s business name. The written content, the site pages and the images are the client’s to keep and reuse. Contact and lead data is exportable on request in a standard file format. Tracking and business profile accounts are set up under client ownership with access granted to us. The handover steps and timeline are named in the agreement, so an exit is a checklist rather than an argument.
The platform and the automation that runs on top of it stay with us, and that is said plainly too, because pretending otherwise would be the same avoidance this post is about.
Being willing to answer the ownership question before you sign is the clearest difference between a partner and a landlord. If a conversation starts with the contract instead of the colour palette, that is a good sign — about them, and about you.