How to Set Up Google Ads Location Targeting for Restaurants

To set up Google Ads location targeting for a restaurant, first choose the fulfilment path the campaign is meant to support: dine in, pickup, delivery, reservations, catering, or a particular branch. Write the branch, menu, hours, practical travel or delivery boundary, capacity, language, landing page, and conversion event for that path. Then configure the matching locations, check the selected location option, add explainable exclusions, and review completed orders or kept reservations rather than clicks alone.

Google’s location-targeting overview and advanced location options explain the advertising settings. They cannot determine whether a guest can reach a branch, whether an address is inside the current delivery zone, whether a kitchen can accept an order, or whether a table is available. The campaign must reflect the restaurant’s approved ordering, reservation, and customer-service process.

Write the restaurant operating brief first

Do not begin with the largest city, broadest radius, or full brand footprint. Begin with the offer that a guest is supposed to act on. A dinner reservation, hot delivery, lunch pickup, private event, and office catering lead have different geography and different proof of success.

For each campaign, record:

branch, kitchen, or fulfilment owner;
cuisine, menu, price position, and dining occasion;
dine-in, pickup, delivery, reservation, or catering path;
opening, ordering, delivery, and reservation hours;
service boundary, fees, minimum order, travel or dispatch expectation;
parking, access, pickup instructions, or branch-routing details;
table, kitchen, courier, event, or staff capacity;
page, phone, ordering link, booking link, language, and support owner.

This brief is the reason behind the location setting. It also makes later review possible: a campaign can be judged against the service it was built to support, not against an undefined idea of “local traffic.”

Keep fulfilment paths separate when the promise changes

Separate campaigns when the guest’s next step changes. A dine-in campaign should lead to the correct branch and reservation or walk-in information. A pickup campaign should explain collection timing and location. A delivery campaign should show the accepted zone, delivery hours, fees or minimums, and the right ordering path. Catering needs event area, lead time, travel terms, menu or package information, and a response expectation.

Use separate location plans when branches have different menus, hours, phone routes, parking, ordering systems, delivery zones, or budgets. If one campaign covers several branches, document how the guest is routed to the right one and how the page prevents the wrong menu or booking calendar from being shown.

Choose the service area from real guest access

Choose the location type and boundary from how the offer is fulfilled. A local dining campaign may use a practical travel area around a branch. A pickup campaign should reach people who can collect within the stated preparation and collection expectations. A delivery campaign should start from the approved delivery zone, not from the edge of the city. A catering campaign can cover farther venues only when lead time, staffing, travel, and pricing support them.

Inspect the edge of the map and test representative addresses. A radius can include a river, motorway, poor transit route, or neighbourhood that looks close but is inconvenient for a guest. A delivery boundary can include addresses where fees, minimum order, dispatch time, or courier coverage make the promise unworkable. A catering region can include venues the team cannot reach or staff reliably.

Map branches, dayparts, and seasonal limits

Record which branch owns each place, including areas where two branches overlap. Lunch, dinner, late-night, holiday, and event campaigns may have different hours and different capacity. A temporary kitchen closure, reduced menu, courier restriction, or seasonal service should be represented in the campaign record and page rather than hidden in an unexplained exclusion.

A location setting does not create a table, delivery slot, menu item, discount, dietary accommodation, or courier. Advertise only the service that the restaurant can support during the campaign’s schedule. If the target is wider for brand awareness or a future event, make the information goal clear and do not send the guest into a normal-order path that cannot serve them.

Configure locations and location options

In the campaign’s location settings, add the cities, neighbourhoods, regions, postcodes, or radius that match the operating brief. Check the selected location option rather than assuming it matches the restaurant’s question. A branch visit, delivery order, and catering enquiry can require different tests.

Google describes the controls in its advanced location options. The restaurant should compare the campaign’s location reporting with the order, reservation, and lead records it is permitted to review. Platform location does not prove that a guest can travel to the branch or that a delivery was fulfilled successfully.

Save a setup record containing:

The target type and exact places selected.
The radius centre, branch mapping, or service-area boundary.
The location option and the access question it is intended to answer.
Exclusions and the operational reason for each.
The page, menu, phone path, ordering or booking link, owner, and review date.

Add exclusions for areas outside the dining, pickup, delivery, catering, branch, language, or capacity boundary. Check for locations assigned to another branch when overlapping campaigns could expose the wrong menu, phone number, ordering platform, or reservation calendar. Review Google’s location-exclusion guidance when checking the current platform behavior.

Give every exclusion an owner and a review date

Write “outside delivery route,” “no pickup access,” “branch B owns this area,” “catering travel unsupported,” “temporary kitchen capacity,” or another concrete reason. “Bad traffic” does not explain the operating constraint. When a temporary exclusion is no longer needed, reassess it rather than letting an old workaround define the market indefinitely.

Review overlap among branch campaigns, delivery campaigns, reservation campaigns, catering campaigns, neighbourhood targets, and brand searches. Overlap can be intentional when pages, fulfilment paths, budgets, and conversion definitions differ. It is a problem when guests receive contradictory location, menu, price, hours, or booking promises.

Align the ad, page, menu, and ordering path

Open the landing page and complete the guest journey before launch. The ad, page, menu, hours, prices or minimums, fees, delivery boundary, pickup instructions, reservation path, phone greeting, confirmation, and customer support should make one consistent promise. A location setting cannot repair a page that sends a delivery guest to the wrong branch or a reservation search to an unavailable booking calendar.

For dine-in campaigns, verify the branch address, map, opening hours, parking or access details, menu, reservation instructions, and walk-in information. For pickup, verify collection location, preparation expectations, parking, order timing, and the ordering link. For delivery, show the accepted zone, delivery hours, fees or minimums, menu, timing language, and support path. For catering, show event area, lead time, packages or menu information, travel terms, enquiry fields, and response expectations.

