"Near me" is the highest-intent query structure in local search. Someone typing "roofer near me" into their phone is almost always within hours of calling a contractor. Winning those queries is commercially transformative for any local service business.
The mechanics of how "near me" queries resolve have quietly shifted since 2025. Proximity used to be the dominant signal, closest business wins. In 2026, proximity is roughly 3% of the equation. S2 Occupancy, Entity Trust, and BERT-scored relevance drive the result. This is what makes it possible, through the Near Me Domination methodology, to rank in a competitor's neighborhood while physically sitting 20 miles away.
This is the Near Me SEO playbook. How the queries actually resolve, the radius expansion formula, the distance decay override, and the specific tactics that move you into the Map Pack for "near me" queries across your entire service area.
Part of our Google Maps SEO in 2026 cluster.
Run the free GeoGrid scan to see exactly how you rank for "near me" queries at every point in your service area.
How "Near Me" Queries Actually Resolve
The lifecycle of a "near me" query is deterministic. Understanding each step lets you engineer against it.
Step 1: Location Resolution
Google reads the searcher's location via GPS (mobile), IP geolocation (desktop), or explicit setting (Google Maps). The location resolves to an S2 cell at multiple levels simultaneously, the Level-14 cell for precision, plus containing Level-13, 12, 11, 10 cells for broader context.
Step 2: Query Intent Classification
BERT parses the query. "Near me" is a strong explicit local intent signal. "Near me" plus a category ("roofer near me") narrows the candidate pool to that category. Some queries have implicit near-me intent even without the phrase ("emergency plumber" from a mobile device), Google treats them similarly.
Step 3: Radius Draw
Google draws a rough 1–2 mile candidate radius around the searcher. The exact radius varies by query category and local density: urban emergency services get tighter radii (0.5–1 mile), suburban categories get wider (2–5 miles), rural queries can extend to 10+ miles because nothing closer exists.
Step 4: K-Cluster Candidate Pool
Google pulls every business indexed in the Level-14 cells intersecting the candidate radius, filtered by category match. This is the K-cluster. See the Map Pack article for the two-stage selection pipeline.
Step 5: Three-Seat Ranking
Within the K cluster, Google ranks by S2 Occupancy + RSVM + Entity Trust + Distance Decay and returns the top 3 as the Map Pack.
Where Distance Still Matters
Distance decay is the tiebreaker at Step 5 when other signals are roughly tied. If five businesses in the K cluster have similar S2 Occupancy, RSVM, and Entity Trust, the closest one wins. If one business has materially stronger signals across the other three factors, distance concedes.
This is why the strategy is not "get closer to your customers" but "get stronger signals in every cell your customers live in."
The Radius Expansion Formula
At Digital Domination we compress the radius expansion mechanics into one formula:
NavBoost + Semantic Agreement = Radius Expansion
Both terms are signals you can engineer.
NavBoost
NavBoost is Google's aggregation of real-world behavioral data tied to locations. When customers physically travel to your business (or request directions, or check in, or call), Google's Maps infrastructure records the origin-destination pattern. Businesses that consistently get direction requests from specific S2 cells build a NavBoost signal for those cells.
The practical consequence: a roofer whose customers frequently drive in from Summerlin (even though the shop is in Paradise) gets reinforced in Summerlin's K-cluster pool. NavBoost is slow to build but durable once established.
Operator levers for NavBoost:
- Consistent NAP and correct GBP address (so direction requests resolve)
- Encourage customers to use Google Maps directions rather than GPS apps (small behavioral nudge)
- Consistent business hours so customers complete direction-request-to-arrival patterns
- Active Google Posts referencing service area neighborhoods (reinforces area association)
Semantic Agreement
Semantic Agreement is the BERT-scored match between your on-page content and the geographic elements of a target S2 cell. Landmarks, roads, zip codes, microclimate, local cost data, neighborhood-specific FAQs. Covered in detail in the ranking factors article under RSVM.
Sentence vectors that link Service + Neighborhood + Action imply frequent physical presence in that area. Example:
- Weak: "We do roofing across Las Vegas."
- Strong: "Our crews install Owens Corning asphalt shingle replacements on Summerlin homes, including the older flat-roof properties near Red Rock Canyon that need specialized membrane work before monsoon season."
The second sentence agrees semantically with Summerlin specifically, it mentions a specific landmark, a specific microclimate concern, a specific product match for the neighborhood's housing stock. Google reads this as evidence that your business operates in Summerlin.
Operator levers for Semantic Agreement:
- Neighborhood spoke pages with real landmarks, microclimate, cost data
- Service page descriptions that reference multiple specific neighborhoods
- Google Posts that call out specific service areas with specific language
- Review responses that mention the customer's neighborhood when natural
The Compound Effect
NavBoost and Semantic Agreement compound. Real customers driving in from Summerlin + spoke page matching Summerlin landmarks + Google Posts about Summerlin jobs + reviews from Summerlin customers = strong Summerlin K-cluster eligibility even though your shop is 20 miles away in Paradise.
This is the Near Me Domination methodology in its simplest form. Build both signals in the cells where your customers live. Distance decay concedes when the other signals are strong enough.
The Distance Decay Override
Two businesses in the same K cluster:
- Business A: Located in Summerlin, average S2 Occupancy, weak Entity Trust, weak spoke content
- Business B: Located in Paradise (20 miles from Summerlin), strong S2 Occupancy across Summerlin cells, strong Entity Trust, strong spoke content
For a "roofer near me" query from a customer in Summerlin, Business A has a 20-mile distance advantage. Business B has strong signals across everything else.
In the pre-2025 model, Business A wins, distance was ~80% of the equation.
In 2026, Business B wins more often than not. Distance decay is roughly 3% of the equation, and the remaining 97% favors Business B's signal stack. This is the distance decay override, and it's the reason Near Me Domination is commercially transformative for operators who build the signals correctly.
When the Override Fails
Distance still decides when:
- Your signals are roughly tied with a closer competitor (distance breaks the tie)
- The closer business has dramatically better reviews or a much longer review history
- You're trying to rank in cells where you have zero indexed presence (no spoke, no citations, no GBP tie-in)
- Extreme distance (50+ miles) where the cognitive "near me" intent breaks down
The override is not magic. It's the predictable outcome of stronger signals outweighing weaker-plus-closer signals.
The 20-Mile Playbook
Concrete playbook for operators who want to rank in service-area cells 10–20 miles from their storefront.
Phase 1: Audit Your Current Radius Reach
Run a GeoGrid scan with a 10-mile or 20-mile radius. The heatmap shows exactly where your current signals fade. The "Radius Reach" component of your AI Trust Score quantifies it.
Phase 2: Target the Underserved Cells
Not all cells at 20-mile distance are equally attackable. Some are dominated by strong local competitors; others are genuinely underserved. Focus on:
- Cells where the current Map Pack top 3 have weak signals (low review count, no visible spoke content, thin GBP)
- Cells where your closest real competitor is also 10+ miles away (no geographic advantage to anyone)
- Cells with high commercial intent for your vertical (wealthier neighborhoods, new construction areas, etc.)
Phase 3: Deploy Spoke Pages for Target Cells
Build neighborhood spoke pages for each target cell. Each spoke gets:
- Real landmarks, real microclimate, real cost data specific to that cell
- Real photos from the cell (even if you haven't worked there yet, drive through and shoot)
- Hub-and-spoke linking pattern
- BERT-optimized content with service + neighborhood tight proximity
- FAQ schema with cell-specific questions
See the Hub-and-Spoke Silo guide for the deployment workflow.
Phase 4: Build NavBoost Signal
NavBoost needs real behavior. Options:
- Light marketing push into the target neighborhoods (flyers, door hangers, local paper ad) that includes the GBP address and encourages Google Maps direction use
- Partnerships with complementary businesses in the target cells (referral arrangements that generate direction requests)
- Service delivery in the cells once leads start arriving (even low-margin jobs in year 1 build long-term NavBoost)
Phase 5: Semantic Agreement Maintenance
Don't let spoke content go stale. Quarterly refresh with new landmarks, new cost data, new photos. Google Posts that mention the target neighborhoods. Review responses that reference the neighborhood when real customers mention it.
Timeline
NavBoost signals take 3–6 months to register meaningfully. Semantic Agreement via spoke pages takes 6–8 weeks to index. Combined, a meaningful radius expansion typically lands 4–6 months after deployment starts.
Near Me SEO vs. Google Maps SEO vs. Local SEO
These three terms overlap but aren't identical. The distinctions matter for scoping work.
| Term | Scope |
|---|---|
| Near Me SEO | Optimizing specifically for "near me"-style queries across the geographic grid |
| Google Maps SEO | Optimizing for the Google Maps Map Pack (includes near-me, but also explicit geographic queries, direction-based queries, and Map Pack appearance) |
| Local SEO | The full scope: Map Pack, local organic results, directories, citations, reviews, offline conversion tracking |
Near Me SEO is a subset of Google Maps SEO, which is a subset of Local SEO. The methodology, S2 Occupancy, Entity Trust, BERT relevance, hub-and-spoke silos, is the same across all three. The difference is the surface you're measuring and the specific query patterns.
Near Me SEO FAQ
What is a "near me" search?
A "near me" search is a query that includes the phrase "near me" (or has implicit near-me intent from a mobile device) and expects a local-business result. Examples: "roofer near me," "emergency plumber near me," "best pizza near me." They're the highest-commercial-intent query pattern in local search.
How does Google decide which businesses to show for "near me" searches?
Google reads the searcher's location, draws a 1–2 mile candidate radius, pulls every business indexed in the intersecting Level-14 S2 cells (filtered by category match), and ranks the K cluster using S2 Occupancy + RSVM + Entity Trust + Distance Decay. The top 3 surface in the Map Pack.
Can I rank for "near me" searches outside my physical location?
Yes. With strong neighborhood spoke pages, Entity Trust Compression, and NavBoost signals, businesses routinely rank for "near me" queries 10–20 miles from their storefronts. The distance decay factor is roughly 3% of the ranking equation in 2026, it's the tiebreaker, not the decider.
How important is physical proximity for "near me" rankings?
Less than most operators assume. Proximity was ~80% of the signal in the pre-2025 model. In 2026 it's closer to 3%. The other 97% is S2 Occupancy + RSVM + Entity Trust, which are engineerable signals. Strong signals routinely beat closer competitors with weaker signals.
What's the difference between "near me" and "in [city]" searches?
"Near me" searches use the searcher's real-time location. "In [city]" searches use the city name regardless of the searcher's location. The ranking factors are similar but "in [city]" queries engage broader S2 cell pools (Level-10 or 11 rather than Level-14) because the geographic anchor is the city, not the searcher's point.
Do "near me" searches work the same on desktop and mobile?
Mobile "near me" searches resolve to tighter, more precise S2 cells because GPS location is typically more accurate than IP-derived desktop location. Desktop queries sometimes resolve to broader cells (city-scale rather than neighborhood-scale). Both use the same K-cluster mechanism, just at different granularity.
Does voice search change "near me" SEO?
Voice search ("Hey Google, find a roofer near me") uses the same Maps ranking pipeline underneath. The surface differs, voice returns a single top recommendation rather than a Map Pack, which amplifies the importance of ranking #1 for voice-triggered queries. The factors are identical.
How do I measure my "near me" ranking across my service area?
Run a GeoGrid scan. Our free scan samples your Map Pack position at 49 or 169 grid points across your service area. The heatmap shows exactly which cells rank you top 3, which are positions 4–10, and which are invisible. Single-coordinate rank trackers miss this distribution entirely.
Next Step: See Your Near Me Coverage
Near Me SEO is invisible without a grid-level measurement. A single-number rank tracker hides the per-cell reality, which is the only reality that matters.
Thirty seconds to start. Heatmap by email in two minutes. See your near-me coverage, competitor positions, and monthly dollar leak.
If your scan reveals that you're losing near-me queries across most of your service area and your vertical plus territory is open, the Maps Domination Programâ„¢ deploys the full Near Me Domination methodology (S2 Occupancy, Entity Trust, Radius Expansion, Geolock Defense Matrixâ„¢) in 12 weeks or you don't pay the success fee.
Methodology from The Google Maps Domination Playbook by Nick Thompson. For the broader framework, see Google Maps SEO in 2026, S2 Cells and Google Maps, and Google Maps Ranking Factors 2026.
