Website Ownership Handover: What You Must Control Now

Table of Contents

Want to get professional advice?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Table of Contents

Every business website has a few parts that matter more than the design: the domain name, the hosting account, the admin access and the accounts around the site. If those parts are controlled by the business, switching supplier is annoying but possible. If they are controlled only by the person who built the site, every future change depends on them.

This is rarely malicious. Most ownership problems happen because nobody asked the question at the beginning. The developer registered the domain, opened the hosting account, connected Analytics and kept the original admin user. The site launched, everyone moved on, and the business only discovers the problem when it needs a change.

The four things your business should own

The first thing is the domain. This is the address people use to reach the site. It can be managed by a supplier, but it should be registered to the business or to the business owner, with an email account you control.

The second thing is hosting. Hosting is where the website files and database live. Your supplier can manage the server, updates and performance, but the account should still be tied to the business rather than to an agency account you cannot access.

The third thing is administrator access to the website itself. On WordPress, that means an administrator user on an email address controlled by the business. A shared login or a login owned by the supplier is not enough.

The fourth thing is the surrounding access: Google Analytics, Search Console, DNS, email routing, backups, plugin licenses and any paid tools connected to the site.

How to check the domain

Start with the domain registrar. If you know where the domain was bought, try to sign in with the business email address. If you do not know, a public lookup can usually show the registrar, even when personal details are hidden.

Hidden owner details are normal and often good for privacy. The important question is not whether your name is visible in a public lookup. The important question is who can sign in, renew the domain, unlock it, change nameservers and approve a transfer.

If nobody in the business has that access, ask for it before you need it. Domain recovery is much easier when the relationship with the current supplier is still good.

How to check hosting and backups

Hosting ownership is usually easier to check. Ask which company hosts the site, which account pays for it and who receives billing or downtime notices. If the invoice is paid from the supplier’s card and you cannot sign in, the site is effectively sitting in someone else’s account.

That is not always a problem when the supplier is actively managing the site. It becomes a problem when the business wants to move, audit performance, change DNS or recover from an outage.

Backups need a similar test. Do not only ask whether backups exist. Ask when a backup was last restored successfully. A backup that has never been tested is a hope, not a recovery plan.

What to ask before handover

A clean handover is a written list, not a vague promise. Ask for the domain registrar, hosting provider, DNS manager, WordPress admin user, backup location, Analytics property, Search Console property and plugin license ownership.

You do not need to manage all of this yourself every day. In fact, many businesses should not. A good technical partner can keep managing the stack. The difference is that the partner manages accounts that are accountable to the business.

For ongoing hosting and maintenance, see our managed hosting plans. For migration work, see migration to WordPress.

Warning signs

The biggest warning sign is resistance to basic access questions. A professional supplier may explain why some access should stay restricted for safety, but they should still be able to show who owns each account and how handover would work.

Other warning signs include a domain registered to a personal email address, a single shared admin login, no written backup policy, no Search Console access and no clear list of paid tools.

None of these means the website is broken today. They mean the business has operational risk. The fix is usually simple when handled early and painful when handled during an emergency.

What a healthy setup looks like

In a healthy setup, the business owns the assets and the supplier owns the responsibility for keeping them working. The business can invite or remove users, see billing, approve transfers and recover the site if needed.

The supplier still does the technical work. The business does not need to become a hosting expert. It only needs enough ownership to avoid being trapped.

At Digitizer, we prefer this model because it creates a better relationship. Clients stay because the work is good, not because the keys are locked away.

Need a clean handover?

If you are not sure who controls your domain, hosting, backups or website admin access, talk to Digitizer. We can audit the setup, explain the risks and help you move to a cleaner ownership model.

The domain should be registered to the business or business owner, with an email account you control. A supplier can manage it, but the business should be able to renew, transfer and recover it.
No. Managed hosting is normal. The problem starts when the business has no visibility, no billing trail and no way to move or recover the site if the relationship changes.
Ask for domain registrar access, hosting account information, WordPress administrator access, backup location, DNS access, Analytics and Search Console access, and a list of paid tools or licenses.
No. The business should own the accounts, but a technical partner can manage them day to day. Ownership and management are not the same thing.
Start by documenting what you do have. Then ask the current supplier for a written handover list. If that fails, a technical audit can map the site, domain, DNS and hosting so you know what can be recovered.

About the author

Ben Kalsky, Founder & Partner at Digitizer

Ben has 15+ years of experience building websites for technology companies, e-commerce businesses, and service providers across Israel and internationally. As co-founder of Digitizer, he’s delivered over 100 projects ranging from ₪5,000 landing pages to ₪100,000+ enterprise platforms.

Notable work includes:

  • Building platforms for companies later acquired by Fortune 500 firms (CrowdStrike, Nvidia)
  • Migrating 50+ businesses from proprietary platforms to WordPress, saving an average of ₪80,000/year in platform fees
  • Managing infrastructure for 100+ websites with 99.9% uptime over 3 years

Ben leads AI implementation and autonomous systems for business, and builds the infrastructure underneath – WordPress, WooCommerce and integrations. His approach: practical, process-based solutions that drive measurable business growth – no buzzwords, no vendor lock-in.

On Digitizer’s blog, he shares real-world insights on website pricing, platform selection, and avoiding costly mistakes when building digital infrastructure.

Share the article

Copy

More articles