Local Services Ads for Multi-Branch Service Networks

Local Services Ads rank on operations, not on bid. The strongest single lever across the profiles I have worked on is call answer rate: a branch that misses a quarter of its inbound calls sits below a competitor with a worse review score and a smaller budget, and no amount of money buys the position back. That sets the shape of this engagement. I run the profile, the verification and the lead ledger, and I tell you which branch is losing rank because the phone rings out after four in the afternoon. Eligibility, before any money moves: Local Services Ads runs on a fixed category list that differs by country, and there is no route in for a service that is not on it. Recruitment and staffing has no category in the UK, so if that is your business, this is a Search and Demand Gen problem instead and you will hear that on the first call. For eligible categories, verification is the gate: business registration, public and employer's liability cover at the levels Google specifies, trade licences where the category demands them, and background screening on named people for Google Screened categories. I make the submissions, chase the ones that stall, and keep an expiry calendar, because a lapsed certificate takes a profile down without warning and reinstatement is slower than renewal. What ranking actually responds to: Proximity to the searcher, review volume and score, responsiveness, stated hours, and your own dispute behaviour. Each of those is an operational task here rather than a setting. Hours in the profile get set to the hours a human answers, not the hours on your website. Service areas are drawn postcode by postcode against where you can genuinely attend, because a lead you decline still counts against the profile. Review requests go out through the Google-generated link inside forty-eight hours of job completion, and I will put that step into your job-close process rather than emailing you the link and hoping. Disputes: Every lead is reviewed inside the dispute window. Wrong category, out of area, spam and abandoned calls get disputed with evidence attached. Genuine leads your team simply failed to convert do not, because a profile carrying a high dispute rate gets scrutinised and eventually throttled. The dispute rate stays visible in the weekly report so you can see for yourself where the line sits between recovering money and damaging the account. Budget, and the pause trap: Budgets here are weekly, and pausing a profile does more damage than lowering it. Recovery of position after a pause has taken weeks in every account where I have watched it happen. So the budget is set to a number you can hold through a quiet month rather than one that looks right in a good one, and seasonal reduction happens by lowering, never by pausing. Reporting: Leads pulled daily from the Local Services Ads API, detailed lead reports and account reports both, into a sheet keyed to your CRM record, so the number in front of you is cost per booked job by branch rather than cost per lead. Charged leads are reconciled against disputes and credits every month, and the reconciliation is yours to keep. What I will not do: Answer your phones, or arrange an answering service to do it. Write, buy, incentivise or filter reviews. Handle a Business Profile suspension appeal. Run your standard Google Ads Search account under this engagement, which is related work, separately scoped and separately priced. Not for you if: You run one location and the honest workload is two hours a month. Your team cannot answer reliably inside your own stated hours, which is the failure this channel punishes hardest. You want the channel managed as a bidding surface with levers to pull each week. Or you expect a lead volume number defended when your service area is genuinely small, because the ceiling here is set by geography and I would rather say that before you buy than after.