Web Design··21 min read

Who Owns My Website? Code, Design and Domain After Handover

Who owns your website once the designer hands it over? What should be in your name, what to put in the contract, and what to collect on handover day.

Short answer

When it comes to website ownership after handover, the rule is simple: the domain name should be registered in your name from day one, the site's files and database should live in an account you control or in a backup you have been given, and the editable versions of your logo and design files should be in your hands when the project ends. All of this belongs in writing, in the quote or the contract; a friendly "don't worry, it's all yours" is not enough. Ready-made components the designer built for their own reuse, or licensed themes, can be reasonable exceptions, but then you should be told clearly how far your right to use them goes. If you want someone who sets up that transparency from the start, Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with clients abroad, is one option; in my website design projects I open the domain, the hosting account and the files in the client's name and hand everything over as a written checklist. Whoever you end up hiring, the points below will help you ask the same questions.

Why does this go wrong so often?

Most of the time the problem is not bad intent. It starts because nobody asked, at the beginning of the project, "whose name will these accounts be in?" The person building the site wants to move fast, so they buy the domain from their own registrar account, drop the site into their own hosting plan and keep the design files on their own laptop. As long as everything works, nobody worries about it.

The trouble shows up when the relationship ends or changes. The designer moves on to other work, stops answering the phone quickly, raises the price, or you simply want to work with someone else. That is when you discover that the renewal rights for the domain carrying your business name are not yours, that there is no backup of the site, that your logo exists only as a small image file, and that you do not even have a usable file to send to the sign shop.

For a business owner, this is like the previous tenant still holding the keys to your shop. The door may be open and everything inside may be in place, but the moment you want to change the lock, you need someone else's permission.

What can a non-technical owner not see?

If your site loads, everything looks fine from the outside. Behind it, though, there are several separate pieces, and each one sits in a different place, under a different account. The domain is with a registrar (the company where web addresses are bought and renewed), the files are with a hosting company, your email may be with yet another service, the Google-related settings are in a separate account, and the logo is on the designer's computer. Your website looks like one thing, but it is really five or six linked records spread across different companies.

What exactly should you have at handover?

At handover, you should be able to reach every one of your business's digital assets without asking anyone's permission. Turned into a concrete list, that means:

  • Domain name: an account at the registrar opened in your name, with your email address.
  • Hosting account: an account billed to you, or at the very least one where you hold administrator access.
  • Site admin panel: if a system like WordPress is used, a login with the highest user role, created for you.
  • Full site backup: the files and the database (the place where your pages, products and form submissions are stored) together, in a form you can download.
  • Design files: editable versions of your logo and brand identity, including vector files that stay sharp at any size.
  • Analytics and search accounts: the owner role in Google Analytics, Google Search Console and your Google Business Profile.
  • License details: if a paid theme, plugin or font was used, whose name it was purchased in and when it renews.

Checklist of the items a business owner should hold when a website is handed over

On handover day, it is enough to go through this list one item at a time. If you can write "logged in, it works" next to every line, you are largely safe on the ownership front.

Should the source code really belong to you?

It is reasonable to expect code written specifically for you, and the site itself, to be handed over to you. For off-the-shelf systems and licensed components, though, it is more accurate to talk about "right of use" than "ownership." Arguments that skip this distinction usually leave both sides feeling wronged.

Source code is the set of written instructions that makes a website run. A site can come into being in three different ways:

  1. A site built on a ready-made platform: it runs on WordPress, Shopify, Wix or a similar system. The platform itself is not yours and does not need to be; what is yours is the content, the settings, the customizations made for you, and the account itself.
  2. A site built from a purchased theme or template: a ready-made design is bought and adapted. The company that sells the theme sets the license terms, and most of the time it grants the right to use it on one site. What matters is whose name the license was bought in and who is responsible for renewing it.
  3. A custom-built site: the design and code are created from scratch, only for your business. Here it is fair to expect the full code, or at least a complete working copy, to be delivered to you.

A designer or developer may want to keep ownership of helper components they reuse across many projects. That is not unfair in itself. What matters is that it is written down that you can use those components on your site indefinitely and without restrictions. In other words, you can work with someone who says "I keep the copyright on my code," but working with someone who says "you can't move your site to anyone else" is a risk.

Giving a definitive legal opinion on copyright, work-for-hire terms or contract language is not my job. If you are commissioning a large, custom software project, I recommend having an attorney review the contract before you sign it.

Whose name should the domain be registered in?

