NAP and Phone Mismatch: Ads, GBP, and the Website in Nepal (2026)
NAP is Name, Address, Phone. Nepal stacks often have a site number, a GBP number, a call-extension number, and a WhatsApp on someone’s private SIM. Arjan KC wants one public +977 everywhere a customer can see it. Playbook: local SEO. Ads taps: call vs WhatsApp. GBP link: Ads + GBP.
→ ORM · Citations (2024) · Canonical host
Reputation-adjacent object
Clinic Maps views ~+340% and search/Maps calls ~+85% after GBP + local pages — /case-studies/kathmandu-healthcare-clinic/. That needs a number people can actually ring. Home-services Search −42% CPA used call tracking in the rebuild — /case-studies/kathmandu-home-services-google-ads/. Neither object says “change the number three times.”
Image: Arjan KC media library.
One public line
| Surface | Shows | Notes |
|---|---|---|
| Website footer / landing | Public +977 | Same as schema telephone
|
| GBP | Same +977 | Primary owner, not a staffer’s phone |
| Call extension | Public or documented forwarding | Call reporting |
| Same org number or labelled desk | Not a personal chat that leaves with an intern | |
| Directories | Same NAP string | Older citation post above |
Address format: one ward/tole/street spelling. www vs apex on the URL field.
Image: Arjan KC media library.
What breaks when they differ
- Ads conversion = forwarding ID; GBP Insights = other line; offline import matches neither.
- Festival hours updated on GBP only → Ads still “Call now.”
- Quality Score landing experience includes “can I reach you.”
Company owns GBP + Ads so you can fix this without a vendor Gmail — ownership.
Next: GBP 2026 · local SEO Nepal · hire Local Demand.
