Does a local business need a website if it already has a Google Business Profile?
Yes, and the research pins down exactly where the listing hands the buyer off. BrightLocal's 2026 Local Consumer Review Survey found that "consumers are most likely (54%) to visit a business's website after reading positive reviews, up significantly from 32% when we last asked this in 2019." Read that as a job description: the profile gets you found, the reviews get you shortlisted, and then most of the buying public leaves for your site to make the final call. BrightLocal sells local SEO software, so weigh its survey with that interest in mind — though it publishes its methodology (1,002 US adults, published February 2026), which is more than most local-marketing statistics manage.
BrightLocal puts a number on the other end of that handoff too:
"With just 40% of local businesses having a dedicated website, many consumers could be dropping off at this point in the funnel." — BrightLocal, Local Consumer Review Survey 2026
One caveat that most write-ups drop: that 40% is not from the consumer panel. It traces back to a separate study, BrightLocal's SMB Marketing Report 2025, a survey of 778 US small-business owners and managers. Treat it as directional rather than a census — the same report found only 35% of those SMBs have a Google Business Profile at all, which suggests a sample tilted toward the very small and the barely-online. The direction still holds, and it is the useful part: a large share of your local competitors have nothing for that after-review visit to land on.
So the real question is not whether to build a site. It is whether the site does the five things a listing structurally cannot do: hold a page architecture a buyer can navigate, load on a phone, publish machine-readable business facts, cover a service area honestly, and prove which channel produced the call. That is the GTM Teardown lens applied to local — rented visibility on top, owned infrastructure underneath.
One pair of numbers from that report gets fused constantly, so keep them apart. Google's share as a review source dipped from 83% in 2025 to 71%. Separately, answering a different question — use of ChatGPT and other generative AI tools for local recommendations — adoption rose from 6% last year to 45%. Two survey questions, not two slices of one pie, and anyone stacking them into a single chart is overselling. The directional read still holds: discovery is spreading across surfaces you do not control, which raises the value of the one you do.
What should each page of a local business website actually do?
Most local business websites fail on architecture long before they fail on tactics. The buyer arrives with one question — can this business do my specific job, in my town, without wasting my afternoon — and the average small-business site answers it with a hero image and a contact form. Here is the version that earns the call:
| Page | What most local sites ship | What earns the call |
|---|---|---|
| Homepage | A hero photo, a slogan, a "welcome to our website" paragraph | Trade, service area and phone visible without scrolling; one tap-to-call link; three lines of proof |
| Service pages | One "Services" page listing eight things as bullets | One page per service you actually want to sell, each with scope, what's included, and what you don't do |
| Service-area pages | The same paragraph with the city name swapped | Drive time, permitting or code notes, neighborhoods, work completed nearby |
| Proof / reviews | A footer link out to the Google profile | Review text beside the offer, dated, with the job type named |
| Contact | A ten-field form and a contact@ address | Phone first, form second, four fields maximum, and a stated response time |
Two design calls worth making explicitly. Put the phone number in HTML text as a tel: link rather than baking it into an image — a homeowner standing in a flooded kitchen should never have to retype it. And cut the form down to the fields you will actually use on the first callback; every extra field is another chance to close the tab.
What to skip: a chat widget nobody staffs, a stock-photo carousel, an "our process" timeline with six numbered steps, and a blog you will abandon in five weeks. None of them move a local buyer, and all of them slow the page down.
How fast does the site have to be, and on which device?
Fast, and on a phone — and the thresholds are published, so there is nothing to argue about. Google's Core Web Vitals set the "good" bar at Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less, measured at the 75th percentile of page loads, segmented across mobile and desktop devices.
Device matters more than most owners assume. Google states that it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking," and its mobile-first indexing guidance tells sites whose mobile version carries less content than desktop to bring the two to parity. A service list that collapses away on mobile is a service list that is not doing ranking work. Test on a real handset over cellular data, not on office wifi with a desktop browser resized.
Why does NAP consistency still quietly cost rank?
Mismatched name, address and phone (NAP) data is the kind of defect that never surfaces in a design review and still moves rankings. In Whitespark's 2026 Local Search Ranking Factors report, published November 2025, "HTML NAP Matching GBP NAP" ranks #15 among local pack and Maps factors, and "Consistency of Citations on Primary Search Engines" ranks #28.
Read that ranking for what it actually is. It is not measured algorithm data — it is 47 local-search practitioners scoring 187 factors from experience, and Whitespark sells citation building, so it has a stake in where citation factors land. Neither factor comes close to the top of its own list, which is led by primary Google Business Profile category, proximity of the address to the searcher, and keywords in the business title.
What makes it worth doing first is cost, not magnitude. There is no creative work and no recurring spend — audit every citation (Google Business Profile, Apple Maps, Bing Places, Yelp, trade directories, and the footer of your own site), then make the name, address and phone identical everywhere. Suite numbers, "St." versus "Street", and a number left over from an old answering service are the usual culprits. Anyone quoting a precise percentage lift from a citation cleanup is selling something.
What does LocalBusiness schema actually buy you?
NAP consistency solves the matching problem across other people's databases. LocalBusiness schema — JSON-LD on your own pages — solves the machine-readability problem: it hands search engines and AI answer engines a structured, unambiguous version of the business name, address, phone, hours, service area and price band, published from the domain you control.
| Field | Why it matters |
|---|---|
name, address, telephone | Must match the NAP on every citation, character for character |
areaServed | Declares the real coverage area, not just the HQ city |
openingHoursSpecification | Feeds the local pack and gets quoted back in AI answers |
priceRange | Sets expectations before the click and filters bad-fit inquiries |
aggregateRating / review | Useful context for answer engines — but see below, it will not put stars on your own results |
With 45% of consumers now reaching for generative AI tools when they want a local recommendation, "add schema" is not the whole answer. What makes a page quotable by an answer engine is the same thing that makes it useful to a human: facts stated plainly in body text. Hours as text, not an image. Service area named in a sentence, not implied by a map embed. Pricing model described even when the number varies by job. A model cannot cite what it cannot parse.
Then run the check yourself, because it takes ten minutes and nobody does it: ask ChatGPT, Perplexity and Google's AI results who they would recommend for your trade in your town, read what they say about you, and note which pages they cite. Wrong hours, a dead phone number, or a competitor named in your place is a content problem on your own site — not a mystery.
How many service-area pages can you build before Google calls it doorway spam?
As many as you can write with something real to say. The ceiling is editorial, not numerical. Spinning up a page per zip code by swapping a city name into an identical template has a name in Google's spam policies: doorway abuse, defined as sites or pages "created to rank for specific, similar search queries" that "lead users to intermediate pages that are not as useful as the final destination." The policy's own example list includes "having multiple domain names or pages targeted at specific regions or cities that funnel users to one page."
The alternative is not skipping service-area pages. It is writing five genuinely different ones instead of twenty identical ones: real drive-time or service-radius notes, permitting and code differences by municipality, the neighborhoods actually covered, and where it is honest, work completed nearby. A crew serving five towns with five distinct pages is building something Google's policy has no quarrel with. The same crew's twenty templated pages are the textbook case in the policy. The trade-specific version of this discipline is in web design for contractors and website design for plumbers — the pattern is universal, the details change by trade.
Where should reviews live on a local business website?
Next to the decision, not linked off it. Reviews get treated as something that lives on Google and earns a footer link, which badly undersells the asset — 97% of consumers read reviews for local businesses and 85% say positive reviews make them more likely to use one, per the same BrightLocal consumer survey. That content belongs on the homepage, on each service-area page, and beside the contact form. Recency counts too: 74% of respondents said they seek reviews written in the last three months, so a testimonial wall dated 2021 is working against you.
One correction, because the opposite advice is repeated everywhere: adding Review or aggregateRating schema to your own site will not put star ratings on your own search results. Google's review snippet documentation is explicit — "If the entity that's being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature." Self-serving reviews are excluded by design, whether hand-written or pulled in through a widget.
So put reviews on the site for the reason that actually holds: they convert the visitor who is already there and deciding, and they give answer engines quotable, attributable text about the business. Neither of those needs a star in the SERP.
How do you prove the website produced the call, not the profile?
An owner who cannot answer that is guessing on the highest-leverage decision in local marketing. The fix is mechanical:
- A tracked phone number on the website, distinct from the number listed on the Google Business Profile
- UTM parameters on every link you control — email signature, ads, social bios, invoices
- A required lead-source field captured at intake in the CRM, not reconstructed from memory later
- A monthly comparison of profile-attributed actions against site-attributed calls and form fills, over the same window
Skip this and the local pack gets credited for every conversion, which quietly justifies never fixing the site. The GTM Teardown rule applies without modification: infrastructure only counts if it is instrumented.
Where to start if the site needs work
Rebuilding a local business website is a sequencing problem more than a design problem. NAP and page speed first, because they are cheap and they gate everything downstream. Then architecture — one page per service you want to sell, service-area pages with something to say, reviews next to the offer. Then schema, then tracking. A site that is slow, locked inside a page-builder subscription, or built on a template that cannot hold clean schema and tracking will fight you at every step; owning the build is the difference between fixing the problem once and renting it indefinitely.
Sizing the spend before committing? Start with average cost of website design for small business, then the affordable web design for small business path. And if you would rather see the fixed version than read about it, the booking card below opens a walkthrough of a free website mockup built for your business.