A homeowner searches “AC repair near me,” taps your ad and lands on the corporate homepage. There’s a brand video, a location finder buried in the nav and a phone number that rings at head office. The branch four miles away never hears about the lead. You paid for the click anyway. Multi-location franchises often lose the money after the click, not on the bid.

This list is for franchise marketing leads and owner-operators running Google Ads for several locations. Say you spend $15,000 a month across nine branches. WordStream’s 2026 benchmark report puts average CPC at $5.42 and average cost per lead at $66.69 across 23 industries. That budget buys roughly 2,700 clicks. If a fifth of them hit a preventable leak, you have spent about $3,000 before the weekly report tells you anything useful. Most fixes start with a page for each location, matched to the search rather than copied by hand.

1. Send every local-intent click to its branch’s page

A “near me” search asks for a nearby branch. A national homepage answers with a brand. The searcher has to find a location, check whether it offers the service and work out whom to call. Every extra step is another chance to lose the click. One study of high-ranking local pages found that 28% of a brand’s site visitors went straight to location pages and that those sessions produced revenue. Visitors were already looking for the local answer.

The ad and page also need to agree. Google’s location-assets documentation links a specific business location with a very location-specific landing page. A branch-specific ad pointing at a generic homepage makes the searcher do the matching that the advertiser should have done. That is where I would start diagnosing landing-page relevance, not with another round of bid changes.

First step: give each branch a distinct URL with its address, phone, hours and actual services. If 20% of clicks land on a page that could belong to any branch and half of those visitors leave without finding theirs, that is roughly $1,500 of a $15,000 monthly budget spent on dead ends. The assumption is illustrative; the route to the right branch should not be.

2. Give each location its own call-tracking pool

One tracked number across nine locations tells you that the phone rang. It does not tell you which branch’s ad earned the call. When calls route through head office, that missing detail contaminates every decision about local budgets, territories and performance.

The scale of the problem shows up in a CallRail case study of a mover franchise with 20 North American markets. Before it installed per-market dynamic number insertion, it could confidently attribute only about 65% of revenue to a source. Afterward, calls could be tied to a page, campaign, channel and booked job. You cannot optimise a branch-level result you cannot identify.

Do not solve this by pasting one tracking line across the site. Multi-location call-tracking guidance warns that dynamic number insertion without per-location pools can show a visitor on one branch’s page a number from another branch’s pool. Now the report is precise-looking and wrong.

First step: map each location’s pages to its own number pool, then log call outcomes against the branch that answered. Google Business Profiles also support two additional phone numbers, so a tracking line can sit beside a primary number. I would audit this before changing bids: the rest of the account needs an honest lead count.

3. Separate overlapping territories before the budget drifts

Two branches twelve miles apart may both target “plumber near me” across overlapping radii. The problem is not that you pay to outbid yourself in a private auction. It is that overlapping targeting and pooled reporting obscure which branch should serve the searcher. Spend can flow toward the larger market while the neighbouring branch’s opportunity disappears into the account average.

A marketer describing 18 locations across two states worried that the largest city was taking most of the budget. An agency commenter described the same pooled-budget problem across 15-to-80-location brands: Google favours available volume, not an even allocation among franchisees. The shared-campaign account structure creates another blind spot when a strong city masks weak-market waste. A shared setup may be manageable for two or three similar locations. Nine distinct territories deserve a closer look.

First step: map actual service boundaries against campaign targeting. Then separate campaigns by location or region, use appropriate geographic exclusions and set budgets around local demand. The 28-location franchise case study gives a worked account-architecture example. I would take nine readable territory reports over one flattering blended CPA.

4. Audit location assets and the conversions they create

Location assets pull branch details from Google Business Profiles. An incorrect address or closing time can therefore follow a branch into its ads. This is not an obscure edge case: an audit of 230 local businesses found hours mismatched or missing 27% of the time and phone numbers wrong 18% of the time. A careful marketing team cannot fix a profile it never checks.

There is a second leak. A manager running campaigns for hundreds of US franchise locations reported that two-thirds of All Conversions came from store visits and directions actions. Those actions may matter, but they are not interchangeable with booked jobs or qualified leads. If you let the conversion column treat them alike, bidding can pursue an impressive number that does not answer the franchise’s revenue question.

First step: compare every branch’s profile address, hours and phone with what the branch actually uses. Then inspect which actions enter your primary conversion reporting and bidding goals. Keep the actions that reflect the outcome you want; do not let a directions tap quietly stand in for a lead.

5. Match each advertised offer to the branch that honours it

National marketing runs an $89 tune-up coupon. Four branches honour it, three price it differently and two do not offer the service. The ad promises the tune-up anyway. The customer reaches the nearest branch and hears “participating locations only.” That $5.42 click has bought an argument at the front desk.

This looks like an ad-copy problem, but the shared page keeps it alive. If the page cannot show which offer applies at which branch, the ad can make a national promise that the local team cannot keep. At a $15,000 monthly budget, even a modest stream of those mismatched clicks adds up; the worse cost is that the searcher no longer trusts the answer on the page.

