Why Your General Contractor Profile Ranks in Torrance But Disappears in Redondo Beach

A general contractor we audited last quarter had done everything the checklists tell you to do. Google Business Profile fully filled out. Service area set to eleven cities: Torrance, Redondo Beach, Hermosa Beach, Manhattan Beach, Lomita, Gardena, Carson, Palos Verdes Estates, Rolling Hills, Rancho Palos Verdes, El Segundo. Forty-one reviews, all five-star, all recent. On paper, a business ready to compete anywhere in the South Bay.

He ranked in the map pack for kitchen remodel searches inside a 1.8-mile radius of his Torrance office. Outside that radius — including in cities he'd explicitly listed — he was gone. Not page two. Gone. A homeowner in Redondo Beach searching "general contractor near me" would never see him, despite Redondo being eleven minutes from his shop and a market he'd listed by name.

He assumed the service area field in GBP was a configuration setting — type in the cities you serve, Google shows you there. That's not how it works, and misunderstanding this single mechanism is costing South Bay contractors, and pretty much every service-area business in the trades, thousands of dollars a month in invisible demand.

Your Service Area List Is a Request, Not an Instruction

Google Business Profile lets you declare a service area of up to twenty places. Most owners treat that field the way they'd treat a settings toggle in QuickBooks — enter the value, get the output. But Google's local algorithm doesn't take your service area list as ground truth. It takes it as a claim, and then it checks that claim against independent evidence before deciding how far to actually extend your visibility.

The evidence Google checks: where your reviews are geographically clustered (reverse-geocoded from reviewer location data and review content mentioning neighborhoods), where your business is cited consistently across directories and industry sites (Houzz, Angi, BBB, local chamber listings), what your website's structured data says about areas served, and whether your primary GBP category has a typical service radius norm that supports operating that far out.

A general contractor with forty-one reviews all written by people within two miles of the office, no city-specific project pages, and directory citations that only list a Torrance address is giving Google zero evidence to support a countywide radius — no matter what's typed into the service area field. Google's ranking system runs on three pillars for local queries: relevance, distance, and prominence. Distance decay is steep, and it gets steeper the less prominence evidence you have supporting a wider radius. You don't get to declare your way past that. You have to prove it.

The Mechanism: Google Computes a Centroid, Then Applies Decay From It

Here's the part almost no contractor understands, because it's not something Google publishes — it's something you reverse-engineer by watching rank-tracking data across grid points. Google doesn't treat your service area as a flat polygon where you're equally visible everywhere inside it. It calculates something closer to a weighted centroid — a center of gravity built from your physical address, your review geography, your citation geography, and your content geography — and then applies distance decay outward from that centroid, query by query, based on how competitive that specific search grid point is.

This is why the same business can rank #2 in Torrance, #9 in Lomita three miles away, and not appear at all in Manhattan Beach seven miles away, even though all three cities were typed into the same service area field. The decay isn't linear and it isn't uniform — it's steeper in denser, more competitive grid points (Manhattan Beach has more contractors bidding for the same map pack real estate than Lomita does), and it's steeper for businesses whose evidence trail (reviews, citations, content) doesn't extend past their centroid.

The failure compounds because most contractors respond to poor visibility by adding more cities to the service area field, assuming broader input equals broader output. It does the opposite. Every city added without supporting evidence dilutes topical and geographic relevance for the cities where you actually have proof, because Google's relevance scoring is comparing your evidenced strength against competitors who are hyper-specific to that exact grid point. A contractor genuinely dominant in Torrance and Lomita, chasing eleven cities, will often lose ground in the two markets he actually owns.

What a Fixed Architecture Actually Looks Like

The fix isn't editing a field. It's building the evidence trail that makes the field true.

Start with the primary category. Google applies different implicit radius norms by category — "General Contractor" behaves differently than "Kitchen Remodeler" or "Home Builder," and stacking too many secondary categories that don't match your actual completed work dilutes the relevance signal rather than expanding it. Pick the primary category your last twenty jobs actually match, not the broadest one available.

Then build geographic proof deliberately instead of hoping it accumulates. That means requesting reviews specifically from completed jobs in the cities you want to rank in — not just asking every client, but prioritizing review requests from Redondo Beach and Hermosa Beach jobs when those are the markets you're trying to expand into, so the geographic center of your review cluster actually shifts. It means building citations (NAP-consistent listings) on directories that carry city-level relevance, not just generic national ones. And it means the website itself needs city-specific proof — not eleven thin city pages competing with each other (a different and equally common failure), but a handful of genuinely built-out project pages, each with geo-tagged photos, local schema markup (LocalBusiness with a proper areaServed GeoShape or GeoCircle, not just a text list), and real project details tied to a real neighborhood.

This is the architecture we build into every general contractor site we launch — structured data that mirrors reality instead of aspiration, project pages that function as geographic evidence rather than SEO filler, and a review-acquisition sequence that's deliberately weighted toward the cities a contractor is trying to grow into, not just the ones he's already dominant in. The same logic applies across home services broadly — HVAC, landscaping, roofing — anywhere a business operates across multiple cities from a single physical location.

Stop Configuring. Start Proving.

Most South Bay contractors treat their Google Business Profile like a form to fill out once and forget. It's not a form. It's an ongoing evidentiary case you're building every time you get a review, land a citation, or publish a project. The businesses winning map pack visibility across five or six South Bay cities aren't the ones with the longest service area list — they're the ones whose review geography, citation geography, and content geography all independently corroborate that list.

If your GBP service area reads like a wish list and your rankings read like a 1.8-mile radius, the fix isn't more cities in the settings field. It's a conversation about what evidence you actually have, city by city, and what it would take to build the evidence for the markets you're leaving on the table. That's the audit worth having before you spend another dollar on ads trying to buy visibility your organic profile hasn't earned yet — and it's the kind of forensic work we do for operators across the South Bay who are tired of guessing why the map pack treats their own backyard like foreign territory.