Lalitpur NAP hygiene
No Thamel phone on a Patan listing.
Patan Durbar Square traffic is not the same as Kupondole office lunch. If the kitchen is in Lalitpur, citations and GBP must say Lalitpur. Hub: restaurants Nepal. City: digital marketing Lalitpur.
See the Restaurant Marketing Nepal hub for Nepal-wide strategy. Everything below is specific to Lalitpur.
Valley ads can prospect Kathmandu; the money page and map pin stay Lalitpur or you train Google that you are a Kathmandu restaurant. Heritage-area hours and resident delivery radii need two offer URLs when they conflict.
English menu pages, GBP categories, photos that match the courtyard you actually have.
Nepali weekday offers, school-area lunch, delivery polygons you honour.
No Thamel phone on a Patan listing.
Indexable dishes; Newari specialty pages only if you serve them daily.
Lalitpur + adjacent only if riders cover it.
Patan heritage dining vs Kupondole office lunch. NAP must say Lalitpur. Hub: restaurants.
Most campaigns in Nepal lose on slow mobile pages and vague landing copy — not on audience size. DataReportal’s Digital 2026: Nepal (late 2025) puts internet users at about 16.6 million (~56% of the population), with most people on phones and roughly nine in ten online users on at least one social platform. Kathmandu and the Valley skew higher than remote districts; even in cities, Nepali copy and tight geo-targeting usually beat a one-size English campaign.
Channel mix follows the full digital marketing stack: Maps and SEO for local intent, Search/Meta when the landing URL matches the query, WhatsApp or call as the close path, GA4 so festival spikes are inquiries not vanity reach. Numbered proof lives on case studies only.
Related: Digital marketing Nepal · Hire.
Say so on the page with a radius. GBP still belongs at the kitchen.
Two GBPs, two pages. See Kathmandu restaurant page for the other kitchen.
Platform policies apply. We will not run prohibited creatives.
Send the Lalitpur GBP pin and menu URL. Request a Patan/resident F&B split.