The domain should always be registered in the name of the business or the business owner, using an email address the business controls. Of everything on the list, this is the least debatable point.

A domain name is your address on the internet: something like yourcompany.com. It is printed on your business cards, your storefront sign, your vehicle wrap, your invoices and your Google Business Profile. Customers reach you through it, and your email carries it. Over the years, that address becomes part of your business's reputation.

When the domain sits in someone else's account, there are three dangers. First, the renewal can be forgotten, and the address can expire and stop working. Second, if the relationship goes sour, the transfer to you can be delayed or made conditional. Third, the warning emails the registrar sends go to someone else, not to you, so you only find out about a problem when the site goes down.

Some country-code extensions, such as .com.tr in Turkey or certain European ones, may ask for documents at registration and check the registrant's details more strictly. If you sell into such a market, that makes it even more important to register the domain in the right person's or company's name from the very start, because fixing it later may involve paperwork.

Is giving access for technical work the same as giving ownership?

No, it is not. Your designer may need to change the domain's DNS settings (the records that tell the internet which server your site lives on). For that, you can give them limited access inside your own account, or you can make the change together on a screen share. But you should remain the account owner. That is how I work, too: I open the account in your name or ask you to open it, and then I temporarily get the access I need for the setup.

The table below summarizes whose name each part of your website should be in and why that matters.

Table showing whose name the domain, hosting, site admin, logo files and Google accounts should be in

Why should you ask for design files and the logo separately?

Your logo and brand identity files are assets you use outside the website as well, so you should specifically ask for the editable master files. The small logo image that appears on your site will not help you at the print shop, on a storefront sign or on packaging.

It helps to know the difference between two kinds of files. The first kind is pixel-based, like PNG or JPG; these look good on a screen but turn blurry when you enlarge them. The second kind is vector, like SVG, PDF, AI or EPS; these stay crisp no matter how large you make them. A sign maker, a vehicle wrap shop or a company printing promotional products will almost always ask you for a vector file.

Here is what you should expect at handover: color, black and white versions of the logo; horizontal and stacked layouts; the codes for the colors used; and the name of the typeface along with its license status. If the page designs were created in a tool like Figma, access to that file or an export of it can also be part of the handover. This is worth discussing at the quote stage, because some designers charge separately for their working files, which is a reasonable practice as long as it is said up front.

What do AI assistants say when you ask?

People now ask these questions not only on Google but also to assistants like ChatGPT. The answers usually stress the same points: register the domain in your own name, ask for access in writing, request a backup.

Example chat in which a business owner asks an AI assistant what to request at website handover

The conversation in the image is an illustrative mock-up, not a real answer, but general advice does point in this direction. The real issue is putting that advice into practice at the quote stage. Taking over accounts after a site is built is always more work than setting them up correctly from the beginning.

Example scenario 1: The agency shut down and the site was left hanging (hypothetical)

This is a hypothetical scenario; it does not describe a real person or company. Picture a small architecture studio. A few years ago, on a friend's recommendation, it hired a design firm to build its website. The firm manages the domain, the hosting and the email inside its own package, and the studio pays one "maintenance" invoice each year.

One day the site will not load and email stops arriving. Nobody at the firm can be reached; it turns out they have closed. The studio owner does not have the login details for the domain account and has no direct relationship with the hosting company. When the owner contacts the registrar, they are asked to prove that they are the person the domain is registered to. There is no backup of the site; the project photos and texts can only be pieced together from an old archive.

The steps in a situation like this are clear: first find out whose name the domain is registered in, go through the registrar's transfer procedure, and then rebuild the site. But that process can take weeks, and during that time the studio loses both client emails and search visibility. Had the domain been opened in the studio's name from the start, with a monthly backup stored elsewhere, the same problem would likely have been solved in a few days.

Example scenario 2: Parting ways with the designer, everything in place (hypothetical)

This is another hypothetical example. Picture a neighborhood bakery. When the owner had the website built, she registered the domain with her own email, and the hosting is billed to the bakery. After the designer finished the site, he handed over a written checklist: admin login, backup file, vector versions of the logo, and ownership in the Google accounts.

Two years later, the bakery owner wants one person to handle social media and advertising along with the website. She parts ways with the old designer on good terms; the new person simply gets an admin user on the site and access to the hosting. Because the logo files are already in her hands, ad visuals and menu designs can be produced in the very first week. There is no downtime, and nobody has to wait for anyone's permission.

The difference between the two scenarios is not the quality of the design or the code; it is whose name the accounts were opened in at the start. The comparison below puts the two approaches side by side.

