Google Ads guide

Google Ads Location Targeting Checklist

Use this Google Ads location targeting checklist before launch and after a change to the service area, radius, reach option, exclusions, language, budget, or landing page. Confirm that the target reflects where the business can actually serve customers, then verify geographic quality with qualified leads, orders, appointments, or another business outcome—not clicks alone.

Pair it with Google Ads location targeting best practices, how to set up location targeting, and Google’s location-targeting overview.

1. Business map checklist

Write down:

  • where the business can sell, ship, deliver, visit, or support customers;
  • delivery, travel, licensing, inventory, sales, or branch constraints;
  • locations that are unavailable or owned by another team;
  • the geography owner and the date the map was confirmed;
  • the outcome that makes a location commercially useful.

Do not select locations from population or search volume alone. A target is good when it represents serviceable demand and can be measured against the business’s operating reality.

2. Included-location checklist

Confirm that:

  1. The country, region, city, postal area, or radius matches the service map.
  2. Similar location names were checked before saving.
  3. The geographic unit is large enough to learn but not wider than needed.
  4. The map edge was reviewed for nearby areas the business can or cannot serve.
  5. Separate regions have a documented reason for separate campaigns or budgets.
  6. The selected locations belong to the intended campaign.

Use Google’s location-targeting setup instructions to confirm the current available choices. A location label alone is not proof that the target matches the intended map.

3. Reach-option checklist

Decide whether the campaign needs people likely to be present in the area, people who regularly visit it, people showing interest in it, or a combination the business can support.

Check:

  • whether customers buy before traveling or only while physically present;
  • whether the offer requires a visit, delivery, appointment, or local license;
  • whether travel, event, education, or relocation interest is valuable;
  • whether the team can qualify and serve interest-based leads;
  • how the reach choice will be checked in reporting.

Read Google’s advanced location options guidance and remember that location signals are approximate. Do not treat any option as a perfect geofence.

4. Radius and boundary checklist

If using a radius, confirm that it is centered on a real store, branch, warehouse, or service hub and that the size reflects travel time, delivery cost, capacity, or historical customer data. Check roads, rivers, boundaries, and nearby places that make straight-line distance misleading.

If using administrative areas, check whether the named city, region, or postal unit is larger or smaller than the operating area. Keep an exception list short and meaningful. If the entire boundary is wrong, revise the target rather than adding dozens of local exclusions.

5. Exclusion and overlap checklist

Before launch, verify:

  • unavailable or unprofitable areas are excluded;
  • another branch or sales team’s territory is handled intentionally;
  • parent-region and city or radius campaigns do not overlap accidentally;
  • each overlapping campaign has a distinct offer, budget, message, or reason;
  • the exclusion was saved in the intended campaign;
  • the map has an owner who will update it when operations change.

Use Google’s location-exclusion instructions when the current interface or behavior is unclear. Exclusions are guardrails, not a substitute for a current service map.

6. Language, ad, and page checklist

Check that the campaign’s language, ad copy, landing page, support process, currency, pricing, opening hours, phone number, and legal information can serve the selected locations. Split campaigns or pages when geography changes the offer or customer path. Keep them together when the full experience is shared.

Test every final URL on mobile and desktop. Confirm that the page explains availability, loads correctly, and makes the next action clear. Do not create a thin local page that changes only a city name; provide useful service-area information and a credible next step.

7. Launch baseline checklist

Save before enabling:

  1. Included and excluded locations.
  2. Radius or geographic unit.
  3. Reach option and language.
  4. Campaign, ad, budget, and schedule structure.
  5. Landing-page and conversion-action versions.
  6. Expected service area and quality definition.
  7. Owner, launch date, review date, and stop condition.

The baseline lets the team tell a location edit apart from a budget, promotion, page, or sales-process change.

8. Geographic quality checklist

At the first comparable review, inspect:

  • impressions, clicks, spend, and conversions by location where available;
  • actual customer or lead locations;
  • presence-versus-interest detail when available;
  • qualified leads, booked jobs, orders, revenue, or margin;
  • device, language, schedule, query, and placement mix;
  • page loads, form completion, and sales acceptance;
  • geographic capacity and fulfillment after additional demand.

Do not pass because a target produced more clicks. Ask whether the business can serve the people reached and whether the outcome is worth the cost.

9. Change-control checklist

For every map, reach-option, exclusion, budget, page, or language change, record:

  • old setting and new setting;
  • business reason and hypothesis;
  • affected campaigns and locations;
  • expected reach and quality effect;
  • owner, date, safety boundary, and review date.

Change one material input when possible. If a policy, fulfillment, or spend risk requires an immediate change, make it and annotate why the comparison is not clean. Allow for conversion lag before making a permanent geographic decision.

For diagnosis, see how to fix Google Ads location targeting problems. For deeper optimization, use how to optimize Google Ads location targeting. The adz.so product overview is a truthful next step for supported workflows; it does not certify a map or guarantee geographic performance.