Problem (shared pattern)
Trades lose money on wasted Search queries and weak Maps/local pages; calls and WhatsApp are the real conversions, not homepage bounce rates alone.
Get our stories in Top Stories with a preferred badge.
One stack view of two published engagements — Google Ads CPA work and local SEO lead growth. Client names withheld on the source pages. This page adds no new numeric KPIs.
Source URLs only: Google Ads case · Local SEO case. Different timelines and (where stated) different accounts — do not treat as one blended P&L.
The engagement
Trades lose money on wasted Search queries and weak Maps/local pages; calls and WhatsApp are the real conversions, not homepage bounce rates alone.
Local SEO/GBP and service pages capture “near me” and brand demand cheaply; cleaned Search campaigns buy emergency and high-intent jobs without funding DIY/competitor waste. WhatsApp and click-to-call sit on both layers.
No combined “stack ROAS” or invented single-client blend. Cite Layer A and Layer B figures separately from their source pages.
Operators often ask whether to “do SEO or Ads first.” The published answer on this site is both jobs, sequenced: stop Search waste and fix landings for paid; build GBP + service pages for durable local demand. Numbers stay on the two case URLs — this page only shows how they fit together.
Do not merge the two timelines into one “before/after” chart. The Ads window is 90 days; the local SEO window is six months. Client identities remain withheld as on the source pages. For city nuance, start from the national hub and Kathmandu home-services pages linked from home services marketing.
No additional lead lifts, occupancy-style %, or blended ROAS are claimed here.
Next step
Message @gurkhatech with trade type, city, and whether Maps or Ads is the bottleneck.