Do You Actually Own Your Website If Someone Else Built It?

You asked a reasonable question and it went quiet. Maybe you asked for the logins, or for a copy of everything, or just said you were thinking about working with someone new. What came back was vague, or partial, or nothing at all. That is usually the moment this question arrives: do I own my website if someone else built it, and what happens if the answer is no. The unsettling part is realising that "my website" was never one thing. It is a domain registration, a hosting account, a platform login, the code and design, the words and pictures, and the measurement accounts that hold years of history. Any one of those can sit in an account belonging to somebody else, and each one has its own paperwork. The good news is that this is a short list of separate checks rather than one enormous unknown, and most of it you can work through today without asking anyone's permission.

The fear underneath the practical questions is rarely about a website at all. It is that years of monthly payments never bought the right to leave, and that going might cost you the web address customers already know, the email attached to it, or search history that took a long time to build.

Worth saying plainly: discovering you do not control every piece is common, and it is usually fixable. It is not evidence that you were cheated. Websites get built quickly, accounts get opened in whoever's inbox was closest at the time, and nobody writes down which is which. Years later that becomes a puzzle rather than a plot.

Two shortcuts are worth putting down now, because both will let you down at exactly the wrong moment. The first is "I paid for it, so I own it." Paying an invoice does not by itself identify who holds the copyright in every element or who is the account holder for every service. The second is "the host will sort it out." A host or platform can help with documented account recovery, and it will not decide a private dispute about who owns what. On one major platform, for example, only the current site owner can transfer ownership, which is a platform rule about permissions rather than a ruling on your contract.

That leaves the approach that does work, which is unglamorous: go asset by asset, and check the paperwork and the account holder for each.

Treat these as separate rows in a list, because that is what they are.

Your domain registration is your address. ICANN describes the registrant as contracting with a registrar and managing the domain through that registrar, which makes the registrar the place where control actually lives.

Your hosting or platform account is where the site runs. Being able to edit pages is a role, not ownership; on many builders an editor cannot transfer the account or connect a domain.

The code and design are copyright, and copyright follows the rules below rather than the invoice.

Your content is the words and images, some of which may be licensed rather than owned, especially stock photography, fonts and plugins.

Your measurement accounts, meaning Search Console, Analytics, Tag Manager and your Business Profile, hold history that nothing can rebuild retrospectively.

Your email, if it runs on the same domain, moves when DNS moves, which is why it belongs on the list even though it feels separate.

The reason to keep them apart is that the answer genuinely differs. You can own the business, pay every invoice, and still be unable to move one particular asset without someone's cooperation, and knowing which one changes what you do next.

None of this requires a conversation with your current provider, and none of it changes anything.

Start with the domain, because it is the one that can take you offline. Use ICANN Lookup to find which registrar holds it, then try signing in to that registrar directly with your own email. If you can, check the registrant details, the recovery email, whether two-factor is on, the renewal card and the lock status. If you cannot sign in, you have learned something specific and useful rather than something vague.

Then check your measurement accounts, because they hold the thing you cannot recreate. In Search Console, look at whether you are a verified owner or only a user, and review which verification tokens are still active. Google is explicit that a verified owner can add and remove users and that access disappears for everyone if all verified owners lose it. In Analytics, check whether access sits at account or property level. A Viewer can export a report, and a report export is a copy of some numbers rather than control of the account.

Then the platform or hosting account, checking whether the account email is one you control and whether you can invite and remove administrators. Then the files and licences: where the source files live, and what was licensed rather than bought.

Write it down as you go, one row per asset, with the account holder, the billing payer, the recovery email and how you would export it. That list is the whole thing. Most owners can answer the first two rows within a few minutes.

Copyright is the part people guess at most, and it is more knowable than it looks.

Under 17 U.S.C. section 201, copyright initially belongs to the author of the work. There is an exception for work made for hire, and the Copyright Office's Circular 30 sets out that for a specially ordered or commissioned work it applies only when all the stated requirements are met, including that the work falls in an eligible category and that there is a signed written agreement expressly calling it work made for hire. A website is not named as one of those categories. So, a commissioned site is generally not work made for hire by default, which means the transfer has to be written down to exist.

That sounds alarming and usually is not, because a durable licence may be all your business actually needs. Being able to use, edit, host and move your site indefinitely covers most real situations. What matters is that the position is written somewhere rather than assumed by both sides in different directions.

Your agreement should carry an asset schedule listing what is assigned, what is licensed, and what is excluded because it belongs to someone else, such as a stock photo, a font, a plugin or a mapping service. In Texas, Business and Commerce Code Chapter 322 means an electronic record or signature is not denied legal effect merely for being electronic in covered transactions, so an emailed and signed agreement is not automatically weaker than paper. None of that decides a dispute, and a genuine disagreement about a contract needs a Texas attorney rather than an article.

Sequence matters here more than speed, because the least reversible steps are also the ones that can take your site or your email down.

Freeze the facts first. Record every URL, the current redirects, DNS records, email routing, measurement IDs, verification methods, invoices and where the source files sit. Change nothing yet, and delete no verification tokens.

Add your own access before anyone loses theirs. Become a verified owner in Search Console and an administrator on the accounts you can, so the business is never relying on a single departing account holder. Then ask for a written, asset-by-asset exit position rather than a general reassurance.

Build and test the destination privately. Then move the least reversible controls last: domain transfer and DNS changes only after you know the recovery email, the two-factor method, the registrar lock status and the renewal details.

