GUIDE · CONTRACTOR WEBSITES

Do You Really Own Your Contractor Website?

Three separate things have to be in your name: the domain, the hosting, and the site files. Most locked-out contractors only ever controlled one of the three, and did not find out until they tried to leave.

Be Seen, Contractors!10 min readUpdated 2026

The short answer

Owning your contractor website means three things are in your name and under your login: the domain (the address, like yourcompany.com), the hosting (the server the files sit on), and the site files (the actual code and content). A lot of contractors control none of the three. The nephew, the agency, or the $99/month builder registered the domain, hosts the site, and owns the template, and the whole thing evaporates the day you stop paying or the relationship ends.

The fix is not complicated, but it has to be checked before you are mid-fight. This guide shows you how to verify each of the three, spot the lock-out traps in DIY builders and cheap agency deals, and get everything moved into your name so the site is an asset you own, not a subscription you rent.

The three things you have to own (and why they are separate)

People say "my website" like it is one thing. It is three, and they can each live in a different account owned by a different person. That is exactly how contractors get stuck.

PieceWhat it isWhere it livesWhat happens if you do not own it
Domainyourcompany.com, the address people typeA registrar (GoDaddy, Namecheap, Cloudflare, etc.)You cannot move it, and it can be pointed anywhere or held hostage on renewal
HostingThe server that answers when someone visitsA host or platform account (Cloudflare Pages, a builder, cPanel)Turn it off and the site goes dark, even if you own the domain
Site filesThe code, images, and page contentA repo, a folder, or trapped inside a builder's templateNothing to move: you rebuild from scratch somewhere else

The reason this matters: a builder like Wix or Squarespace will happily let you own the domain while the site itself is locked inside their platform. You can point the address anywhere, but there are no files to take with you. On the flip side, a cheap agency might build you a real site but register the domain in their account, so they hold the front door key.

Real ownership means all three sit in accounts with your email on them, your credit card, your name on the invoice. If any one of them is in someone else's account, you do not fully own the site. You are renting a piece of it from them, and the terms are whatever they decide the day you want to leave.

Think of it like a truck. The domain is the plate and the title, the hosting is the parking spot, and the files are the truck itself. You can have the title but no truck (domain but a builder site you cannot export). You can have the truck but no title (a real site on a domain someone else registered). Only when all three are yours do you actually own the rig, and only then can you drive it wherever you want.

How to check who owns your domain right now

Start with the domain, because it is the one you can verify in about two minutes without asking anyone. The domain is the most valuable and most fought-over piece: it is where your reviews, your Google listing, and years of search history all point.