First step: ask each franchisee, in writing, which offers and services they will honour this month. Put that branch’s offer state on its own page, then limit the corresponding ad copy to the branches where the offer exists. If four branches run the coupon, four branches can promise it. The other five cannot.

6. Replace HQ’s hours and service menu with the branch’s

Head office publishes a standard service list and 9-to-6 hours. Branch three closes Sundays and does no commercial work; branch seven opens at 7 a.m. for contractors. A shared page cannot tell both stories accurately. Someone clicks, calls at the wrong time or drives to a locked door. You still pay for the click.

The local-business audit found wrong or missing hours in 27% of the 230 businesses it checked. Copying profile data into a page can save work, but sync is not the same as accuracy. Template-first page platforms can distribute hours from a central source across many locations. If the source is stale, the mistake travels efficiently.

The damage can also feed back into measurement. In some setups, a call still registers as a conversion even when it reaches a closed branch. The account records a successful action at an hour when nobody could take the job.

First step: have each branch manager verify the hours and services shown on the page, then repeat that check quarterly. As an illustration, if 3% of roughly 2,700 monthly clicks reach a branch that is shut when the page says it is open, that is about 81 clicks, or $440 at the benchmark CPC. Hours are not glamorous. Neither is paying to advertise a locked door.

7. Protect new branches from a single shared budget

A new branch in a smaller market needs enough spend to show what it can do. In a shared budget, mature metros already producing conversions can take most of the available spend. The new branch gets fewer chances to generate results; its thin data then makes the next budget decision look easy. It is a loop, not a verdict on the market.

I used to favour equal splits. That is wrong too. Equal budgets ignore differences in local demand and acquisition cost. A shared pool hides those differences; a rigid nine-way split ignores them. Give each branch enough room to test, then judge it on its own marginal results. WordStream’s benchmarks put average cost per lead at $66.69 across 23 industries. That is a sanity check for planning a test, not a universal target for every franchise location.

First step: inspect spend and impression share lost to budget by location. Give new branches a testing minimum and cap mature markets where needed, then adjust each allocation against that branch’s results. If a new location loses 40% of its eligible impressions to budget in month two, do not call it a weak market before checking the pool.

8. Attach every lead to the franchisee who earned it

Even with separate phone numbers, a lead can vanish into head office if forms and call outcomes lose their branch labels during distribution. Central marketing sees a total. Franchisees see leads arriving without a clear connection to their spend. Then the quarterly budget conversation becomes a dispute nobody can settle.

A multi-location franchise discussion describes how messy attribution becomes when everything routes through head office. Practitioners discussing 40-plus corporate locations describe splitting accounts when franchisees pay their own spend, or using campaigns per location when they do not. The useful principle is simpler than either account structure: the lead record must retain the location that earned it.

Without that record, HQ optimises the blend while each owner judges a different set of outcomes. The cost is not just misallocated clicks. It is a budget decision made without the number that would resolve it.

First step: carry a location identifier from the landing page through the form or call to the recorded lead outcome. Use the per-location call pools from entry two, pass the branch through form submissions and give each franchisee a report of their own leads. Before trusting CPA, check whether its conversion count includes store visits and directions requests alongside actual enquiries.

9. Build local pages that stay local after launch

Nine hand-built pages look manageable. They launch with the right hours, a local photo and distinct copy. Six months later, two branches have moved, one has changed its phone number and last year’s holiday hours are still live. Nothing in a neat weekly ad report tells you the page has gone stale.

There is a reason to keep the pages distinct. Research cited on local landing pages reports that unique city-specific content ranked better than templates that swapped only the city name. But uniqueness at launch is not a maintenance plan. Check each location page’s canonical setup, too: franchise SEO guidance flags canonicalisation to a parent page as a risk to the local page’s visibility. A page should not tell search engines that a different page is its preferred version by accident.

The market’s easy answer is a template. Templates help distribute changes, but they do not verify the source. Localith lists pricing for listings and review management; that is a different job from matching a paid click to a local landing page and attributing its lead. Location-page software can carry per-location pricing. Before adding another tool, I would ask whether it connects the page, the ad and the branch-level outcome, or merely makes a larger set of pages easier to publish.

First step: pick one branch and trace a change to its hours from the branch’s source of truth to its profile, page and ad-facing details. If the systems disagree, fix the source before automating the sync. Then ask a page provider three questions: Can the page answer the search behind the ad, not just display a city name? Can the franchisee see leads for their location? Do the accounts, pages and data remain yours if you leave?

Those are the questions I would put to groas, too. Its approach pairs a landing page for every ad group with continuous work on bids and keywords, a named strategist and month-to-month terms that leave the pages yours. A page built per search is useful only if it stays accurate for the branch that has to answer the phone.

If I could start with only one of these nine fixes, I would start with entry two: the phone number. Until I know which branch earned the call, I cannot tell whether the new local page worked, whether the budget moved to the right territory or whether head office sent the lead to the right franchisee.