The short version
Google Business Profile lets you list up to twenty service areas, and most contractors treat the cap as a target because more areas feels like more reach. It is not. Service areas are a relevance input, not a broadcast radius - they help Google understand who you are rather than pushing your pin further across the map, and a profile claiming twenty areas is a weaker answer to 'who is genuinely near me and can come out' than one claiming six. The business effect usually outweighs the search effect anyway: a tighter area means shorter average drive time, which means more jobs per truck per day on the same lead volume.
What the service area field actually does
The most common misconception about service areas is the most consequential one: people believe the list determines where the profile can appear. It does not. Proximity in the local pack is calculated from the searcher's location relative to your business, and listing a town twenty minutes further out does not move your pin toward it.
What the field does is describe you. It is one of several inputs Google uses to work out what kind of business this is and which queries it is a good answer for. That makes it a relevance signal rather than a distribution mechanism, and relevance signals behave differently from reach - specifically, they get weaker as they get broader.
Why more polygons is not more reach
Consider what the ranking system is trying to decide. Somebody types a query with local intent, and the system is choosing which three profiles best answer 'who is genuinely near this person and can actually come out'. A profile claiming six areas around a clear centre is a confident, coherent answer. A profile claiming twenty areas spanning ninety minutes of driving is a vaguer one, because it describes a business with no particular centre.
It also puts you in direct comparison with more competitors. Every area you add overlaps somebody's home turf, and in each of those overlaps you are the business that is further away with less local review text and no local job history. Adding areas does not add positions; it adds contests you are structurally positioned to lose.
Our rule of thumb, and where it comes from
List what the crew can genuinely reach in about forty minutes. Not what you would drive to for a large enough job - what a technician can get to on an ordinary Tuesday without wrecking the schedule.
Forty minutes is not a magic number from Google; it comes from dispatch. It is roughly the point where a single job stops being profitable against the drive, and it happens to correlate with how far a person will consider a business 'local' when choosing. Setting the field to a business reality rather than an aspiration produces a list that is both honest and, in practice, tighter than most.
The business effect is larger than the search effect
This is the part that surprises owners, and it is worth putting first when you make the case internally. Shorter average drive time per job means more jobs per truck per day on the same number of leads. That is a capacity gain, it shows up in revenue rather than in a dashboard, and it arrives immediately rather than after a ranking change.
The search effect - concentrated relevance, fewer losing contests - is real but slower and harder to attribute. If the only argument for trimming were the search one, it would be a reasonable thing to be sceptical about. The scheduling argument stands on its own even if the ranking never moves.
What to do if you genuinely serve a wide region
The answer is more locations, not more polygons. A genuine second location - real address, real staff, verifiable - gives you a second pin, and a second pin is the only thing that actually moves your position on the map. Twenty areas on one profile is an attempt to fake that, and it is both weaker and more fragile than the real thing.
Where a second location is not realistic, the honest structure is a tight profile plus organic location pages covering the wider catchment. The map pack serves the core; the pages serve the edge. Those are different mechanisms and trying to make the profile do both jobs weakens it at the one it is good at.
Run the test on your own listing
This is one of the few local search changes that is genuinely testable in a reasonable window, because it is a single variable you control. Trim the list, change nothing else, and watch for eight weeks.
Track two things: profile impressions, and the average distance of the jobs you actually book. The expected pattern is impressions holding flat or rising slightly while average job distance falls. If impressions collapse, put the areas back - that is a real result and worth knowing. In our experience they do not, but it is your listing and an eight-week test costs you nothing but patience.
What to tell a customer who asks where you are based
This comes up more than the technical side of it. A homeowner two towns over wants to know whether you are local, and a service area business has no address to point at, which can read as evasive if you let it.
Answer it directly on the page instead of hiding from it. Say where the vans leave from in the morning, how long it takes to reach their area, and which towns the crew covers on a normal week. That is more useful than a pin on a map, and it is true, which matters because the alternative is renting a mailbox somewhere and hoping nobody notices.
The listings that get suspended for address problems are almost always the ones trying to manufacture a presence they do not have. A business that explains its actual geography plainly has nothing to defend and nothing to lose if somebody checks.
Keep a copy of what you submitted
Screenshot the service area, the categories, the hours and the description every time you change them, with the date. It takes a minute and it is the only record you will have.
Profiles get edited by other people. Suggested edits get accepted, hours get changed by an automated signal, categories move during a rollout. Without a dated record you are arguing from memory about what your own listing used to say, and the support conversation goes very differently when you can show exactly what changed and when.
Check it on your own site
Write down what you currently claim
Open the profile and list every service area on it. Most contractors have not looked at this since setup, and a meaningful number find towns nobody has driven to in three years still sitting in the list.
Ask dispatch which of those you actually go to
Not sales, not the owner - whoever schedules the trucks. Pull the last ninety days of completed jobs and count them by town. The list of places you genuinely serve is almost always shorter than the list you claim.
Measure forty minutes at the hour you actually dispatch
Not at midnight. Check drive times at eight in the morning and at four in the afternoon, because a town that is thirty minutes away at nine at night can be an hour at school run, and the second number is the real one.
Trim to what survives both checks and change nothing else
Leave categories, services, hours, photos and posts alone for the duration. One variable is what makes the next step meaningful - if you also rewrite the description this week, the result tells you nothing.
Compare impressions and average job distance after eight weeks
Profile impressions from the performance report, average distance from your own dispatch records. Impressions flat or up with distance down is the outcome to expect. Impressions genuinely collapsing is a real finding - restore the areas and you have learned something specific about your market.