Back to blog

Red Flags in Website Contracts

6/11/2026

The contract clauses that cost small business owners their sites, domains, and money: ownership ambiguity, hostage clauses, auto-renew traps, and vague scope.

A surprising amount of our work starts the same way: an owner calls us, not because they want a new website, but because they want their current one back. The designer disappeared. The agency won't hand over logins. The domain is registered to somebody's personal email. The monthly bill renewed for another year three days before they tried to cancel.

Almost every one of those situations was visible in the contract before anyone signed it. Not hidden, exactly. Just sitting there in language nobody read closely, because website contracts feel like paperwork and the demo looked great.

So here's the checklist we wish every owner had before signing anything. None of this is legal advice, and a lawyer reviewing a contract is never wasted money. But you can catch most of these problems yourself in fifteen minutes.

Red flag 1: Nobody says who owns the website

This is the big one, and it hides in silence. Many website contracts simply never state who owns the finished site. When ownership isn't written down, you're relying on goodwill, and goodwill has a way of evaporating exactly when the relationship goes sideways.

There are several things that can be "owned" here, and a good contract addresses each:

  • The domain name. This should be registered in an account you control, full stop. Not the designer's GoDaddy account, not the agency's "client portfolio." If a provider registers it for you as a convenience, the contract should say the domain belongs to you and will be transferred on request. Losing control of a domain you've printed on trucks and business cards is one of the most painful messes in small business web work.
  • The content. Your photos, your service descriptions, your reviews, your logo. These should be yours without question, but say so in writing anyway.
  • The design and code. This is where it gets genuinely murky. Some builders retain ownership of their code or templates and license them to you. That's not automatically a scam; it's how a lot of the industry works, including platform builders where you can never "take the site with you" at all. But you deserve to know which deal you're signing. The question to ask, word for word: "If we part ways in two years, what exactly do I walk away with, and in what format?"

If the answer is fuzzy, or the salesperson says "that never comes up," that's your answer. It comes up constantly.

Red flag 2: Hostage clauses

A hostage clause is any term that makes leaving so expensive or painful that you effectively can't. Some common forms:

  • Proprietary platform lock-in that nobody mentioned. The site only runs on the provider's system, so "leaving" means starting from zero. Again, platform builds aren't inherently bad, but undisclosed lock-in dressed up as a custom build is.
  • Exit fees and "site release" charges. A few hundred dollars to export your own content. A "buyout" to get your own domain transferred. If the contract charges you to take possession of things it elsewhere says you own, those two clauses are at war, and you should ask why.
  • Withholding logins. The contract never promises you admin access to your own hosting, domain, analytics, or Google Business Profile. Then one day you ask for them and discover access is a "courtesy" rather than a right. Get a clause that says you receive credentials, or at minimum that they'll be surrendered within a set number of days of any termination.
  • Work product held until final payment, forever. Holding work until you've paid is fair. Holding your domain or your content as leverage in any future dispute is not. The contract should distinguish between the two.

A fair provider makes leaving boring. That's actually a useful litmus test in the sales conversation: ask them to walk you through what off-boarding looks like. The good ones have a clear answer because they're not relying on hostages to retain clients.

Red flag 3: Auto-renew traps

Recurring contracts are normal in this business. Hosting, maintenance, and SEO are genuinely ongoing work. The trap isn't auto-renewal itself; it's auto-renewal engineered so you miss the exit.

Watch for the combination of:

  • Long renewal terms. The contract renews for a full year, not month to month.
  • Narrow cancellation windows. You can only cancel within, say, a 30-day window that ends 60 days before renewal. Miss it by a day and you owe another year.
  • Burdensome cancellation mechanics. Cancellation only by certified mail, or only by phone during business hours, while signup took ninety seconds online.

Regulators have been paying increasing attention to exactly this pattern. The FTC has pursued rulemaking and enforcement around negative-option billing and the general principle that canceling should be as easy as signing up. But you don't want to be the test case. Read the renewal clause, put the cancellation window on your calendar the day you sign, and prefer providers who earn the renewal instead of engineering it.

