A customer sits in Dallas and searches “plumber in Plano.” Your franchise has a shop in each city. The expensive mistake is getting the right shop into the ad and sending the click to a page that could belong to either one.

There are four separate signals to follow: where the searcher is versus where they show interest, the geography in the query, the addresses eligible to appear with the ad, and the final URL. The first three help Google determine which ad can appear and what local information it can show. They do not write the page the customer sees after the click. I ran home services accounts long enough to watch that handoff go wrong. Targeting deserves attention, but the page is where a well-matched click most often gets wasted.

1. Presence decides who is eligible—not where the job is

Start with the customer’s location. Google distinguishes physical presence from interest in a place. Presence means someone is in or regularly in a targeted area. Interest can come from search terms, recent presence, or content viewed about that location. Google calls this matching best effort, not perfect.

That distinction matters because the default is Presence or Interest. A Plano campaign using that setting may reach someone outside the area who has shown interest in Plano. Sometimes that is useful: our Dallas searcher may be arranging plumbing work at a Plano address. Sometimes it buys curiosity from someone who cannot book a job there.

I used to tell clients to leave the default alone. I was wrong for service businesses whose customers need a truck at an address inside a defined service area. One home services example I still use as a reference point spent $542.84 of a $4,500 budget on 41 clicks from outside Arizona, at $13.24 each. Those clicks were a reminder to check where interest was coming from, not a reason to assume every out-of-area search is worthless.

For a tightly local campaign, I start with Presence. But Presence is a gate, not an interpretation of the query. If the Plano campaign targets only Plano by Presence, our customer sitting in Dallas does not become physically present in Plano by typing its name. If booking from another city is valuable, the targeting has to permit that behavior. Decide which bookings you can actually serve before deciding how widely to admit interest.

2. Query geography tells you what the customer wants

Now read the words “plumber in Plano.” Dallas is where the customer is; Plano is where the customer says the job is. That explicit place name gives you information GPS cannot. It does not, however, override a campaign’s location eligibility. Google can use the query as a signal of interest only within the targeting you have allowed.

Compare three searches from the same phone:

  • “Plumber in Plano” names the intended city. If your settings permit interest-based reach, the Plano campaign has a reason to enter the picture.
  • “Plumber near me” supplies no city name. Device location becomes more important, so Dallas is the more natural local match.
  • “Emergency plumber” names neither a city nor a distance. Location settings and eligible assets have more work to do.

ZIP codes can narrow the intended area further. City names are useful, but “near me” is fuzzier than it looks in a franchise account. When several units sit within 15 miles of one another, their targeting can overlap. Practitioners suggest ZIP exclusions or bids that prioritize the closest unit to keep neighboring locations from chasing the same broad local demand.

That does not mean excluding Dallas from every Plano campaign. Do that, and you may shut out the Dallas customer who needs a Plano plumber. The practical move is to read search terms alongside location performance and ask two questions in order: where does this person appear to be, and where do the words say the job is? A geo-modifier is evidence of intent, not a waiver of your targeting rules.

3. Location assets decide which address the ad can show

Once a campaign is eligible, the ad still needs to look like it belongs to the right shop. Linked Google Business Profiles can sync addresses into location assets. You can attach all locations or a location group containing only a subset to a campaign or ad group. There is also an affiliate option for businesses selling through stores they do not own.

That attachment is the part I check first. If a Plano campaign can show only its Plano address, the ad has a coherent local identity. If every campaign can show every address, you have given Google far less help distinguishing one branch from another. The asset does not repair a messy account structure; the structure controls which addresses are available.

The setups I see work are boring on purpose. Where markets behave alike, an ad group per location under one campaign can keep the account manageable. Where budgets or search behavior differ, a campaign per location gives each unit more room. Past a dozen units, regional clusters can make more sense. Ad customisers can then insert an approved town and offer into the relevant account, campaign, or ad group copy. None of that makes a shared national page local. It only makes the ad local.

Return to Dallas and Plano. If the Plano campaign is allowed to reach the Dallas searcher’s expressed interest, carries the Plano location asset, and uses Plano copy, the ad can answer the query cleanly. If it is restricted to Plano Presence, no amount of Plano wording or asset setup makes that Dallas-based searcher eligible. Sort out eligibility first. Then check which address an eligible ad is allowed to show.

4. The final URL has to keep the ad’s promise

The click is the handoff Google will not fix for you. It will not rewrite a homepage URL into a Plano shop page because the query, headline, and address all say Plano. If the ad points to a national franchise page, that is where the customer lands.

Picture the sequence from the customer’s side. They type “plumber in Plano.” The ad says Plano and shows a Plano address. They click. The page presents a national scheduler, a general phone number, and a list of cities they must search again. The ad answered their question; the page handed it back. That mismatch can hurt Quality Score and conversion, but you do not need either metric to see the problem. Someone ready to call now has extra work to do.