Do a public WHOIS lookup. Type your domain into any WHOIS search (ICANN's lookup tool works). Most contractors have privacy turned on, so the public record will show a proxy, not a name. That is normal and fine. What it does not tell you is which account the domain lives in, and that is the part that matters.

So go straight to the registrar. Log in to the account where you think the domain is registered (GoDaddy, Namecheap, Cloudflare, Google Domains now moved to Squarespace, and so on). If the domain shows up in your account under your login, good. If you have no login, or the domain is not listed when you get in, someone else controls it. Ask these questions plainly:

  • Which registrar is the domain registered with?
  • Whose email is on the registrar account?
  • Whose card renews it every year?
  • Can you get the login handed to you today?

If the person who built your site gets vague on any of those, that is your answer. A straight builder hands over the registrar login without a fight. Someone who wants to keep you locked in will explain why they "manage it for you" instead. Managing it for you is fine while you are working together. Not being able to get it back is a trap.

One more tell: check the domain's expiration date while you are in there. Domains registered on someone else's card have a way of quietly lapsing when the relationship sours, and an expired domain can be scooped up by anyone within days. If your address goes dark for a week because a nephew's card expired, your Google listing and every link pointing at you goes dark with it.

While you are checking, do the same pass on hosting. Ask where the site is actually served from and whose account it sits in. You can spot the host with a quick lookup tool, but the account is the real question: a site hosted inside a builder's platform cannot be moved without a rebuild, no matter who owns the domain. Owning the domain and the host account, but discovering the files are trapped, is the most common surprise contractors hit. So verify all three the same way: log in yourself, or watch someone log in and show you it is your account, not theirs.

The lock-out traps in cheap builders and $99/month deals

Most lock-outs are not malice. They are the business model. A subscription site builder makes money by making it hard to leave, so the whole thing is engineered to keep your website inside their walls.

Here is what that looks like in practice on the deals contractors get pitched:

  • The all-in-one builder ($49 to $299/month). Wix, Squarespace, GoDaddy Websites, Duda. The site is real and it works, but the files live in their platform. Stop paying and the site goes dark. There is no clean export you can drop onto another host. You own the domain (usually), the content in your head, and nothing else.
  • The "free" website with the marketing contract. A lead-gen company or an HVAC/roofing "marketing system" builds the site at no upfront cost, then owns it as a lever to hold. The domain is often in their account. Cancel the monthly and the site, and sometimes the domain, walks out with them.
  • The nephew or the buddy. No contract, no documentation, domain registered on a personal Gmail nobody can find three years later. When they move, change jobs, or stop answering, you are locked out of an account you never had the password to.
  • The agency that "handles everything." Legitimate on the surface, but the domain, the host, and the code all sit in the agency's master accounts. Great until you want to switch agencies, at which point everything is a negotiation.

The common thread: your website is being used as a hostage to keep the monthly payment coming. None of these are scams exactly. They are just rental arrangements dressed up to look like ownership. A site you truly own keeps working the day you fire everyone, because the domain, the host, and the files are all in accounts you control.

There is a specific version of this that stings the worst for established contractors: the site that has been ranking and ringing for years. You built up reviews, a Google listing, and search history all pointing at that address, then you go to switch providers and learn the domain was never yours. Now the thing you spent years earning is the exact thing being held over you. The earlier you check, the cheaper the fix. Sorting ownership out on a two-year-old site is a phone call. Sorting it out after a decade of investment, when a former provider knows what it is worth to you, is a fight.

Owned vs rented: a straight comparison

Rented site is not automatically bad. For a brand-new one-truck operation testing whether they even want a web presence, a builder subscription can make sense for a season. The problem is contractors treat rented as owned, invest years of reviews and search history into it, and then discover they cannot take any of it with them.

Rented (builder subscription)Owned (hand-coded static site)
DomainUsually yours, if you set it upRegistered in your account, your name
HostingBundled, cannot be separatedAny host you choose; portable
Site filesTrapped in the platform, no clean exportHanded to you as real code you keep
If you stop payingSite goes darkSite keeps running on your host
Moving to a new builderRebuild from scratchCopy files, point domain, done
Ongoing costMonthly, forever, or it disappearsDomain (about $15/yr) plus hosting (often free to cheap for static)

The way we build sits on the owned side by design. Hand-coded static sites (no WordPress, no page-builder) are plain HTML, CSS, and a little JavaScript in a folder. There is nothing proprietary to get trapped in. The domain goes in your name, the site files get handed over as an asset you keep, and the site loads in under two seconds because there is no platform bloat sitting between the visitor and the page.

That does not mean cheaper is always right. It means you should know which side of this table you are on before you pour a year of reviews and rankings into something you do not own. The math also shifts over time. A builder at $99/month is $1,188 a year, every year, forever, and you own nothing at the end of it. An owned static site is a one-time build plus a domain renewal and cheap-to-free hosting. For a contractor who plans to be in business more than a year or two, owned wins on cost and on control at the same time, which is rare.

How to get everything back in your name

If you found out you are locked out, do not panic and do not burn the bridge yet. You need cooperation from whoever holds the accounts, so play it straight until the transfer is done. Work through it in this order.

  1. Get the domain first. It is the piece worth fighting for. Ask for the registrar login, or ask them to release the domain and send you the authorization code (called an EPP or transfer code) so you can move it into your own registrar account. Once the domain is in your name, you hold the strongest card in the deal.
  2. Get the site files. Ask for a copy of the actual site: the HTML, CSS, images, and any content. If it is a real coded site, this is a folder they can zip and send. If it is a builder, there may be no clean export, in which case the files are gone and a rebuild is the honest answer.
  3. Sort out hosting. Once you own the domain and have the files (or a rebuilt site), hosting is the easy part. Point the domain at your new host and the site is live under your control.
  4. Document it. Write down which registrar the domain is in, which host serves the site, and where the files are backed up. Put the logins somewhere you and one trusted person can reach. Most lock-outs happen because one person had one password and then disappeared.

If the current holder refuses to release the domain, you have options. A registrar can help with a dispute when you can prove the business is yours, and ICANN has a formal transfer-dispute process. It is slow, but a domain registered for a business you clearly own is not something a former contractor gets to keep. Keep every invoice, email, and receipt that shows the domain was bought for your company.

The clean move, if the old site is trapped or the relationship is beyond saving, is to get the domain into your name and rebuild the site properly on it. You keep the address (and everything pointing at it), and you finally own the thing that sits behind it.

What ownership should look like before you launch a new site

Whether you are hiring us or anyone else, this is the checklist that keeps you from ending up locked out again. Get answers in writing before you pay for a build.

  • The domain is registered in your account, your name, your card. Not "we'll manage it." You hold the registrar login from day one.
  • You get the site files at the end. The finished site is handed to you as real code you can take to any host. Not a template you rent.
  • Hosting is separable. You can move the site to another host without a rebuild. Static sites make this trivial.
  • Logins are documented and yours. A short handoff sheet listing registrar, host, and where the files live. Passwords in your possession.
  • No hostage clause. Nothing in the deal says the site or domain reverts to the builder if you stop a monthly payment.

Notice what is not on that list: you do not have to become a tech person to own your site. You do not need to manage the server or touch the code. Owning it just means the accounts have your name on them and the files exist somewhere you can reach. Someone can still handle the day-to-day for you. The difference is they are doing it in accounts you control, so the day the relationship ends, you keep everything and simply hand the keys to whoever is next.

That is the whole test. A build shop that intends to keep you as a client through good work will hand you every key without hesitation, because the way you keep a contractor is by ringing their phone, not by holding their domain hostage. Since 2008 that is how we have handed sites over: domain in your name, files in your hands, hosted somewhere portable, and built to load fast and get quoted by search rather than trapped behind a monthly bill.

If you want, we will do a free look at what you currently own before you commit to anything. We will tell you plainly whether your domain, host, and files are actually in your name, and what it would take to get them there. No obligation to build with us to hear the answer.

Key takeaways

  • A website is three things: the domain, the hosting, and the site files, and they can each live in a different person's account.
  • The domain is the piece worth fighting for; get it into your own registrar account first.
  • Builder subscriptions (Wix, Squarespace, $99/month deals) trap the site files, so leaving means rebuilding from scratch.
  • Verify ownership by logging into the registrar and host yourself, not by taking anyone's word for it.
  • A hand-coded static site is portable by design: domain in your name, files handed over, hosting you can move.
  • Before any new build, get in writing that the domain, files, and logins are yours with no hostage clause.

WHERE THIS LEADS

Put this to work.

STRAIGHT ANSWERS

Quick answers.

01I own my domain but the site is on Wix. Do I own my website?

You own the address, not the site. The pages, layout, and content are locked inside Wix, and there is no clean export you can move to another host. If you leave, you keep the domain and rebuild the site elsewhere.

02My old web guy disappeared and I cannot log in. Can I still get my domain?

Usually yes, if you can prove the business is yours. Contact the registrar the domain is with, or use ICANN's transfer-dispute process, and keep every invoice and email showing the domain was bought for your company. It can be slow, but a domain registered for a business you clearly own is recoverable.

03Is a hand-coded static site really something I can take with me?

Yes. It is plain HTML, CSS, and a little JavaScript in a folder, with nothing proprietary to get trapped in. You get the files at handoff, the domain stays in your name, and the whole thing can move to another host by pointing the domain, no rebuild required.

04What is the one thing I should check before hiring anyone to build a site?

That the domain will be registered in your own account under your name and card, and that you get the finished site files at the end. If a builder will not put both in writing, walk. Those two things are the difference between owning a site and renting one.

WANT THIS HANDLED FOR YOU?

Not sure what you actually own?

We will do a free look at your domain, hosting, and files and tell you plainly what is in your name and what is not. Call (407) 705-2452 or book a strategy call, no obligation to build with us.

Start With the Free Audit
Call (407) 705-2452 Text