Google Ads Geo Targeting in Nepal: Valley, Country, and India Leak (2026)
Location targeting decides who is allowed to see the ad. Nepal SMEs often set the country and leave Presence or interest, then wonder why CPC buys Indian research traffic. Arjan KC sets Presence for local services and only opens interest for products that actually export or host tourists. Service: Google Ads Nepal. SEM.
→ Account ownership · Call vs WhatsApp · Local SEO
Cite Search objects, not a geo %
- Home services −42% CPA — /case-studies/kathmandu-home-services-google-ads/ (Kathmandu services, not “South Asia”)
- Education −40% CPL — /case-studies/nepal-education-consultancy-ppc/ (intent can be national; still watch Locations)
Do not invent “X% of budget leaked to India” as a survey.
Image: Arjan KC media library.
Defaults that usually work
| Business | Target | Setting |
|---|---|---|
| Clinic, plumber, cafe | Valley or radius around the pin | Presence (people in or regularly in) |
| Consultancy with Nepal-wide calls | Nepal + exclude cities you refuse | Presence; language as needed |
| Hotel / trek / inbound education | Nepal + feeder countries you want | Presence in Nepal plus a separate campaign for interest from IN/AU/EU if the landing is for them |
| Everyone else “testing” | Not “worldwide” | Locations report weekly |
Exclude India (and random APAC) on a Lalitpur dentist unless you have a medical-tourism brief. Tourism brands: separate campaigns so Kathmandu CPC and Delhi interest CPC are not one blended CPA.
Radius pins lie if the GBP address is wrong — GBP / Ads · NAP.
Image: Arjan KC media library.
How to catch leak
- Google Ads → Locations → where ads showed (not only the targeting list).
- Search terms:
in india, foreign city names, visa-only queries you do not serve. - Negatives.
- PMax location reports are thinner — fix Search first.
Festival spikes do not justify worldwide.
Next: Quality Score · audit · hire.