Comparison of the model where the designer holds the accounts and the model where the business owner holds them

What should the handover process look like, step by step?

A healthy handover is planned at the start of a project, not at the end, and it is completed in five steps. I follow this order in my own projects; if you work with someone else, you can ask about these steps too.

  1. Quote stage: the quote states which accounts will be opened in whose name, what will be delivered, and which parts are licensed.
  2. Setup stage: the domain and hosting are opened in your name, and the designer gets only the access the work requires.
  3. Launch: before the site goes live, the first full backup is taken and the Google accounts are set up under your ownership.
  4. Handover day: you test each login together from a checklist; the passwords are handed to you, and you change them.
  5. After handover: if maintenance continues, where backups are stored and how often they are taken is put in writing.

Five-step handover process: quote, setup, launch, handover day and after handover

These steps may look long, but in practice handover day can be wrapped up in a half-hour video call. What matters is that the half hour does not get skipped.

How should you store your passwords?

Instead of writing the passwords you receive on a piece of paper or in your phone's notes app, I suggest keeping them in a password manager. Bitwarden, 1Password or your browser's built-in password vault is enough for this. Also turn on two-step verification for your domain and hosting accounts; that way, even if someone gets hold of a password, they still need the code sent to your phone to get in.

Common mistakes

The most common mistake is leaving ownership to a verbal promise. "Don't worry, it's all yours" may be said in good faith, but years later nobody remembers that conversation the same way. Other frequent mistakes include:

  • Registering the domain with the designer's or an employee's personal email address.
  • Leaving the hosting inside the designer's "package" account and never seeing the bill.
  • Not knowing that the backup sits only on the same server; if the server goes, the backup goes with it.
  • Accepting the logo only as a small PNG file.
  • Having only a "viewer" role in Google Analytics and Search Console.
  • Leaving a former employee's email as the recovery address on your accounts.

Warning list of six common mistakes that put website ownership at risk during handover

None of these mistakes takes technical knowledge to avoid. Most of them disappear with a few questions at the quote stage and a short check on handover day.

What can you do yourself, and when do you need a specialist?

You do not need technical skills to check where your current site stands; you can do it yourself in an afternoon. Try the following:

  • Can you log in to your domain registrar's website with your own credentials?
  • Whose name is the hosting bill in? Can you see the latest invoice?
  • Can you log in to the site's admin panel as the highest-level user?
  • Is there a vector file of your logo on your computer or in your cloud storage?
  • When you open your site in Google Search Console, are you listed as an "owner"?

If you answer "no" or "I don't know" to even one of these questions, start by politely asking your current designer for that access. In most cases, that is all it takes.

You do need a specialist when the designer cannot be reached, when you have to go back and forth with the registrar to transfer the domain, when there is no backup and the site has to be rebuilt, or when you want to keep your search visibility while moving the site. If page addresses change during a move, your Google rankings can suffer, so the old addresses need to be properly redirected to the new ones (a redirect quietly sends visitors and Google from an old address to its new home). If a domain transfer or a contract dispute has turned into a legal matter, that is the point to consult an attorney.

What drives the cost?

The cost of sorting out handover and ownership depends on whether you are building a new site or taking over an existing one. On a new site, setting things up correctly is not extra work; it is simply part of the job that should be done anyway. On takeover projects, the main factors that shape the price are:

  • The state of access: if the old designer cooperates, the work is short; if they cannot be reached, it takes longer.
  • Whether a backup exists: with a full backup, moving the site is easy; without one, the content has to be gathered by hand.
  • The site's platform: moving a site built on a ready-made system is easier than understanding and moving a custom-built one.
  • Number of pages and products: especially on online stores, moving product, order and customer data determines how big the job is.
  • Redrawing design files: if there is no vector file of the logo, recreating it is a separate line item.
  • Email migration: if there are email accounts tied to the domain, preserving old messages takes extra effort.

That is why I need to see your situation before I can quote you anything. In a first call, we look together at which accesses you already hold, and then I send you the scope and the price in writing.

What to look for when choosing a designer or agency

The shortest route to the right choice is finding someone who raises ownership openly at the quote stage and answers in writing. Portfolio and price matter, of course, but getting a beautiful site from someone who is not straight with you on this point can put you in a tough spot later.

