Google Ads guide

How to Set Up Google Ads Location Targeting for Online Stores

To set up Google Ads location targeting for an online store, map where each product and variant can be sold and fulfilled profitably, choose geographic targets that match shipping and storefront operations, select the location option from the buying journey, exclude unsupported areas, align catalog and checkout data, and validate orders, currency, taxes, refunds, subscriptions, and contribution by location. The setup is complete only when the advertising promise matches the actual storefront and delivery experience.

Google’s location-targeting overview and advanced location options describe current controls. Location is estimated from available signals rather than a perfect border, so compare campaign data with shipping addresses, orders, inventory, refunds, returns, currency, and customer records.

1. Create the online-store operating map

Before editing the campaign, record countries, regions, cities, radii, or other available areas where the store can sell and deliver each product, variant, collection, subscription, and fulfillment method. Include shipping zones, warehouse inventory, carrier cost, delivery time, taxes, duties, currency, payment, language, customer support, returns, subscriptions, and margin.

Prepare an include list, an exclude list, and a test list. Add reason, source, date, product group, market rule, shipping rule, fulfillment owner, and customer-service owner to each important boundary. A market may be available for one product or variant and not another.

2. Choose the campaign and geographic granularity

Use one campaign when the same products, variants, catalog, prices, currency, language, budget, shipping, subscriptions, and value model apply across the target. Separate campaigns when geography changes market settings, inventory, price, currency, taxes, shipping, payment, fulfillment, customer value, or budget ownership.

Choose country or region when those systems change at that level. Use city, radius, or smaller targets only when enough demand exists and the split changes a real store, warehouse, market, product, budget, page, or fulfillment decision. Do not create a campaign for every city simply to reproduce a map.

For a new campaign, open its location settings after selecting the objective and campaign type. For an existing campaign, open Settings and Locations. The interface may vary, so use the current campaign screen and official guidance to confirm the path.

3. Add included locations and choose the location option

Search for the intended country, region, city, or other supported target and verify the correct place and country. If the store uses a regional or radius boundary around a warehouse, showroom, pickup point, or local delivery area, compare it with product, variant, shipping, currency, tax, and checkout coverage. Similar place names can create a valid-looking but incorrect target.

For online stores, choose an option that matches whether customers must be physically in the supported shipping market or whether interest from travelers, relocators, gifting, events, or cross-border customers is valuable. Read Google’s advanced location options guidance and record why the selected option fits the buying journey. Do not assume every impression can be classified perfectly.

Use radius only for a real online-store operating reason

A radius can be useful around a store, warehouse, pickup point, showroom, or local delivery area. Set it from route economics, inventory, fulfillment, or customer data, not a round distance that merely looks tidy. Inspect edge cases and nearby areas before launch.

4. Add exclusions and check overlap

Exclude markets outside shipping or fulfillment coverage, areas where the advertised product or variant is unavailable, locations with unapproved tax or payment treatment, and regions where shipping, returns, currency, or app costs make the offer unprofitable. Use Google’s location-exclusion instructions to confirm current behavior.

Review overlap among country, region, city, radius, product, subscription, warehouse, storefront market, and promotion campaigns. If overlap is intentional, define which campaign owns budget, catalog, offer, page, market rule, and customer. If it is accidental, consolidate or narrow targets rather than making online-store reporting ambiguous.

5. Align catalog, product page, and checkout

Check product and variant IDs, prices, stock, currency, taxes, shipping, payment, promotions, subscriptions, returns, and landing pages for each target. The catalog, feed, storefront, and order data must refer to the same sellable product and market. Test cart, checkout, payment, confirmation, order value, shipping address, and support in the market.

Set languages the ads, product pages, checkout, customer service, subscription terms, and legal information can actually serve. Location targeting does not translate an online-store offer. Review Google’s location and language settings when planning multilingual coverage.

Do not add local copy that promises market-specific stock, price, taxes, payment, delivery dates, subscriptions, or returns the store cannot honor. A valid geographic target cannot repair a stale feed, mismatched variant, or unsupported market.

6. Validate the configuration before launch

Read the final settings from top to bottom:

  • included countries, regions, cities, or radius centers;
  • location option and excluded areas;
  • product, variant, catalog, price, currency, tax, shipping, and availability;
  • language, storefront market, landing page, checkout, subscription, support, and returns;
  • budget ownership, conversion value, owner, review date, and rollback.

Use the map preview and location search to catch a wrong country, duplicate city, or radius beyond the operating boundary. Save the configuration record with the source and reason for each important choice. Run a controlled test from ad or product entry to page, checkout, order, shipping address, currency, tax, refund, and return process.

7. Review location performance by profitable outcome

Compare impressions, clicks, spend, orders, conversion rate, revenue, contribution, product cost, shipping, taxes, duties, payment or app costs, refunds, returns, subscriptions, cancellations, currency, product and variant mix, new-customer share, and delivery time by location. Use order and shipping addresses to validate the campaign’s location classification. Allow for payment, delivery, refund, return, subscription, and currency lag.

If traffic comes from outside coverage, check location option, included and excluded areas, overlap, language, market rules, and actual order address. If a market has poor catalog, shipping, currency, or checkout quality, check product IDs, variants, inventory, app, demand, and page before changing the map. A short click report should not set a long-term online-store market.

Change one meaningful region, radius, option, or exclusion at a time. Record expected effect, guardrail, owner, review window, and rollback. Annotate product releases, stockouts, market changes, app changes, currency, taxes, promotions, shipping, subscriptions, and returns so geography is not blamed for an integration change.

Online-store setup checklist

The setup is ready when:

  1. Shipping zones, product and variant stock, currency, taxes, duties, payment, subscriptions, returns, customer support, and margin are mapped.
  2. Included and excluded locations match the advertised products, variants, market rules, shipping, and checkout.
  3. Location option and granularity match the buying journey and business decision.
  4. Catalog, product and variant IDs, prices, currency, taxes, shipping, checkout, subscription, and support agree.
  5. Orders, contribution, shipping, taxes, refunds, returns, subscription, currency, and customer value will be reviewed by location with normal lag.
  6. Owner, baseline, review window, guardrail, and rollback are saved.

For the broader framework, see Best Google Ads Location Targeting for Online Stores. The Google Ads location targeting best practices article covers the operating map, and adz.so can organize account evidence and workflow. It does not promise perfect geolocation or change ecommerce administration, catalog, app, shipping, tax, inventory, subscription, or returns systems.

Sources