How to Set Up Google Ads Location Targeting
To set up Google Ads location targeting, document where the business can actually sell or serve customers, choose the geographic units and reach option that match that map, add exclusions, align language and landing pages, then test the campaign before launch. The setting should represent an operating decision—not simply a list of cities with high search volume.
Use this sequence with Google Ads location targeting best practices, best location targeting settings, and Google’s location-targeting setup instructions.
1. Document the service area before opening the settings
Write the operating boundary in the language of the business: delivery zones, store catchments, technician travel time, branch territories, licensing, inventory, shipping cost, or sales coverage. Decide whether the campaign can serve a country, region, city, postal area, or radius. Note locations that are unavailable, separately owned, or unprofitable.
This step prevents a common setup error: choosing a large place because it has search demand even though the business cannot fulfill the request. It also prevents a target that is so narrow that the campaign cannot learn. Keep the map and its owner in the launch record. If the business changes coverage, the location setup should be reviewed rather than copied forward.
2. Open the campaign’s location settings
In Google Ads, open the campaign you intend to configure and find its location settings. The exact labels and available controls can vary by campaign type, account state, and product changes, so use the current interface and Google’s location-targeting setup instructions rather than an old screenshot.
Before saving, confirm that you are editing the intended campaign and not a shared or overlapping campaign. Record the current locations, exclusions, reach option, language, budget, and date. If another campaign owns a region, understand whether the overlap is intentional. Location setup is safer when the current state can be restored or compared.
3. Add the geographic units that match the map
Search for and select the country, region, city, postal area, or other available unit that reflects the service boundary. Review the map preview and the included area. Use the smallest practical unit that supports a business decision, not necessarily the smallest unit the interface allows.
For national ecommerce, a country or group of regions may be suitable when shipping and margin are consistent. For a local service, cities, postal areas, or a radius around a branch may better represent fulfillment. For a sales team, regions may need to follow ownership and capacity. If economics differ sharply, separate the campaigns or structures so one budget does not hide the difference.
Check for similarly named places and nearby areas. A saved location label is not enough; verify that the selected geography is the one the business means. Use Google’s location targeting overview as a platform reference for available geographic controls.
4. Choose the reach option for the customer journey
Decide whether the campaign should reach people likely to be in the area or also people who have shown interest in it. Interest-based reach may help a travel, event, education, relocation, or destination business. A presence requirement may be more appropriate for a repair visit, local delivery, appointment, or service that cannot be fulfilled remotely.
Do not select the broader option simply to increase impressions. Do not select the narrower option when people commonly research and purchase before entering the location. Define what makes a click serviceable and match the option to that definition.
Google’s advanced location options guidance and out-of-area traffic troubleshooting guide explain the platform’s current controls and limitations. Location signals are not a perfect geofence, so plan to validate the result with real lead, order, or customer location data.
5. Add exclusions and check campaign overlap
Exclude places the business cannot serve, cannot ship to, cannot license, or does not want to own. Examples include a town beyond a delivery boundary, a territory assigned to another branch, or a region where a product is not available. Use exclusions as a maintained business rule rather than as a replacement for understanding the map.
Review campaigns that target a parent region and a more specific city or radius. Overlap can be intentional when the campaigns have distinct offers, budgets, or priorities. If it is accidental, decide which campaign owns the traffic and consolidate or adjust the structure. Document the decision before launch.
Use the Google Ads location-exclusion guide to verify the current behavior. After launch, inspect actual locations because no exclusion list eliminates every classification or operational change.
6. Configure language and campaign structure
Choose languages the ad, landing page, support team, checkout, and legal information can serve. Location does not automatically determine language. For multilingual markets, separate campaigns or ads when copy, phone numbers, currency, inventory, or customer support differs materially.
Keep locations together when the same offer, page, budget logic, and quality definition apply. Split them when geography changes value, fulfillment, inventory, sales capacity, or the message. Avoid producing dozens of local campaigns that cannot collect enough data for a decision.
Read Google’s location and language settings guide for the relationship between these controls. Then test the full customer experience: ad, page, form or checkout, support, and fulfillment.
7. Align ads and landing pages with each area
Review the ad promise for every geographic group. A local ad should not imply coverage outside the service map. A regional offer should make availability, delivery, pricing, or appointment information clear. If a location has a different phone number, store address, opening time, or promotion, put that difference in the appropriate campaign or page.
Test final URLs on mobile and desktop. Confirm that the page loads, the location is understandable, the next action works, and the form or checkout does not collect requests the business cannot fulfill. Location targeting can send the right person to the wrong page if the creative and page are generic.
Do not create a near-empty page that only swaps a city name. A useful local page explains the service, availability, proof, and next step for that area.
8. Record a launch baseline
Before enabling the campaign, save:
- included locations and exclusions;
- reach option and language settings;
- campaign and ad-group structure;
- budget, bid strategy, and schedule;
- ads, landing-page versions, and conversion actions;
- the expected service area and quality outcome;
- owner, launch date, and review date.
This baseline matters when a later location edit coincides with a new promotion, page, budget, or sales process. Without it, a report may attribute the change to geography alone.
9. Verify the setup after launch
During the first review, compare impressions, clicks, spend, and conversions by location where the report supports it. Look at the actual location mix and whether leads, orders, or appointments are serviceable. Check interest-based traffic separately when available. Review search terms or placements, language, device, schedule, and page behavior for clues about quality.
If delivery is too low, check whether the geography is too narrow, demand is limited, the budget is constrained, or eligibility is failing. If traffic is outside the service area, check the reach option, exclusions, overlap, and customer-location data before expanding the exclusion list. If one region performs well, confirm operational capacity before adding budget.
Change one material input when possible and annotate it. For ongoing review, use Google Ads location targeting best practices and best Google Ads location targeting settings. The adz.so product overview is a truthful next step for supported workflows; it does not guarantee location accuracy or perform the setup for you.