Shared pages also blur what the account learns. When Plano and Dallas clicks lead into the same experience, an acceptable aggregate CPA can conceal very different results by location. One unit may be getting the bookings while the other pays for clicks that never find its phone number. I have watched that kind of mismatch persist because the combined number looked fine. It was fine in the way an average of one starving location and one flooded location is fine.

The first three signals help match the search to an ad. The final URL determines whether the destination honors that match. It cannot guarantee a booking. It can avoid making a customer repeat the location choice they already made.

Trace the Dallas click before changing bids

Here is the full chain, with the targeting condition kept in view:

  1. Check eligibility. The customer is in Dallas. A Plano campaign limited to Plano Presence will not reach them on the strength of “Plano” in the query. A campaign configured to admit relevant location interest may.
  2. Read the query. “Plumber in Plano” identifies the intended job location. That is different from “near me,” which would lean on the customer’s Dallas location.
  3. Check the eligible address. A Plano-focused campaign should have access to the Plano location asset, rather than an unrestricted collection of franchise addresses.
  4. Open the final URL. The customer should arrive at the Plano page, with a clear way to contact that shop. A national page breaks the chain after you have paid for the click.

This order prevents a common bad fix: increasing the Plano bid because its ad is underperforming when the actual problem is a generic destination. It also prevents the opposite mistake, building an excellent Plano page while a Presence-only campaign excludes the Dallas customers who need it.

Watch exclusions while you work. They operate on Presence only by default, so an inclusion based on Presence or Interest and an exclusion based on Presence do not form a perfect mirror. Someone outside an excluded area who expresses interest in it can still fit through that gap. Radius settings deserve the same care: the interface pre-fills 20 miles, and a radius does not respect city borders. Practitioners recommend starting around 5 miles and adding explicit negative ZIPs and cities where that fits the service area. Use the actual booking footprint, not a tidy-looking circle, as the test.

Give the Plano page proof that it is Plano

A per-location page is not a corporate page with a city token swapped into the headline. That approach scales production, but it does not give the customer much reason to believe they have reached the right branch. Nor does it give each page much distinct local substance.

Start with the details that establish which shop this page represents:

  • A distinct URL, such as brand.com/locations/plano-tx.
  • The shop’s name, address, and phone number matching its Google Business Profile.
  • Hours, including holiday hours, and a map.
  • LocalBusiness schema in the page code.

Then add what helps a person decide to call: photos of the branch rather than stock vans, reviews that mention the town, local FAQs about the service area or seasonal work, a staff introduction, and a call button that reaches the shop instead of headquarters. The older franchise PPC rule is still useful here: match the ad headline and make the local address, phone, hours, testimonials, mobile layout, and fast load easy to find.

Not every page needs to read like a completely different business. The system can be shared. The evidence should not be interchangeable. If I put the Plano and Dallas pages side by side and only the city name changes, I would fix that before raising either budget. A visitor should not have to scroll to discover which location they reached.

Test a vendor on the URL, not the local-ad pitch

Ask a vendor how it handles 40 locations and listen for where the explanation stops. Campaign targeting, town names in headlines, and synced addresses cover the first three signals. The fourth requires a page for the shop the ad promises.

I would ask four questions before connecting an account:

  1. Does each ad group get an appropriate final URL, rather than the same corporate destination?
  2. Does that page carry the shop’s matching name, address, phone, hours, map, and LocalBusiness schema?
  3. Are its copy, reviews, photos, and FAQs specific to that shop?
  4. Will those pages remain distinct as more locations are added?

A city-token demo does not pass that test. An intent-built page keeps a repeatable structure while changing the local evidence. The Tampa page can address mold and algae in summer humidity; the Denver page can address freeze-thaw cycles and ice. Same system, different reason for the customer to trust the match.

That is why I point franchise operators to Google Ads for multi-location businesses that treat account structure and pages as one system. It is also where groas has the stronger answer to this particular job: Search Ads at $1,499 a month includes a landing page built for every ad group, so Plano and Dallas do not have to share a final URL. An agency can polish the targeting report all month. If the click still lands on the national page, the customer gets the same extra homework.

Now change the case. Someone in Fort Worth searches “emergency plumber near me” at 10pm. There is no city in the query, so you cannot use an explicit place name to identify the intended branch. Start with the person’s location and the campaign’s eligibility. Next, check whether an eligible ad can show the Fort Worth address. Finally, follow its URL.

If the Fort Worth campaign uses Presence, carries the Fort Worth location asset, and points to a page with that shop’s after-hours number, reviews, and map, the chain stays intact from search to possible call. A national page with a national phone tree breaks it at the last step. Neither setup guarantees the job. Only one answers the search without asking the customer to sort out your franchise structure.

That is the order I use when I audit: presence and interest, query words, eligible addresses, final URL. I keep the 31-point pre-flight checklist for franchise locations open because the page items are easy to miss. Get those right, and the first three signals finally have somewhere useful to land.