Do not imply that a table, delivery slot, menu item, discount, dietary accommodation, or branch service is guaranteed. If holiday hours, a seasonal menu, a temporary kitchen restriction, or a delivery-partner change affects the offer, update the campaign record and destination together.

Keep language and occasion claims real

Google’s location and language settings describe platform controls. A language setting does not create a translated menu, booking flow, dietary explanation, customer-support route, or ordering experience. Use languages the restaurant can support across the ad, page, menu, phone, ordering, and follow-up.

Location targeting also does not reveal whether a guest is planning a family meal, an office lunch, a celebration, or late-night pickup. Make the occasion clear in the campaign and page, then assess whether orders or reservations match the menu, service, table, and kitchen capacity.

Define conversion events for the restaurant workflow

Set conversion definitions before launch. Google’s conversion tracking documentation describes the platform concept; the restaurant must decide which events show progress and which later outcomes it can verify.

Keep the stages separate:

ad interaction or call;
menu or ordering-page visit;
order start, reservation request, or catering enquiry;
completed order, confirmed reservation, or qualified catering lead;
retained order, kept table, or booked event;
cancellation, refund, no-show, failed delivery, or other operational outcome.

A click is not a menu view. A menu view is not an order. An order start is not a completed order, and a completed order is not necessarily a profitable order after delivery and promotion costs. A reservation request is not a kept table. Give each stage an owner, timestamp, and definition that staff can apply consistently.

Capture enough location context to review fit

Where the restaurant’s privacy and data policies allow, connect the campaign, target, branch, fulfilment path, reported location, date, and stage to the order, reservation, or catering record. Do not collect unnecessary guest details for advertising analysis. If the source or location is uncertain, preserve that uncertainty instead of inventing an exact explanation.

For delivery, measure completed and retained orders, cancellations, refunds, dispatch time, fees, minimum order, and contribution after fulfilment costs. For dine-in, measure booking starts, kept reservations, covers, no-shows, table capacity, and the intended occasion. For catering, measure qualified enquiries, event area, lead time, expected value, travel, staffing, and booked events.

Launch and review the location setup

Before enabling the campaign, inspect the target map, the location option, exclusions, branch route, destination page, ordering or booking path, phone route, schedule, and conversion events. Test representative addresses for dine-in, pickup, delivery, and catering. Confirm that staff know how to route an out-of-area, wrong-branch, unsupported-service, or capacity-limited request.

After launch, compare the intended location with available campaign reporting and approved fulfilment records. Review opening hours, holidays, menu changes, staffing, weather, local events, delivery partners, reservation inventory, and branch changes alongside performance. A temporary closure can make a good market look weak; a local event can make one day’s orders look like a durable geographic advantage.

Use a written hypothesis for changes

Write the first test in operational terms, such as: “A delivery boundary limited to the kitchen’s reliable dispatch area will reduce failed orders while preserving contribution,” or “Separating catering from dinner delivery will improve qualified event leads without diverting the reservation budget.” Record the current target, option, page, fulfilment path, budget, baseline, owner, review date, decision rule, and rollback action.

Change one boundary, option, exclusion, branch route, page, or fulfilment rule at a time where possible. If several changes are necessary, document them as one combined workflow change. Judge the result by completed orders, retained contribution, kept reservations, qualified catering leads, response time, and guest-service evidence—not clicks alone.

If traffic arrives outside the intended area, inspect target type, location option, exclusions, search intent, branch mapping, ad language, and page before changing the radius. If traffic is inside the target but orders are weak, inspect menu, price, fees, page, ordering path, delivery promise, and capacity. If orders are strong but contribution is weak, review radius, minimum order, delivery cost, offers, and branch allocation.

Avoid common setup mistakes

Watch for these failure modes:

using one brand-wide radius for branches with different menus, hours, or delivery zones;
targeting a city before checking the real delivery boundary or practical travel route;
leaving the location option undocumented;
excluding a place without a concrete operating reason, owner, or review date;
sending dine-in, pickup, delivery, reservation, and catering traffic to one generic page;
counting every call, form, or order start as a completed or profitable outcome;
changing the boundary, page, menu, budget, staffing, and conversion definition at the same time;
leaving expired offers, holiday hours, temporary closures, or wrong-branch links live;
promising a table, delivery time, menu item, discount, or dietary accommodation the restaurant cannot reliably provide.

Resolve the underlying access or fulfilment problem and save the reason for the change. Adding more locations rarely fixes a mismatched menu, broken ordering route, unavailable tables, or unprofitable delivery zone.

Restaurant location-targeting setup checklist

Before launch or a material change, confirm:

The campaign’s branch or fulfilment path, cuisine or occasion, hours, owner, and capacity are documented.
The target boundary reflects real travel, pickup, delivery, catering, branch, and seasonal conditions.
The location option, target list, radius centre or branch map, and exclusions are recorded.
Every exclusion has an operating reason, owner, and review date.
The ad, landing page, menu, prices or minimums, fees, hours, ordering link, booking link, and support path agree.
Language, dietary, parking, access, and delivery information matches the service the restaurant can provide.
Clicks, calls, order starts, completed orders, retained orders, reservations, kept tables, catering leads, cancellations, refunds, and no-shows have separate definitions.
The first geographic hypothesis, baseline, review date, decision rule, and rollback action are saved.

The best Google Ads location targeting for restaurants article covers the broader decision framework. adz.so can organize supported advertising evidence and workflow, but it does not provide restaurant operations, verify delivery zones, reserve tables, guarantee orders, or guarantee profitability.