Two timing traps are worth knowing before you start, because both are documented and both surprise people. A registrar that does not let you generate your own AuthInfo code must provide one within five calendar days of a request. And a change of registrant can trigger a lock of around 60 days in the circumstances ICANN describes, which is why updating your contact details the week before a planned move is the wrong order.

Remove old access only after everything is accepted and checked, not on the day you launch.

If your addresses stay the same, most of this risk disappears. That is worth asking about early, because moving hosting while keeping your URLs is a smaller job than changing domains, and the two often get bundled together without anyone deciding to.

Where addresses do change, Google's site move guidance is the thing to hold your project against. Map old URLs to new ones, redirect each page to its real replacement, submit the new sitemap, and monitor both properties afterwards. Google says significant changes can cause temporary fluctuation while pages are recrawled, that a small or medium site can take a few weeks or more for most pages to move across, and that redirects should generally be kept at least a year.

The mistake to avoid is sending lots of unrelated old pages to your home page. Google warns this can be treated as a soft 404, and it tells a visitor the same untrue thing. A page that genuinely no longer exists should return a real 404 or 410 instead.

No representative price survey exists for recovering ownership or moving a site after a dispute, and a figure presented as a standard rate is invented. The label covers wildly different jobs: account recovery, legal review, recreating a site from scratch, copying assets you are permitted to copy, URL mapping, ecommerce, email and analytics repair.

What is published is narrow and worth knowing. Registering a copyright claim with the U.S. Copyright Office through the electronic standard application is $65, which registers a claim rather than proving your business controls the accounts.

What moves your own number is the inventory: how many URLs, how much content has to be recreated rather than exported, whether ecommerce or memberships are involved, whether email moves, and whether anyone is being uncooperative. The cheapest version is the one where you already control the domain and the addresses stay put.

Sign in to the registrar itself rather than a dashboard your provider gave you, and confirm the registrant. Confirm you are a verified owner in Search Console under your own account. Export what you can from Analytics now. Take a copy of your content and images. Put two-factor on the accounts you control, using a business email that outlasts any one person.

Then stop. Do not change DNS, do not cancel hosting, do not edit registrant contact details, and do not delete anything from the old site. All four are easy to do, awkward to undo, and one of them starts a 60-day clock.

There is a useful exercise here even if nothing is wrong. Once a year, try to leave: sign in with your business email, identify your registrar, look at the administrator lists, download the exports, and confirm every account ties back to somebody inside your business. It takes an hour and it turns an unknown into a checklist.

There is no Texas filing that establishes ownership of an ordinary business website's domain, code, content, hosting or analytics accounts, and a Secretary of State business filing is not evidence that the filer controls those accounts. Anyone implying otherwise has misunderstood what those records do.

What Arlington does have is general small-business support. The City of Arlington's business pages and the Greater Arlington Chamber's business resources point to local advisers, and they are genuinely useful for the surrounding business questions. They will not settle a digital ownership dispute, and a real contract disagreement is a matter for a qualified Texas attorney.

I paid for my website. Doesn't that mean I own it?

Not automatically, and not every part of it. Copyright starts with the author under U.S. law, and a commissioned work becomes work made for hire only when it meets all the stated requirements including a signed agreement saying so. Payment is evidence of a deal, and the deal still has to be written down.

If I own the domain, do I own the website?

No, those are separate. A domain registration is your address, governed by your agreement with the registrar. The code, the content and the accounts are different assets with different paperwork.

My designer says the site is on their server. Is that a problem?

It is a question rather than a problem. Ask whether the account can be transferred to you, whether you can be made an administrator, and how you would export everything. Plenty of arrangements are fine; the ones that go wrong are the ones nobody wrote down.

Can I lose my email if I move my website?

You can, if your email runs on the same domain and the DNS records are changed carelessly. Identify your mail records before anything moves, and preserve them through the change.

Will moving cost me my Google rankings?

Not if your addresses stay the same, which is often possible. Where they change, Google's own guidance is to map every old URL to its real replacement, keep the redirects at least a year, and expect some temporary movement while pages are recrawled.

Should I register the copyright in my website?

It is optional, and the electronic standard application fee is $65. It registers a claim. For most owners, a clear written agreement and control of the accounts does more day to day.

What if my provider simply refuses to hand anything over?

Preserve the correspondence, do not make allegations you cannot support, and do not try to work around access controls. Get the asset register and the paperwork in front of a Texas attorney. A platform support ticket will not decide a copyright or contract question.

Ownership of a website is not one yes-or-no answer, which is exactly why it feels so unsettling when someone gives you a vague one. It is six separate checks, each with its own account holder and its own paperwork, and most owners can answer the first two, domain and hosting, in the time it takes to sign in and look. Where you find a gap, you now know the specific thing to ask for: a registrant transfer, verified ownership in Search Console, or a written statement about who holds the code.

Doing this once buys you more than an exit. It gives you a business asset you can actually move, price and hand to somebody else, and it turns your next website decision into a choice rather than a negotiation with your own history.

If you want a second pair of eyes on that asset register before you say anything to your current provider, we are glad to help. We are Arlington Website Designer, working out of Arlington, Texas and the surrounding Tarrant County towns, and nationally on search and writing work. We build sites our clients own outright, the domain, the content, the analytics and the code, in accounts that are in their own name, with no monthly platform rent. Have a look through the sites we have built, and when you are ready, get in touch and tell us what you have been able to sign in to so far.