Ownership
Who owns your website? Five questions to ask before you rebuild
6 August 2026 · 5 min read · ENGIS Studio
Before any rebuild, there is a question that matters more than design, features or price: who actually owns what you already have? Not morally — literally. Whose name is on the domain, whose account holds the hosting, and who can take the whole thing away by ignoring an email.
We check this at the start of every engagement, because the answers change what is possible. Here are the five questions, where to find the answers, and what "good" looks like for each.
1. The domain
Your domain is the one asset that cannot be rebuilt — lose it and you lose your email, your search history and every link anyone has ever shared. Look up your domain on a WHOIS service or, for .au domains, the auDA registrant search. The registrant should be your business entity, not a web company, not a former employee’s personal email.
If it is registered to someone else, fixing that is the first job — before any rebuild, before anything. A cooperative transfer takes days. An uncooperative one can take much longer, which is exactly why you do it while relations are good.
2. The hosting
Hosting in someone else’s account is a tenancy where the landlord holds your furniture. It works until you want to leave, renegotiate, or the provider disappears. You should hold the hosting account in your own name, with your own billing, and grant your developer access — not the other way around.
The monthly invoice is the tell: if you pay a web company a bundled fee and have never seen the underlying account, you are renting access to your own website.
3. The source code
Ask one question of whoever built your site: "If we parted ways tomorrow, what exactly would you hand over, and could another developer work from it?" A good answer names a repository you can be given access to. A bad answer involves a proprietary page builder, an export that is not really an export, or silence.
Our own answer is published in our terms: at final payment, the repository, the design work and the accounts transfer to the client, and nothing stops them taking it elsewhere. We publish that because we think it should be the industry’s default, not a premium feature.
4. The content
Photography, copy, logos, videos: who holds the originals, and who holds the rights? Commissioned photography is frequently licensed to the agency that arranged it rather than assigned to the business in it. Copy written "for" you may live nowhere except inside the CMS it was typed into.
Keep originals in storage you control, and make sure contracts assign rights to you. If your current site is the only place your content exists, back it up this week — before a rebuild, a lapsed subscription or a hack decides the matter for you.
5. The measurement
Analytics accounts are the least dramatic item on this list and the most commonly lost. Years of data about how customers actually find and use your site — gone, because the account belonged to an agency that moved on. Check that analytics properties are owned by your organisation and that agency access is granted, revocable, and yours to control.
The same applies to your search-engine console accounts, tag containers and advertising accounts. Ownership first; access second; never the reverse.
The one-line test
If every professional relationship around your website ended tomorrow, could you — without anyone’s permission — keep the domain, move the hosting, hand the code to a new developer, keep every word and image, and keep the data? If the answer is yes five times, you own your website. Anything less, and part of your business is on loan.
None of the five fixes requires a rebuild. Do them first, and any rebuild you choose later — from anyone — starts from a position of strength.
Ownership is not a feature you buy at the end. It is the condition you insist on at the start.