How to Set Up Google Ads Location Targeting for Home Services

To set up Google Ads location targeting for a home-services company, map each service to its real dispatch area, travel time, crew, equipment, response promise, and capacity before adding a city, service area, or radius. Choose a location option deliberately, exclude places the team cannot serve, align ads and booking paths with the job promise, and measure qualified calls, booked work, completed jobs, and travel-adjusted value.

Google’s location-targeting overview and advanced location options explain the platform controls. They do not know whether a technician can reach an address, whether a permit or vehicle is available, or whether the job is profitable after travel. The campaign map should be built from dispatch reality.

1. Build the service and dispatch map

List the service the campaign will promote: emergency repair, scheduled maintenance, replacement, installation, inspection, cleaning, landscaping, or another specific job. Record the crew or technician, equipment, service hours, emergency response, expected travel time, minimum job value, callback process, and locations the business can support.

Separate services when their operating promises differ. A same-day repair may need a tighter radius than a planned installation. A roofing inspection may use a different crew and booking path from an HVAC tune-up. A broad home-services brand area should not automatically become the target for every service and every response window.

Create three lists: places the company serves now, places for a deliberate test, and places to exclude. Add a reason, owner, service, travel assumption, and review date to each boundary. Note traffic corridors, tolls, seasonal conditions, referral partners, permit limits, and locations where a vehicle or specialist is not available.

2. Choose the campaign structure before locations

Keep locations in one campaign when the same service, page, phone route, dispatch team, hours, budget, and booked-job definition apply. Separate campaigns when geography changes the crew, emergency promise, travel fee, job type, minimum value, or budget owner. The split should help dispatch or management make a real decision.

Separate urgency and job journeys when needed

An emergency caller, a homeowner planning a replacement, and a property manager requesting recurring maintenance need different responses. They may need different pages, call scripts, qualification fields, schedules, and conversion events. If the team cannot answer an urgent call in a market, do not use a broad local target that implies same-day availability.

Name each campaign with service, area, and response model. Record location target, option, exclusions, landing page, phone path, dispatch owner, service hours, travel assumption, and review date. Clear records prevent an operator from treating an old radius as a current promise.

3. Add the city, service area, or radius

Open the campaign location settings and search for the supported country, city, county, state, province, or region that matches the service map. Verify the target name and map before saving. If using a radius, confirm the center is the real dispatch point or chosen service hub, then inspect the edge for addresses the crew cannot reach within the stated response window.

Choose the geographic unit that makes the service decision understandable. A local repair company may start with a practical office radius. An installation team with route density may serve a wider region. A specialist crew may test another area with a separate page, call path, and schedule. A smaller radius is not a goal by itself; it is useful when it improves fulfilment, qualification, or measurement.

Save the target, service, reason, owner, travel assumption, and review date. Check adjacent towns and boundary roads rather than trusting a postal label. Dispatch should be able to explain why an address is included or excluded when the first call arrives.

4. Select the location option for the reach question

Choose the location option that matches who the business wants to reach. A local service campaign may begin with people present in the markets where crews operate. A separate test for people researching a service from elsewhere needs its own page, response expectation, and review rule. Read Google’s advanced location options and compare the platform report with the customer’s actual job address.

The setting is not proof that the caller is in coverage. When inquiries appear outside the dispatch map, check the target, option, exclusions, search intent, and address captured by the call handler. Do not widen the service area just because the campaign reports impressions from a place the team cannot reach.

5. Add exclusions and check campaign overlap

Exclude markets outside the crew’s workable area, places requiring unavailable equipment or permits, locations where the advertised response cannot be met, and routes assigned to another branch or referral partner. Review Google’s location-exclusion guidance when checking current behavior. Record each exclusion with service, reason, owner, and review date.

Inspect overlap among office radii, city targets, regional campaigns, emergency campaigns, and installation campaigns. Overlap can be intentional when the pages, phones, teams, and booked-job definitions differ. It needs correction when one caller enters multiple queues and dispatch cannot tell which service promise or budget received the call.

6. Align the customer promise with booking

Review the ad, landing page, service menu, availability, emergency wording, price or travel-fee language, phone greeting, form, booking calendar, confirmation message, and technician follow-up. They should agree with the target and the crew’s real capacity. A page should not promise same-day service in a market that the schedule only reaches next week.

Ask for address or service area, job type, urgency, property type, access constraints, and contact details when the team can use them. Explain the first-response expectation and how customers should share photos or equipment information through the company’s intended process. Avoid asking for information that cannot be protected or routed appropriately.

Language settings should match the actual call and field-service experience. A campaign setting does not supply a bilingual dispatcher or technician. Google’s location and language settings explain the advertising controls; the company remains responsible for a clear service and booking path.

7. Validate calls, bookings, and dispatch tracking

Review the setup as one system:

included locations, exclusions, target type, radius center, and location option;
service, job type, page, phone number, form, calendar, hours, and availability wording;
qualified-call, booked-job, cancellation, completed-job, revenue, and margin definitions;
dispatch owner, response window, travel assumption, baseline, review date, and rollback action; and
report fields for actual job address, crew, service, travel time, job stage, and outcome.

Run a controlled page-to-call or page-to-form test. Confirm that the event is recorded once, reaches the intended dispatcher, and contains the information needed to decide whether the job is in coverage. Check an address that should be included, one that should be excluded, the radius edge, a neighboring market, and a request for an unsupported service.

Do not change geography, offer, page, phone process, schedule, budget, and conversion definitions together unless the combined operational change is the experiment. Annotate weather, outages, seasonal demand, staffing changes, vehicle downtime, service launches, office moves, and tracking changes.

8. Review geography through completed work

Track spend, calls, forms, qualified calls, booked jobs, cancellations, dispatch time, travel time, job type, technician, completed work, revenue, gross margin, repeat work, and cost. Keep stages separate: a click is not a call, a call is not a booked job, and a booked job is not completed work.

High call volume may be a failure when callers are outside coverage, jobs are too small for the drive, or dispatch cannot meet the promise. A smaller target can be stronger when customers book the right service, accept the schedule, complete the work, and produce healthy value. Compare location with crew availability, route density, seasonality, and rework.

If calls are outside coverage, inspect target, option, exclusions, query intent, and actual address. If calls are in coverage but the wrong service, inspect the page and ad. If bookings cancel, review schedule, price expectations, travel fees, and confirmation. If completed jobs have weak margin, assess drive time, job mix, materials, rework, and the promise made before changing the map.

Home-services location-targeting setup checklist

Before launch, confirm:

Each service has a documented area, job type, crew, equipment, travel assumption, response window, and owner.
Emergency, scheduled, installation, inspection, and repair journeys are separated when their promises differ.
Location targets, radius edges, exclusions, and location option match the dispatch map.
Ads, pages, calls, forms, booking paths, and technician follow-up make the same availability promise.
Qualified calls, booked jobs, cancellations, completed work, travel time, margin, and repeat value are defined.
The test hypothesis, baseline, owner, review date, capacity assumption, and rollback action are saved.

For the strategic framework, see Best Google Ads Location Targeting for Home Services. The Google Ads location targeting best practices article covers controlled tests. adz.so can organize supported advertising evidence and workflow, but it does not dispatch technicians, verify licenses or insurance, quote a job, guarantee availability, or guarantee booked or profitable work.