How to Set Up Google Ads Location Targeting for Agencies
To set up Google Ads location targeting for an agency-managed account, turn the client’s approved service map into campaign targets, choose the geographic unit that supports the client’s operating decision, select presence or interest reach with a documented reason, add exclusions and ownership rules, and test the page, phone, form, and sales handoff. An agency should be able to explain every location setting to the client and connect it to qualified outcomes.
Google’s location-targeting overview and advanced location options describe the platform controls. The following process adds the client approval, change management, and reporting steps an agency needs around those controls.
1. Get an approved client location brief
Do not start by copying locations from an old account or selecting every place where a keyword has search volume. Ask the client to define where the advertised service can be sold, delivered, installed, staffed, or legally provided. Record branches, service areas, technician bases, delivery limits, sales territories, licenses, minimum job values, opening hours, languages, and capacity.
Separate the customer’s address requirement from the business’s marketing reach. A national software consultation, a regional sales meeting, and a local repair visit may all belong to the same client but need different campaigns or pages. Have the client approve included areas, excluded areas, effective date, owner, and exceptions. Save the brief with the account so the next agency operator can understand why a place was selected.
2. Decide the campaign boundary
Keep locations together when they use the same offer, page, phone number, budget, language, schedule, conversion action, and sales owner. This avoids unnecessary fragmentation and makes the account easier to maintain. Separate locations when the client needs a distinct budget, margin, branch, service level, message, landing page, or follow-up team.
Select the right geographic unit
Choose a country, region, city, postal area, or radius according to the way the client fulfills work. Use a radius around a meaningful branch, store, clinic, warehouse, or technician base when travel and dispatch matter. Determine the distance from road time, job history, delivery cost, and capacity. Inspect the map for boundaries, rivers, highways, and areas the client cannot serve.
Do not create a campaign for every neighborhood unless each split has an actionable budget and a business decision attached to it. An agency can preserve detail in a reporting table without turning every small area into a thin campaign.
3. Add and verify the locations in Google Ads
Open the campaign’s location settings and search for each approved country, region, city, postal area, or supported target. Confirm the place name and country before saving. For a radius, verify the center pin and inspect the coverage map. Keep the approved location brief open while entering settings; similar place names are easy to select incorrectly.
Use Google’s location-targeting documentation to check the current interface and supported target types. Store a screenshot or export of the final settings with the change record, but do not treat a screenshot as a substitute for a client-approved map and operational test.
4. Choose the location option and record the reason
Choose a presence-focused option when the client needs the customer to be in or regularly in the service area for an appointment, delivery, repair, or regulated service. Consider interest-based reach only when people outside the area may legitimately plan a local event, move, trip, or purchase the client can serve. Write the selected option and the business reason in the agency change log.
Google explains these advanced location options, but location signals are not a perfect address-level fence. Plan to compare targeting with the lead address, call notes, appointment location, and completed revenue. If the client requires strict qualification, reinforce location with form fields, page copy, call questions, and sales routing.
5. Add exclusions and branch ownership
Exclude places outside the approved service, license, delivery, staffing, or profitability boundary. If several campaigns or branches overlap, define which one owns each area, offer, page, phone number, budget, conversion action, and sales queue. Intentional overlap can be managed; undocumented overlap creates conflicting ads and makes client reporting unreliable.
Review Google’s location-exclusion guidance when checking exclusions. Save the before and after lists, reason, approver, date, and rollback. If the client has a sensitive boundary, use the client’s approved list rather than guessing from a map.
Do not use an exclusion to hide poor lead quality that is caused by an offer, page, form, schedule, or sales process. Fix the issue at the layer that owns it.
6. Align page, creative, hours, language, and routing
For each target, check the landing page, address, phone number, service wording, price qualifier, hours, language, and booking or contact path. A branch-targeted campaign should not send every visitor to a generic page that displays a closed office or the wrong phone number. If one page serves multiple areas, explain the coverage honestly and make the next step clear.
Align ad schedules with staffed hours when a call or immediate response is part of the promise. If forms can arrive after hours, document who owns the queue and what response time the client can actually meet. Use Google’s location and language settings to review language planning, then test the ad-to-page and page-to-routing journey.
7. QA the complete agency setup
Before launch, read the settings in this order:
- campaign, network, language, schedule, budget, and conversion owner;
- included targets, radius centers, options, exclusions, and branch ownership;
- ad wording, local page, phone, form, booking path, and service availability;
- call or form test, CRM destination, notification, sales queue, and review date.
Search the map and exact place names to catch a wrong country or duplicate city. Run a test form and call where possible. Follow the record into the CRM or client queue and confirm that the branch, source, area, and service are retained. Have the client approve the final setup before enabling traffic.
8. Review by qualified result
After launch, report impressions, clicks, spend, calls, forms, qualified leads, appointments, completed jobs, revenue, margin, cancellations, response time, and travel or delivery cost by location. Allow for the lag between a click and a sale. A target with high cost may still be valuable if it produces profitable work; a cheap form may be waste if the client cannot serve it.
If out-of-area leads appear, check the location option, inclusions, exclusions, overlap, page copy, language, schedule, and address collection before widening or pausing. Change one variable at a time and record the hypothesis, guardrail, review date, and rollback.
Common setup mistakes
- Importing a previous client map without asking whether service, staffing, or licensing changed.
- Selecting a similarly named city or radius center in the wrong country.
- Using one generic page and phone number when branch ownership is different.
- Leaving the location option out of the launch record.
- Creating many tiny campaigns that cannot support a useful decision.
- Reporting geographic clicks as qualified local demand without checking the customer address and completed outcome.
These are preventable with a signed location brief and repeatable QA checklist. The agency’s process should make a setting explainable months after launch.
Agency setup checklist
The account is ready when the client-approved map, target structure, option, exclusions, ownership, page, language, schedule, phone, form, CRM route, and review plan agree. For the decision framework, see Best Google Ads Location Targeting for Agencies. The Google Ads location targeting best practices article covers ongoing review, and adz.so can organize account evidence and workflow. It does not select a client’s territory or promise leads.