Geotargeting is the practice of delivering different content, ads, or search results based on a user's geographic location. In paid media it filters who sees an ad. In SEO it means optimising pages to rank for city-, region-, or country-specific queries. Google detects location via IP, GPS, account history, and query language.
Every Google search happens somewhere. Geotargeting is how you make sure the somewhere matches your business — instead of showing a Denver plumber to a Miami visitor and wasting the impression.
What is geotargeting?
Geotargeting is a family of techniques for tailoring digital experiences to a user's location. It shows up in three main places: SEO (location-optimised pages, hreflang, service-area content), paid ads (radius targeting in Google Ads or Meta), and website personalisation (localised content, currency, hours).
Google itself geotargets by default. A search for "plumber" in Denver returns a different local pack than the same query in Miami — even without any location modifier in the query. The system pulls signals from IP, GPS, past searches, and the phrasing itself.
Because Google auto-injects location into most local-intent queries, a page that isn't geotargeted for the right city will lose to a page that is — even when the untargeted page is technically higher quality. Local matches beat quality when the intent is local.
Why geotargeting matters
Four reasons every local, multi-location, or international brand invests in it:
- Relevance = conversion. Location-matched results convert dramatically better. "HVAC repair near me" converts 5-10x higher than untargeted "HVAC repair".
- Local pack qualification. Google's map pack requires a business entity that matches the searcher's location. No geotargeting, no pack.
- Lower CPA on paid. Radius targeting cuts wasted spend on out-of-area impressions.
- Competitive positioning. National brands that don't localise leave the local pack to smaller, more focused competitors.
How geotargeting works
Google (and every ad platform) combines four signals to decide where a user is:
1. IP address → city, region (~city-level accuracy)
2. Device GPS → precise coords (mobile only)
3. Account history → home + work + travel patterns
4. Query language → "plumber Brooklyn" or "near me"
# Delivery decision
filter: pages / ads / results that match location
rank: proximity + relevance + prominence
serve: localised SERP + ads
Geotargeting for SEO — the four moves
- Location-specific landing pages (city, neighbourhood, service area)
- Local keywords used naturally in title, H1, headers, and body
- LocalBusiness schema markup with address, geo coordinates, area served
- Area-relevant backlinks from local publications, chambers, and directories
Geotargeting scopes and when to use them
| Scope | Typical unit | Best for | Signal quality |
|---|---|---|---|
| Neighborhood | 0.5-2 miles | Single-storefront retail, cafes | Highest |
| City | 5-15 miles | Local service businesses, dentists | High |
| Metro area | 25-50 miles | Multi-location HVAC, plumbing | High |
| Region / state | State-level | Regional franchises | Medium |
| Country | Country | National e-comm, SaaS localisation | Medium |
| Language + country | hreflang pair | International SEO | High (with hreflang) |
Real geotargeting examples
1. Regional HVAC — 12 city pages
A Dallas-Fort Worth HVAC company built 12 individual city pages — each with unique service details, technician bios, neighbourhood photos, and customer reviews from that city. Six months later, the company ranked in the local pack for 9 of 12 cities, up from 3.
2. Franchise fitness brand — localised content
each location publishes: "Best 5K races in [city] 2026"
plus: local trainer spotlight, community events
result: 60% lift in location-page organic traffic
3. International SEO — hreflang
A SaaS company serving US, UK, and Australian audiences added hreflang tags for en-us, en-gb, and en-au, plus regional pricing pages. Country-appropriate pages started serving in each region, cutting bounce from 62% to 41%.
Geotargeting vs geofencing — which one
They sound similar. They operate at very different scales.
Use geotargeting when
- You want city, region, or country reach
- The goal is SEO or long-lived ads
- You're building location landing pages
- You need international SEO (hreflang)
- Radius is measured in miles
Use geofencing when
- You need block- or venue-level precision
- You want to trigger on physical entry
- You're conquesting competitor locations
- You need offline foot-traffic attribution
- Radius is measured in feet
7 best practices for geotargeting
- Give every location a unique page. Templated city pages with only the city name swapped get filtered as thin content. Unique testimonials, team, and photos per location.
- Use LocalBusiness schema on every location page. Include address, geo coordinates, area served, and opening hours.
- Match paid radius to your service radius. Don't run city-wide ads on Google if you deliver in three postcodes.
- Localise the content, not just the URL. Weather references, local landmarks, and neighbourhood-specific pain points.
- Use hreflang for international targeting. One page per language + country pair, all cross-referenced.
- Build local citations. Local chambers, city directories, and industry-specific directories with a footprint in the target area.
- Track by location, not aggregate. Aggregate metrics hide that one location is winning and another is dying.
The most common local SEO fail is 100 city pages that swap the city name and nothing else. Google identifies these as doorway pages under its guidelines and either ignores or actively demotes them. Unique content per location is the only path.
Common geotargeting mistakes
- Templated city pages — treated as doorway pages under Google's guidelines.
- Wrong radius in paid ads — burning budget on impressions outside the service area.
- Missing LocalBusiness schema — leaves entity signals ambiguous.
- Using ccTLD without hreflang — fragmenting authority across country domains without connecting them.
- Aggregating reporting across locations — hides underperforming outlets that need attention.
How theStacc helps with geotargeting
theStacc's Local SEO module tracks Maps rank, Local Pack rank, and organic rank as three separate numbers per keyword, and publishes Google Business Profile posts and review replies for each location you connect. Reporting stays broken out per location rather than smashed into one aggregate, so you can see which market is actually moving.
Frequently asked questions
Geotargeting delivers content or ads to anyone matching a location signal (city, region, IP). Geofencing triggers a specific action when a device physically enters a defined virtual perimeter. Geotargeting is broader; geofencing is narrower and event-driven.
Google combines IP address, device GPS, account history, and query language (e.g. adding "near me"). Signed-in users on Android give the strongest location signal; anonymous desktop users rely on IP.
Service area businesses create service area pages, publish location-specific content, build citations that mention each city served, and optionally run geo-targeted ads in the same footprint.
Yes. Use hreflang tags for language + country pairs and country-code top-level domains (ccTLDs) or country-specific subdirectories to signal geographic targeting to Google.
Google reports geotargeted campaigns perform roughly 20% better on average than non-geotargeted equivalents. Near me queries specifically convert 5-10x better than generic keyword variants.
Related glossary terms
Sources
