Website design services for small business proposals are almost never comparable at a glance, because two vendors can quote the same job and mean two completely different amounts of work. One "complete website" includes copywriting, local SEO setup, and a year of support. Another "complete website" is a five-page template with lorem-ipsum you fill in yourself and a bill every time you want a phone number changed. This is a checklist you run on the actual proposals in front of you — line by line, scope area by scope area. For each item there is a plain pass (what a real inclusion looks like) and a fail (the quiet gap or the thing that becomes "extra" after you sign).
Print it, or open the two or three quotes you are weighing, and go down the list. You are not grading the design taste yet — you are grading the scope.
How to use this audit
Every proposal breaks into six scope areas: design, development, copywriting, SEO, hosting, and support. Reputable studios spell out all six. Thin ones name one or two loudly ("custom design!") and leave the other four undefined so they can bill for them later. Go through each area below and mark the quote pass or fail. A quote that fails three or more areas is not cheaper than the others — it is a smaller job wearing the same title. If you want the wider framing on evaluating the vendor themselves, our guide on how to choose a web designer for your service business pairs directly with this scope list.
Scope area 1: Design
Item — Is the design custom to your business, or a template with your logo dropped in? Pass: the proposal names a discovery or wireframe step and shows you a layout built around your services and service area. Fail: it references a "premium theme" or a demo site you'll be cloned from, with no wireframe stage. A template is not automatically wrong for a small service business — but you should know you are buying one, and it should cost accordingly.
Item — Mobile layout, explicitly. Pass: the quote says responsive or mobile-first and treats the phone layout as the primary design. Most of your customers — the person standing next to a dead water heater — are on a phone. Fail: mobile is unmentioned, or listed as "mobile optimization" as a separate add-on. Google has been mobile-first for indexing for years; a proposal that treats mobile as extra is telling you how current the vendor is.
Item — Page count is named. Pass: the exact pages are listed (home, services, individual service pages, about, service area, contact, reviews). Fail: "up to X pages" with no list, or a suspiciously low number. A service business usually needs a page per core service so each can rank and convert on its own; if the scope is four pages total, ask which services get left off.
Item — Who owns the design files and the final build. Pass: you do, in writing. Fail: silence, or a line that the design is licensed to you while the vendor retains it. This matters most the day you want to switch vendors.
Scope area 2: Development
This is where the biggest hidden gaps live, because clients rarely know to ask.
- Domain and DNS ownership. Pass: the domain is registered in your account (your email, your credit card) and the proposal says so. Fail: "we'll handle the domain" with no account in your name. This is the most common trap in small-business web work — the domain is the one asset the entire business runs on, and you want it held by you at a registrar you control. If you are still weighing whether to keep these pieces together or apart, our breakdown of bundling versus splitting web and hosting vendors walks through the tradeoff.
- SSL / HTTPS. Pass: included, no line item. Fail: listed as a paid extra. HTTPS is a baseline Google expects; charging for it separately is a red flag.
- Contact and quote forms that actually deliver. Pass: forms are built, connected to a real inbox or CRM, spam-protected with a honeypot or challenge, and tested. Fail: "contact form included" with no mention of where submissions go. An unmonitored form silently eating leads is one of the most expensive failures a service site can have — every dropped submission is a job that went to a competitor.
- Click-to-call on mobile. Pass: your phone number is a tap-to-dial link in the header on every page. Fail: unmentioned. For a service business this is not a nicety; it is the primary conversion action.
- Speed / Core Web Vitals target. Pass: the proposal names a performance standard — ideally Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1, which you can verify free in Google's PageSpeed Insights. Fail: no performance commitment at all. A slow site loses both rankings and the impatient visitor.
- Accessibility. Pass: the build targets WCAG 2.1 AA — proper alt text, keyboard navigation, color contrast. This is a genuine legal exposure; the U.S. Department of Justice web accessibility guidance points to WCAG as the practical ADA standard, and Title III lawsuits reach small businesses. Fail: not mentioned.
Scope area 3: Copywriting
Item — Who writes the words? This is the single line that most changes the real workload, and it is the one most often left vague. Pass: the vendor writes the copy for every page, based on an interview with you, and you review it. Fail: "content provided by client" buried in the terms — meaning you will be writing a service page for every trade you offer, at night, after the crew goes home, or the site launches with placeholder text and never gets finished.
Item — Are the words written to convert, not just to fill space? Pass: the proposal talks about clear calls to action, trust signals, and service-area language. Fail: copy is described only by word count. If you want to see what conversion-focused structure looks like before you judge a draft, our piece on fixing the real conversion leaks on a small-business site gives you the yardstick.
Item — Photos. Pass: the scope states whether stock photos are included or your own job-site photos will be used, and who sources them. Fail: silence — then a launch delay while everyone waits on images. Your own photos of real trucks and real crews outperform stock every time, so this is worth pinning down.
Scope area 4: SEO
"SEO included" is the vaguest phrase in the entire industry. Break it into the parts that are actually build-time technical work versus ongoing marketing, and grade only what the design service should deliver at launch.
- On-page basics. Pass: unique title tags and meta descriptions per page, one clear H1 per page, clean URL structure, an XML sitemap submitted to Google Search Console. Fail: "SEO-ready" as a slogan with none of these named.
- LocalBusiness schema. Pass: JSON-LD structured data with your legal name, address, and phone matching your other listings. This is what feeds the local pack and, increasingly, AI overviews — and it is a distinct dev task most quotes omit. Fail: not mentioned.
- NAP consistency and Google Business Profile. Pass: the vendor at least aligns your on-site name/address/phone with your Google Business Profile, or hands you a checklist to do it. Deep local SEO is often a separate engagement, and that's fine — our overview of local SEO for small business covers where the site ends and marketing begins. Fail: the proposal implies ongoing ranking work is included when it is really just launch-day tags.
- Analytics. Pass: Google Analytics and Search Console installed and verified, with call and form tracking so you can see what the site produces. Fail: no measurement, which means you'll never know if it works.
Scope area 5: Hosting
Item — Is hosting included, and for how long? Pass: the term is stated and what happens after is stated. Fail: "hosting included" with no duration, which usually means an ongoing arrangement you didn't consciously agree to.
Item — Can you leave with your site? Pass: you can export or receive the full site files and move to another host without a rebuild. Fail: the site is locked to a proprietary platform you can only rent. This is the difference between a vendor and a landlord.
Item — Backups and uptime. Pass: automatic backups and an uptime standard are named. Fail: neither is mentioned. For a business whose phone rings because the site is up, a day of downtime during a heat wave is lost jobs, not an inconvenience.
Scope area 6: Support
Item — What counts as "support," precisely? Pass: the proposal defines it — security updates, plugin/platform patches, small content edits, and a response time. Fail: "support included" with no definition, so the vendor decides later whether changing your hours is free or billable.
Item — Turnaround on edits. Pass: a stated window (for example, routine edits within a few business days). Fail: unstated, which in practice means whenever they get to it. A roofer who can't get a storm-season banner updated for two weeks has lost the point of having a site at all.
Item — Who you contact. Pass: a named person or channel. Fail: a general inbox with no commitment. For more on separating a real support relationship from a lock-in, see our no-nonsense guide to hiring a web designer.
Scoring your proposals
Go back through the two or three quotes and count the fails by area. A useful pattern: the cheapest-looking proposal usually fails copywriting ("content by client"), SEO (slogans, no schema), and support (undefined) — three areas that quietly move onto your plate or onto a future invoice. The apples-to-apples comparison isn't the headline figure; it's the headline figure plus the cost of everything a given quote left out. Two proposals that both look complete on the surface can differ by a full quarter of real work once you total the fails.
The point of running this audit isn't to find the vendor who checks every box for the least money. It's to make sure that when you compare quotes, you are comparing the same job. Once the scope matches, then you get to weigh design quality, the vendor's track record with businesses like yours, and whether you actually want to work with them for the next few years.
Frequently asked questions
What should always be included in website design services for a small business?
At minimum: a custom or clearly-priced design, a mobile-first responsive build, working spam-protected forms that deliver to your inbox, HTTPS, on-page SEO tags, analytics, and written confirmation that you own the domain and the site. Anything on that list that a vendor calls an add-on deserves a second look.
Is SEO part of web design or a separate service?
Both, split by timing. Launch-day technical SEO — title tags, LocalBusiness schema, sitemap, clean structure — belongs in the design scope. Ongoing ranking work, content, and link building are a separate marketing engagement. A proposal that blurs the two is either overpromising or planning to bill later.
Why does domain ownership matter so much?
The domain is the asset your whole online presence, email, and rankings sit on. If it's registered in the vendor's account instead of yours, leaving that vendor or recovering from one who disappears becomes a fight. Confirm in writing that the domain lives in an account you control.
Should copywriting be my job or the designer's?
If the proposal says 'content provided by client,' you are the writer, and that is the line that stalls most small-business launches for months. Prefer a scope where the vendor writes each page from an interview with you and you review it.