Website ownership: questions to ask before signing

Start with the domain name

The legal registrant and renewal contact should be clear. Ideally, the business has direct visibility of the domain account even when the web provider manages the technical settings.

Check which email address receives renewal notices and what happens if the working relationship ends. A website can be rebuilt; recovering an uncontrolled domain can be much harder.

Separate content, design and code

The business normally retains rights to material it supplied, such as photographs, logos and approved written content. The provider may use licensed systems, frameworks or reusable components that cannot be transferred as exclusive intellectual property.

A fair agreement explains the difference between owning the completed site and owning every underlying tool used to create it.

Understand pay-monthly arrangements

Some monthly plans are website rental. Others spread the build cost over an initial term and then continue with hosting and care. Neither model is automatically wrong, but the agreement should state when ownership transfers and what payments remain due.

Ask whether early settlement is possible and whether a release fee applies in addition to the remaining agreed balance.

List the accounts the website depends on

Record who owns each account, who has administrative access and which subscription the business must continue paying.

• Domain registrar
• Hosting platform
• Business email
• Analytics and Search Console
• Google Business Profile
• Booking, payment or e-commerce systems
• Email marketing and CRM
• Image, font or software licences

Ask what a transfer actually includes

A transfer may involve moving a repository, exporting content, changing DNS, handing over accounts or rebuilding parts that depend on the provider’s private systems. Ask what format will be supplied and whether another competent developer can use it.

Agree who pays third-party migration costs and how much notice is required.

Check responsibilities after handover

Once hosting or code moves, the original provider may no longer be responsible for updates, security or problems caused by the new environment. That boundary should be documented.

The business should change passwords, remove old access where appropriate and confirm that forms, email and renewals still work.

Put the important answers in the contract

• Who owns the domain?
• When does the completed website transfer?
• Which third-party licences are non-transferable?
• What is the minimum payment term?
• What happens when support is cancelled?
• What files, content and access will be supplied?
• Are there migration or release charges?