A local site is judged by one question: did somebody nearby call, book or walk in because of it. That is a narrower brief than most design conversations assume, and it changes what is worth paying for. Layout, photography and the two or three pieces of information a nearby customer needs on a phone matter enormously. Animation, a custom content system and a bespoke design language mostly do not. This page describes what a local build should contain, how templated, custom and leased arrangements compare over the life of the relationship, and the ownership questions that determine whether the site is an asset you own or a service you rent.
The five things a nearby customer needs immediately
What you do, where you do it, whether you are open, what it roughly costs, and how to reach a human. Every one of those should be answerable within one screen on a phone, without scrolling past a hero image. The phone number should be tappable and present in the header on every page. Hours and service area belong above the fold, not on a contact page. A price range, even a wide one, filters out the calls you do not want and increases the ones you do. Reviews should be visible near the point of action rather than corralled on their own page. This is unglamorous and it is where nearly all of the conversion difference between local sites lives, which is why a design review that starts with the brand palette rather than with the phone on a small screen is starting in the wrong place.
Three commercial models, priced over three years
The first is a configured template, usually a few weeks and a modest one off fee plus hosting. For most single location businesses this is the correct answer and the money saved is better spent on photography and on being found. The second is custom, months and several times the cost, justified when you have multiple locations, an unusual service mix or existing rankings that a migration puts at risk. The third is the leased site, free or nearly free to start with a monthly fee that bundles hosting, edits and often marketing. It is the model with the highest total cost over three years and the one where the site typically cannot be taken with you when you leave. Price all three by totalling thirty six months of every line, not by comparing the build fee. The ranking usually inverts.
Accessibility and speed are not optional extras
A local site is used disproportionately on phones, on cellular connections, often by older customers, and sometimes in a hurry. Slow pages lose calls in exactly the moments when the customer had the highest intent, and the Core Web Vitals metrics documented on web.dev give you a shared vocabulary for holding a builder to a standard rather than arguing about whether a site feels fast. Accessibility matters for the same practical reason and for a legal one: the Department of Justice publishes guidance on web accessibility under the Americans with Disabilities Act, and businesses open to the public have been the subject of claims. Ask a candidate what standard they build to, whether contrast and keyboard navigation are checked before launch, and whether they will run the site through a public performance tool with you present.
Design decisions that either help or hinder being found
Structure decides how much ranking work the site needs later. Real pages for each service and each area you serve, rather than one page listing everything, is the single most consequential choice, and it is a design decision as much as a content one. Location markup, which Google documents explicitly for local businesses, should be implemented at build time rather than retrofitted. Any rebuild of an existing site needs a redirect map before launch, because renamed URLs without redirects is the standard way a local business loses its positions overnight. This is why the build and the local business SEO services decision belong in the same conversation: a beautiful site with no page for the town you want customers from cannot rank for that town, and no amount of later optimisation fixes a structure that has nowhere to put the answer.
Questions people ask about local business web design
Is a website builder good enough for a small local business?
For many, yes. A mainstream builder configured carefully, with your own photographs, real service pages, correct location markup and a fast theme, will out perform a poorly executed custom site and cost far less. The limitations show up at scale, with multiple locations, large service catalogues or complex booking. Judge on whether the platform lets you export your content and point your own domain at it.
Who should own the domain name?
Your business, registered in your company name with an email address you control as the administrative contact. This is the single most important ownership term and the one most often handled badly. Log into the registrar yourself and confirm it rather than accepting an assurance. A domain held by a former agency is the most damaging thing to be missing during a fallout.
How many pages does a local site need?
Fewer than most proposals suggest and more than most builders deliver. One page per service you want to be called about, one per distinct area if those areas are genuinely different markets, plus about, contact and reviews. Thin duplicated town pages that differ only by name are a known spam pattern under Google's published policies and are a liability rather than a shortcut.
Should we pay for ongoing maintenance?
Yes for security updates, backups and hosting, which are real recurring costs and cheap. Be more sceptical about a maintenance retainer sold as unlimited edits, which usually means a handful of small changes a year at a substantial annual cost. Ask what was actually delivered under that plan for a comparable client in the last twelve months.