A plumber working out of a home office and a restaurant on a busy corner run on the same Google Business Profile system, but they are playing different ranking games. The plumber is a service area business: the work goes to the customer, the address stays hidden from public view, and the ranking signals never include the foot traffic and street-level prominence a restaurant draws on. The restaurant is a storefront: the address is the destination, signage and physical presence count, and proximity is a foundation rather than a constraint. Most local SEO advice flattens the distinction. The two run on the same GBP infrastructure but need separate playbooks, and the first job is naming which one a business actually is.
A service area business (SAB) delivers its service at the customer’s location instead of at a fixed address customers visit: plumbers, electricians, HVAC contractors, mobile groomers, house cleaners, lawn care crews, locksmiths. A storefront is a business customers come to: restaurants, retail stores, dental practices, salons, gyms, medical offices. Google treats these as distinct setup configurations, and calling a storefront an SAB (or the reverse) confuses the ranking system. The model choice decides which work matters, so it comes first.
Address visibility is the difference everything else follows from #
The most visible split is the address. Storefronts list a public address that appears on the profile, in search results, and on Google Maps; Google ties storefront eligibility to a real, staffed location with on-site signage where customers are served. SABs list a registered address (the owner’s home or a small office) that gets removed from public display when the profile is set up as service-area.
The hidden-address mechanic exists because businesses serving customers at their locations do not need an operating address shown publicly. A plumber’s home address on a public profile invites unwanted visits, neighborhood spam, and privacy problems. Google’s guidance is direct: if you do not serve customers at your business address, remove the address and enter only your service area. The address stays on the back end for verification but does not display, and the setting has to match reality. A profile set up as storefront while operating as an SAB shows the owner’s home address publicly until it is reconfigured.
This one choice ripples through everything downstream. Citations behave differently when the address is public versus hidden, photos differ with a visible storefront versus a home office, and reviews accumulate differently when customers visit a place versus when the business comes to them.
The service area field is where an SAB tells Google what “local” means #
The service area field is a list of cities, postal codes, or defined regions that specifies where an SAB delivers. It sets which queries the business is eligible for based on the searcher’s location. A plumber listing Brooklyn, Queens, and Manhattan is eligible for those areas; a plumber listing only Brooklyn is not eligible for Queens searches even if the business technically serves there. The field is eligibility infrastructure, not a ranking dial.
The mechanics carry hard constraints, and two of them changed the calculus recently:
- A flat cap of 20 areas. Google allows up to 20 service areas per profile, counted as a single total whether they are cities, postal codes, or a mix. A business serving 50 cities has to pick the most strategic 20 or run separate profiles where eligibility allows.
- No radius option. Radius definitions are no longer supported. Google requires areas named by city, postal code, or region, and profiles that previously used a radius can no longer edit it that way. Guidance that still recommends radius targeting is stale.
- A two-hour boundary. Google states that the overall service area should not extend more than about two hours of driving time from where the business is based. Country-level and state-level areas are rejected outright.
Two misconfigurations recur. Over-expansion lists every adjacent city hoping to rank everywhere; it dilutes signal and can trigger spam evaluation when the spread looks unrealistic for the business size. Over-constraint lists only the immediate city when operations reach further, forfeiting eligibility next door. The right definition is the operational truth: the areas the business actually serves, inside Google’s limits.
Verification asks for different evidence in each model #
GBP verification uses similar methods for both models (most commonly video verification in 2026), but the specific evidence differs. Storefront verification expects the video to show signage, a physical entrance, interior operations, and proof of access at the registered address. SAB verification expects different evidence because no public storefront exists.
For SABs, current video verification centers on branded company vehicles, work uniforms, the equipment used to perform the service, and the registered workspace (even though that address is not publicly visible). A plumber’s video shows the branded van, typically with a slow walk-around and the plate visible, the tools inside, and the home office where dispatch happens. Magnetic signs that peel off tend to fail as proof of a genuinely branded vehicle.
Google’s review also checks whether the evidence matches the claimed operational scale: a business claiming five cities of coverage while showing a single small van draws scrutiny. Storefront verification is simpler because its evidence is concentrated (signage, door, interior, access). SAB verification takes preparation because the evidence is distributed across vehicles, equipment, workspace, and often documentation like a license, insurance, or open job paperwork.
Where the two models diverge, at a glance #
| Element | Storefront | SAB |
|---|---|---|
| Address visibility | Public | Hidden (back-end only) |
| Service area field | Not used (single location) | Up to 20 cities or postal codes |
| Verification evidence | Signage, entrance, interior, access | Branded vehicles, equipment, workspace |
| Primary proximity | Distance to single address | Distance within defined service area |
| Photo strategy | Storefront, interior, operations | Vehicles, equipment, completed work |
| Review moment | On-site after visit | Follow-up after service completion |
| Citation focus | Address-anchored directories | Service-anchored directories |
Proximity works against an SAB the way it works for a storefront #
Proximity is a primary local pack ranking signal, but its mechanics differ sharply. Storefronts get ranking strength near their registered address that falls off with distance; a restaurant downtown ranks well from downtown and worse from the suburbs. SABs are more complex: rankings depend on the service area definition, not just the registered address, and proximity gets weighed relative to that area.
In practice, rankings within an SAB’s service area still favor proximity to the registered address. A plumber registered in Park Slope and serving all of Brooklyn tends to rank strongest from Park Slope and weaker from Bay Ridge or Williamsburg, even though both sit inside the listed area. The service area defines eligibility; proximity within it still shapes ranking strength. So the registered location matters even while hidden: an SAB at one edge of its area has uneven coverage, one near the center has more even coverage, and when there is any flexibility about where to register, that becomes a strategic decision rather than an administrative one. For hybrids, proximity runs both ways, with storefront proximity driving visit queries and service-area proximity driving at-customer-location queries.
Citations, photos, and reviews shift by model #
Citations (directory listings with consistent NAP information) support prominence for both, but the directory mix shifts. Storefronts benefit most from address-anchored directories emphasizing the physical location: Yelp, TripAdvisor, Foursquare, neighborhood guides. SABs benefit most from service-anchored directories emphasizing what the business does: Angi, HomeAdvisor, Thumbtack, the BBB, trade associations, certification directories. NAP consistency holds either way, and for SABs the listed service area should align across directories that capture it, since “Brooklyn and Queens” in one and “Brooklyn only” in another reads as uncertainty about the footprint.
Photos are where an SAB has a problem a storefront does not. Storefronts have abundant material: exterior, interior, products, staff. An SAB has none by default, so the working strategy documents what it can show: completed work as before/after shots with customer permission, branded vehicles and equipment, uniformed team members, in-progress work. Roofers, house cleaners, landscapers, and mobile detailers all translate to the before/after format, which gives Google engagement signals it would not otherwise see. Stock photos of generic tools read as inauthentic. Monthly fresh uploads suit both models.
Reviews are a major signal for both, but the workflow and language differ. Storefronts can ask at the point of transaction, when the customer is on-site and the experience is fresh. SABs have to ask after service completion at the customer’s location, a follow-up text or email within hours rather than an in-the-moment request, and that friction makes velocity harder to sustain. Storefront reviewers describe the place (“clean dining room”); SAB reviewers describe the service (“fixed the leak quickly”). For SABs, review language also discloses coverage: “they came all the way to Queens” tells Google the business serves Queens, and steady recent reviews tend to outrank large historical counts with no recent activity.
Scaling and hybrids: represent the real operation #
A storefront chain scales by opening locations, each with its own profile. A multi-area SAB scales by extending its service area, which the 20-area cap constrains. A business serving 50 cities can pick the 20 most strategic, create separate profiles for genuinely distinct operational regions (with separate verification and management), or use the service area for the primary region and support the rest with website location pages. Those pages work when the extended regions have real, separate operations (their own phone numbers, teams, scheduling) and can rank organically for service-plus-city queries the GBP area does not cover. Franchise SABs need one profile per franchisee, since each is a separate business under shared branding. The mistake to avoid is spinning up multiple profiles for one operational entity across overlapping areas; Google’s duplicate detection reads that as spam and can suspend the listings.
Hybrids run both playbooks in parallel. The GBP shows the public address and defines a service area for the off-site work; photos combine both signal types, reviews split into on-site asks and follow-up asks feeding one profile, and citations cover both directory categories. The failure to avoid is presenting only one mode: claiming to be a pure storefront while also serving off-site forfeits eligibility for at-customer-location queries, and claiming to be a pure SAB while also running a storefront forfeits the proximity benefit and the visible-address signals a public location carries.
FAQ #
Do I have to hide my address as a service area business?
If you do not serve customers at your business address, Google’s guidance is to remove the address and enter only your service area. The registered address stays on the back end for verification but is not shown publicly.
Can I still set my service area as a radius?
No. Radius definitions are no longer supported. Define areas by city, postal code, or region, and keep the overall area within about two hours of driving time from the base location. Country-level and state-level areas are rejected.
How many service areas can one profile have?
Up to 20, counted as a flat total across cities and postal codes combined. A business covering more has to prioritize, run separate profiles for distinct regions, or extend reach through website location pages.
How is video verification different for an SAB?
A storefront shows signage, entrance, and interior. An SAB shows branded vehicles, the equipment used on the job, the registered workspace, and often supporting documentation. The evidence has to match the claimed scale of operation.
The two models are not two flavors of the same optimization work; they run on different foundations. A storefront optimized like an SAB underuses the visible-address signals it has, and an SAB optimized like a storefront misses the vehicle, photo, and review patterns that build its credibility. Name the model honestly first (does the work happen at the customer’s location, at the business’s location, or both), then run the playbook that matches. That choice is not decorative. It decides which optimization work actually moves the profile.