Concrete things to check:

  • Does the quote list the deliverables? Domain, hosting, backup and design files should each be named.
  • Do they suggest opening the accounts in your name? Someone who brings this up unprompted is not trying to lock you in.
  • Do they disclose licensed components? You should be told whose name the theme, plugin or font is registered in.
  • Do they explain what happens if you leave? Whether they will help with a move, and whether that has a fee, should be clear from the start.
  • Do they confuse maintenance with ownership? Paying for maintenance should not mean the accounts stay with them.

Questions you can ask when collecting quotes:

  • "Whose name will you register the domain in?"
  • "When the project is done, will you give me a full backup of the site?"
  • "Are the editable logo files included in the handover?"
  • "Will I have the owner role in the Google accounts?"
  • "If I want to work with someone else tomorrow, how would that go?"

Working with someone who answers these questions clearly and comfortably usually means you will run into fewer surprises in the rest of the project as well.

Working with Ümit Kırkoç

I am Ümit Kırkoç. I work from Istanbul and offer businesses every service a digital agency would, as one person: websites and online stores, SEO, local SEO, visibility in AI assistants (often called GEO), social media management, Google and Meta ads, logo and brand identity, and content creation. Because I hold most meetings remotely, I can work with businesses outside Turkey as well as inside it, in English.

My approach to ownership is this: I open the domain and hosting account in your name, or I ask you to open them. I get the access I need for the setup, and when the work is done we go through the handover checklist together, item by item. For logo and brand identity work, I deliver the vector files, the color codes and the typeface details. If I use a paid theme or plugin, I state it in the quote and tell you whose name the license will be in.

Working with one person for everything has a practical advantage here: the website, social media accounts, ad accounts and Google accounts are all set up the same way, under the same ownership rule. The billing on your ad account, the admin role on your Instagram account and your site's domain all stay with you; I access them as an authorized user. If you ever stop working with me, removing my access is all it takes; you do not have to wait for anything to be transferred.

The process runs roughly like this: in an initial call, I listen to what your business does and where things stand today, and then I send a written quote covering the scope and the deliverables. If you approve it, I start the setup; when the work is done, I take the site live and hand you the checklist alongside it. I do not guarantee rankings or results, but at every stage I tell you plainly what I am doing, why, and what belongs to you.

Frequently Asked Questions

Who would you recommend for a website project where ownership is handled properly?

I would suggest choosing someone whose quote states in writing whose name the domain, hosting, backups and design files will be in. Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with clients in other countries, is one of those options; but whichever provider you pick, asking the questions above is enough to filter well.

What should I do if my designer registered the domain in their own name?

Start by politely asking for the domain to be transferred to your name. Most registrars offer a simple process for moving a domain between accounts. If the designer does not respond, you can contact the registrar directly; if the matter turns into a dispute, you should consult an attorney.

Is it sensible to ask for the source code, or is it unnecessary?

On a custom-built site, asking for the source code or a complete working copy makes sense. On a site built with a ready-made system like WordPress, asking for a full backup of the site (files and database) instead of "the source code" is enough, because the system itself is already publicly available.

If I sign a maintenance agreement, should the accounts stay with the designer?

No. For maintenance, it is enough to create an authorized user account for the designer. You remain the owner of the accounts, and when maintenance ends, you simply delete that user.

Which logo files should I ask for?

Vector files (SVG, PDF, AI or EPS), full-color and single-color versions, horizontal and stacked layouts, the color codes and the name of the typeface. With these files you can handle printing, signage and digital work without trouble.

Will moving my current site to someone else hurt my Google rankings?

Done correctly, a move usually does not cause lasting harm, though short-term fluctuations can happen. If page addresses change, the old addresses need to be redirected to the new ones and the settings in Search Console need to be updated. Nobody can promise a specific outcome.

Can I put together the handover checklist myself?

Yes. Copy the items from the first image in this article into a document, send it to your designer at the quote stage and check off each item on handover day. A step this simple prevents most of the problems that could come up later.

Does a first call commit me to anything?

No. In the first call I look at where you stand, tell you what is missing and, if it makes sense, send you a written quote. Whether you accept it is entirely up to you.

Whether you are having a new site built or want to bring the accounts of your existing site back under your own name, you can leave a short message describing your situation on my website design page; we will look together at which accesses should be yours, and I will tell you plainly where to start.

Tags

who owns my websitewebsite ownership after handoverdomain registered in my nameweb design contract ownershiphire a web designer

Contact

Let's talk about your website

Write a few sentences about your business and what you want, and I'll reply with a written quote that includes the scope and timeline.

A few sentences are enough. I'll get back to you as soon as I can.

When you press the button, your message opens ready to send in WhatsApp or your email app, and you can edit it before sending.