Website Contract and Ownership Terms: What to Check Before You Sign

Before you sign a web design or development contract, confirm six things: the scope is described in detail, payments are tied to milestones, you own your domain and hosting accounts, the contract states who owns the design, code and content once you pay, there is a clear way to end the agreement and recover your files, and ongoing fees and renewal terms are written down. Many disputes between businesses and web providers come from missing or vague terms rather than bad faith. This guide explains each term in plain language and shows what to look for.

1. Scope of work

The scope lists exactly what the provider will build and deliver. A strong scope names the number and type of pages, features, integrations, content responsibilities, browsers and devices to support, and any deliverables such as training. Weak scopes use phrases such as "full website" or "all necessary pages," which invite disagreement.

Look for a section that lists exclusions. If something matters to you, such as copywriting, search setup, accessibility checks or data migration, it should either be in the scope or be explicitly excluded with a price.

2. Price, payment schedule and extras

Contracts normally set a total price and a payment schedule. A common structure is a deposit at signing, one or more milestone payments and a final payment at launch. Check:

• The amount and trigger of each payment.
• Whether the final payment is released before or after you receive all logins and files.
• The rate for work outside the scope, such as an hourly rate for changes.
• Late-payment fees and what happens if either side pauses the project.
• Whether recurring charges, such as hosting or maintenance, are separate.

Avoid paying the entire fee before any work is delivered. Paying in stages keeps both sides motivated.

3. Revisions and approvals

State the number of design revision rounds included and how feedback is submitted. Define what counts as a revision versus a new request. For example, changing colors is a revision, while adding a new page is a change in scope. Contracts often say that approval of a design milestone means later changes are billable. Understand this before you sign off on anything.

4. Ownership of the work

Intellectual property is the term that surprises people most. In the United States, copyright in custom work generally belongs to its creator unless the contract assigns it or the work qualifies as work made for hire under the Copyright Act. For independent contractors, a written agreement is usually needed to transfer ownership. If your contract is silent, the developer may keep the copyright and you may hold only an implied license. The U.S. Copyright Office provides general information on ownership and transfers.

Check these items:

• Design and code. Does ownership transfer to you on final payment, or does the provider retain it and license it to you?
• Content. You should own text and images you provided, and the provider should confirm that anything they add is original or properly licensed.
• Third-party components. Themes, plugins, fonts and stock images carry their own license terms. These are often licensed, not owned, and may require renewal fees.
• Portfolio rights. Providers commonly ask to show your site in their portfolio. That is usually fine, but you can negotiate it.

5. Domain, hosting and account ownership

Your domain name and accounts should be registered in your name, with your email address as the primary contact. If a provider registers the domain for you under their own account, you may have trouble moving it later. For hosting, the same principle applies. Even if the provider manages it, you should be listed as the account owner or hold admin access. Ask for all credentials at launch, including website admin logins, hosting, domain registrar, analytics and any third-party tools.

6. Hosting, maintenance and support terms

If the provider hosts or maintains your site, the contract should say:

• What is included: updates, backups, security monitoring, edits, support hours.
• The monthly or yearly fee and how it may change.
• Response time targets and how to request support.
• The minimum term and how to cancel.
• Whether you can move the site away and any fee for doing so.

A subscription that appears inexpensive monthly but locks you in for 36 months with a termination fee is a significant financial commitment. Multiply the monthly fee by the number of months to see the real total.

7. Warranties and bug fixes

Many contracts include a short warranty period after launch, during which the provider fixes defects at no charge. Check how long it lasts and what is covered. Defects are things that do not work as specified, not new features you decide to add later.

8. Confidentiality, data and privacy

If the site will collect personal information or the provider will access customer data, the contract should address confidentiality and how data is handled. If you collect personal data, you may have obligations under state privacy laws or industry rules. Ask the provider how they protect your data, and consider a data processing clause in higher-risk projects.

9. Limitation of liability and indemnity

Many contracts limit the provider's liability to the amount you paid. That is common, but read it, especially if the site is central to revenue or handles sensitive data. Indemnity clauses require one party to cover the other's legal costs in certain situations, for example if the content you supplied infringes copyright. These are good topics for legal review.

10. Termination and exit

A good contract lets either party end the agreement under defined conditions and explains what happens next. Look for:

• Notice periods.
• Payment for work completed up to termination.
• Delivery of files, source code and credentials upon payment.
• Transition help and any fees.
• What happens to your site if the provider closes.

11. Dispute resolution

Contracts may require mediation or arbitration, name a state whose law applies, or set where lawsuits must be filed. These terms affect how costly a dispute would be. If you are in a different state from the provider, consider whether the chosen venue is practical.

Contract term checklist

Worked example: the cost of an unclear exit

A business signs for a $1,500 site with $99 a month hosting and support for a 24-month minimum. The agreement says the provider owns the code and will "make the site available while the subscription is active." After 8 months, the owner wants to switch to another provider. The early termination clause requires payment of the remaining 16 months, which is 16 x 99 = $1,584, and the owner cannot take the code. The total spent for a site that must be rebuilt is $1,500 + 8 x 99 + $1,584 = $3,876. A $3,000 site with clear ownership could have been cheaper. These figures are illustrative, but the structure is common enough to warrant careful reading.

Practical steps before signing

1. Read the entire contract, not just the price page.
2. Ask the provider to explain any term you do not understand and to put changes in writing.
3. Keep copies of all agreements, proposals and emails.
4. Confirm that the person signing for the provider has authority to do so.
5. Keep a document with all accounts and logins.

When to consult a professional

Consult a licensed attorney for contracts above a budget you are not comfortable losing, any unusual intellectual property or liability terms, and projects that involve regulated data.

Frequently asked questions

Do I need a lawyer for a small web project?

Not always. For a simple, low-cost project with a clear scope, careful reading may suffice. For larger or riskier projects, a short review is worth the cost.

Can I own the code if I use a website builder?

Typically not. Builders license you the service, and you cannot usually export the underlying code. Content and images can often be exported.

What if the provider will not put ownership in writing?

Treat that as a serious red flag, and consider another provider.

Does paying in full mean I own everything?

Only if the contract says so or the law provides it. Do not assume.

Sources

• U.S. Copyright Office — information about copyright ownership, work made for hire and transfers.
• Federal Trade Commission — business guidance on contracts and consumer protection.
• ICANN — domain registration and registrant information.