A 2024 BrightLocal analysis of local pack results across 500 metro areas found that 23% of local packs contained at least one business located outside the city boundaries specified in the search query. This anomaly is not a bug. It reflects how Google’s candidate pooling system expands geographic boundaries when the initial pool lacks sufficient qualifying businesses, when a business’s entity signals indicate strong relevance to the target area, or when prominence signals are extreme enough to override distance penalties. Understanding the triggers for cross-city inclusion determines whether an out-of-area business can exploit this effect or a local business can defend against it.
How Google’s Candidate Pool Expansion Triggers Cross-City Inclusions
Google’s local pack requires three results. When a query specifying a city name returns fewer than three qualifying businesses within that city’s geographic boundaries, the algorithm progressively expands the candidate pool radius until it fills the pack. This expansion behavior explains the majority of cross-city inclusions and operates through a predictable set of triggers.
The primary trigger is low category density within the named city. A search for “helicopter charter in [small city]” may return zero businesses within city limits because no helicopter charter companies exist there. Google expands outward, pulling results from the surrounding region until three qualifying candidates appear. The expansion radius varies by category: high-density categories like restaurants or dentists expand narrowly because candidates are plentiful, while specialized categories expand aggressively because candidates are scarce. In extreme cases, the expanded radius can cover 50 miles or more for rare service categories.
The second trigger is insufficient qualifying businesses after applying relevance filters. A city may contain dozens of businesses, but if the query requires a specific primary category match and only two businesses in the city have selected that category, Google expands to find a third candidate. This means the cross-city inclusion is sometimes caused not by a lack of businesses but by a lack of businesses with correct category alignment, reinforcing the importance of primary category selection.
The third trigger involves historical search satisfaction data. Google tracks which results searchers actually engage with (clicks, calls, direction requests) for specific query patterns. If searchers in a given city consistently engage with a business outside city limits for a particular query, Google incorporates that behavioral signal into future candidate pooling. A popular specialty restaurant 2 miles outside city boundaries that draws significant traffic from within the city may be included in the city’s local pack based on demonstrated user preference rather than geographic qualification.
The December 2021 Vicinity update tightened the expansion thresholds substantially. Before that update, businesses could appear in local packs for cities well outside their effective service radius through optimization alone. Post-Vicinity, the expansion requires a genuine scarcity of in-city candidates or overwhelming prominence signals. Businesses that previously ranked in multiple city packs lost those positions overnight when the update restricted expansion behavior.
The Entity Authority Signal That Allows Distant Businesses to Override Proximity
Certain businesses appear in cross-city local packs not because of candidate pool expansion but because their prominence signals are strong enough to override the proximity penalty. This mechanism is distinct from pool expansion and applies even when sufficient local candidates exist.
Google’s prominence calculation aggregates review count and quality, citation volume and authority, link profile strength, behavioral engagement metrics, and brand recognition signals. When the prominence gap between an out-of-area business and local competitors exceeds a threshold, the algorithm may surface the prominent business despite its distance disadvantage. This mirrors Google’s organic search behavior, where highly authoritative results can rank for queries in regions where they have no physical presence.
The threshold for prominence override is high. In competitive categories with three or more strong local competitors, an out-of-area business rarely breaks through regardless of prominence. The override most commonly occurs in mid-competition markets where local competitors have weak profiles. A business with 500 reviews and a 4.8 average rating located 5 miles outside city limits can displace a local competitor with 12 reviews and a 3.9 rating, because the prominence gap compensates for the proximity penalty.
Brand recognition creates a special case. National or regional brands with strong entity recognition may appear in local packs for areas served by their nearest location, even when that location falls outside the specific city searched. Google’s entity model associates the brand with the broader region, and the brand’s accumulated prominence signals support inclusion. Independent local businesses do not receive this treatment unless they have built comparable entity authority within Google’s knowledge graph.
The practical implication for local businesses facing cross-city displacement is that the response must target the specific signal where the gap exists. If the out-of-area competitor wins on review count, accelerating review generation is the defensive priority. If the competitor wins on brand authority, building local-specific link and citation profiles creates differentiation that Google values for geographic relevance matching.
City Boundary Definition Mismatches and Defensive Strategies Against Out-of-Area Competitors
A significant portion of apparent cross-city anomalies dissolve when practitioners understand that Google’s geographic boundaries do not align with official municipal borders. A business that appears to be outside city limits on a municipal map may fall within Google’s definition of that city, or a business within municipal limits may fall outside Google’s boundaries.
Google’s geographic data draws from multiple sources: census-designated places, postal code boundaries, Google’s own derived geographic entities from Maps data, and boundary information from geographic data providers. These sources do not always agree with each other or with official municipal boundaries. Census-designated places (CDPs) in particular can differ substantially from incorporated city limits, especially in areas with unincorporated communities, annexation history, or overlapping jurisdictions.
Local Search Forum discussions have documented cases where a business’s physical address falls within the official city limits according to municipal records, but Google Maps does not include that area within its mapped boundary for the city. The reverse also occurs: Google may extend a city’s boundary to include areas that the municipality does not officially govern. These discrepancies are not correctable through GBP optimization because they reflect Google’s underlying geographic data rather than listing-level attributes.
Practitioners can diagnose boundary mismatches by searching the city name on Google Maps and observing the shaded boundary area Google displays. If the business’s address falls outside this shaded area despite being within official city limits, the listing faces a geographic classification disadvantage for explicit queries naming that city. The address itself may be tagged with a different locality in Google’s system, which reduces relevance signals for the target city.
Correction options are limited. Submitting a Maps feedback report about incorrect boundary data sometimes triggers a review, but the timeline and outcome are unpredictable. Using the correct city name consistently across all citations, the website, and the GBP listing reinforces the geographic association. Structured data markup with LocalBusiness schema that explicitly names the target city provides an additional signal. However, if Google’s base geographic data classifies the address as belonging to a different locality, these reinforcement signals may be insufficient to override the system-level classification.
Local businesses displaced by cross-city competitors need targeted strategies that reinforce their geographic legitimacy while building the prominence signals required to hold their position.
Strengthen city-specific relevance signals. Ensure the GBP listing uses the correct city name in the address field and that all citations consistently reference the same city. Create city-specific content on the website landing page linked from the GBP that includes the city name in the title tag, H1, and body content. Build local backlinks from sources within the target city: chamber of commerce, local news sites, community organizations, and city-specific directories. These signals establish geographic relevance that out-of-area competitors cannot replicate.
Close the prominence gap. If the cross-city competitor’s inclusion is driven by superior review count or rating, invest in review generation targeting consistent monthly velocity rather than one-time campaigns. If the competitor has stronger website authority, pursue local link building that simultaneously strengthens both geographic relevance and domain prominence.
Monitor for guideline violations. Some cross-city inclusions stem from competitors who have falsified their address, used a virtual office, or created unauthorized listings within the target city. If a competitor’s physical address does not match their listed address, reporting the violation through Google’s “Suggest an edit” feature or filing a redressal form may result in the listing being corrected or suspended. This is not a guaranteed outcome, and the reporting process can be slow, but it addresses illegitimate cross-city placements directly.
Audit your own geographic signals for conflicts. Inconsistent city references across citations, a mailing address that differs from the physical address, or a postal code that maps to a different city in Google’s system can all weaken geographic relevance. Run a citation audit specifically checking city name consistency. Even one high-authority citation listing the wrong city can introduce enough entity confusion to impact local pack positioning.
When Cross-City Ranking Anomalies Indicate a Larger Entity or Data Problem
Not all cross-city inclusions result from normal algorithmic behavior. Some indicate underlying data problems that require different diagnostic and remediation approaches.
Listing merges represent the most disruptive data problem. Google’s automated systems occasionally merge two separate business listings into one, combining attributes from both. If a business in City A gets merged with a similarly named business in City B, the merged listing may appear in local packs for both cities with confused geographic signals. The merged listing might display one business’s address with another’s phone number or reviews. Diagnosing a merge requires checking whether the listing’s CID (customer ID) in the Google Maps URL has changed and whether the listing’s attributes contain information from a different business.
Inherited location data from third-party sources can place a listing in the wrong geographic context. If a data aggregator or directory published the business’s address with an incorrect city, and Google’s entity reconciliation system adopted that incorrect data, the listing may be geographically misclassified. This differs from a boundary discrepancy because the error is in the listing’s data rather than in Google’s geographic boundaries. The fix requires correcting the source data in the aggregator or directory and then monitoring until Google’s system reconciles the correction.
Duplicate listings in different cities can create cross-city appearance patterns. If a previous owner or a third party created a listing for the business at a different address, and that listing was never claimed or removed, Google may surface either listing depending on which one better matches a given query. The business appears to rank in a city where it has no physical presence because an unauthorized listing placed it there. Resolving this requires identifying and requesting removal of the duplicate through Google’s duplicate resolution process.
The diagnostic sequence for cross-city anomalies should first rule out data problems (merges, inherited errors, duplicates) before attributing the anomaly to algorithmic pool expansion or prominence override. Data problems require direct remediation through Google’s support channels and citation cleanup. Algorithmic anomalies require competitive strategy adjustments. Applying the wrong solution to the wrong diagnosis wastes time and may introduce additional complications.
How can a business intentionally leverage cross-city ranking to appear in local packs for adjacent cities where it has no physical presence?
Cross-city ranking cannot be reliably manufactured through optimization alone post-Vicinity update. The most effective approach is building overwhelming prominence signals (300+ reviews, high domain authority, strong local citations) combined with city-specific website content targeting the adjacent city. If the business operates in a low-density category where the target city has fewer than three qualifying competitors, the candidate pool expansion mechanism may pull the listing in naturally. Businesses in high-density categories have minimal realistic opportunity for cross-city inclusion without a physical presence.
Does adding the adjacent city name to a GBP service area help a business appear in that city’s local pack results?
Service area settings have been tested repeatedly by Sterling Sky and Whitespark with consistent findings: modifying service areas does not impact local pack rankings. Adding an adjacent city to the service area field will not trigger inclusion in that city’s local pack. The service area field affects which geographic terms appear in the listing’s description but does not influence the proximity or relevance calculations that determine local pack eligibility. Businesses seeking visibility in adjacent cities must pursue organic landing pages or paid local advertising.
What recourse does a local business have when an out-of-area competitor ranks in its city’s local pack through suspected address manipulation?
File a Google Business Profile redressal form documenting the suspected violation with evidence such as the competitor’s actual physical location from public records, photos showing no business signage at the listed address, or evidence of a virtual office. Additionally, use the “Suggest an edit” feature on Google Maps to flag the incorrect address. Response times vary from weeks to months, and outcomes are not guaranteed. Building the local business’s own prominence signals simultaneously ensures competitive positioning improves regardless of the enforcement outcome.
Sources
- Local Search Forum: Businesses Outside Cities Ranking in Local Pack – https://localsearchforum.com/threads/i-am-noticing-businesses-outside-the-cities-rank-prominently-in-the-local-pack-any-suggestions-or-its-google-doing-its-thing.61803/
- Search Engine Land: What Is the Google Local Pack? How to Rank in the 3-Pack – https://searchengineland.com/guide/google-local-pack
- Local Search Forum: Is Proximity to the Center of a Search Location a Ranking Factor? – https://localsearchforum.com/threads/is-proximity-to-the-center-of-a-search-location-a-ranking-factor.50963/
- Sterling Sky: Does the Service Area in Google My Business Impact Ranking? – https://www.sterlingsky.ca/does-the-service-area-in-google-my-business-impact-ranking/
- Google Developers: Boundaries Coverage for Data-Driven Styling – https://developers.google.com/maps/documentation/javascript/dds-boundaries/coverage
- Salt Water Digital: How to Rank on Google in Multiple Cities – https://www.saltwaterdigital.com/how-to-rank-in-multiple-cities/