Our own bias: month-to-month for ongoing services. If the work stops being worth it, you should be able to stop paying for it. You can see how we structure that on our pricing page.

Red flag 4: Vague deliverables

"Professional website. Modern design. SEO included." That's not a scope of work; that's a horoscope. Vague deliverables are how both sides of a bad deal get made: the provider can declare victory at any time, and the client can demand revisions forever. You want specificity that protects you both:

  • Pages and features, listed. How many pages? Contact forms? Online booking? A photo gallery you can update yourself? If it matters to you, it should be in the list.
  • "SEO included" defined. Does that mean basic on-page setup (titles, descriptions, indexing) or ongoing monthly work? These differ by an order of magnitude in effort and value. If a provider claims ongoing SEO, ask what they actually do each month and how it maps to what Google itself publishes in its search documentation. Anyone doing real work can answer in plain English.
  • Revisions, counted. How many rounds are included, and what does an extra round cost?
  • A timeline with teeth. Not "approximately 8 to 12 weeks," but dated milestones, and ideally some consequence if they slip. Endless website projects are so common they're a cliché. It's one reason we run our builds the opposite way: draft in 24 hours, live in 7 days, with you on the call while it happens.
  • What you must provide, and what happens if you're slow. Fair contracts put obligations on the client too (photos, content approvals). Just make sure a client delay pauses the clock rather than triggering fees.

Red flag 5: Payment structures that frontload all the risk onto you

Deposits are normal and fair; nobody should build for free. But be cautious about:

  • 100% upfront from a provider with no track record you can verify. Half down is common. All of it, before anything exists, from someone you found last week, is asking you to carry all the risk.
  • Hourly billing with no cap on a fixed-scope project. Hourly is fine for genuinely open-ended work. For "build me a five-page site," a fixed price keeps the incentive on finishing.
  • Surprise pass-through costs. Stock photos, plugins, "premium" fonts, and licensing fees that appear on invoices later. Ask whether the quoted price is the whole price.

The questions to ask before you sign

Print this list, ask them out loud, and write the answers into the contract:

  1. If we part ways, what do I walk away with: domain, content, design, code? In what format, and within how many days?
  2. Is the domain registered in an account I control?
  3. What logins do I get, and when?
  4. Exactly which pages and features are included, and how many revision rounds?
  5. What does "SEO" mean here, specifically, month by month?
  6. What is the renewal term, the cancellation window, and the cancellation method?
  7. What does off-boarding look like? Walk me through your last one.
  8. Is the quoted price the entire price?

A provider who welcomes these questions is telling you something. So is one who gets defensive. The SBA's guidance on hiring contractors and vendors makes the same general point about any service relationship: clarity up front is the cheap version of every dispute you'll never have.

One more honest note: most web designers and agencies aren't villains. The majority of bad contracts come from sloppiness, copied templates, and an industry habit of vagueness, not malice. But the contract is what governs when things go wrong, and things go wrong often enough that "they seemed nice" is not a clause.

How we try to be the easy comparison

We're a veteran-owned shop in Wilmington, NC, and we've built 1,500+ small business sites in the last 90 days, which means we've also inherited a lot of other people's contract messes. Our answer to the questions above: you own your content, you control your domain, ongoing services are month to month, and the scope is short enough to read because the build happens live, with you on the call.

  • Minimal: from $500, a clean professional site
  • Standard: $2,000 plus $200/mo with ongoing SEO and AI-search optimization
  • Max: $3,500 plus $400/mo, adds a 24/7 AI receptionist
  • Super Max: from $6,000, custom back office built around your operation

First draft in 24 hours. Live in 7 days, guaranteed. Pay-in-4 and Klarna available. See /pricing for the full breakdown, or book a call and bring your current contract. We'll go through it with you, even if you don't hire us. Especially if you're in a hands-on trade like HVAC or roofing, where the website is the lead engine and being held hostage costs real jobs.

Red Flags in Website Contracts — Omnyra