Google Ads Audit Checklist for Restaurants

Use this Google Ads audit checklist for a restaurant in order: define channel and location scope, classify dining intent, verify menu and offer freshness, test reservations and orders, reconcile paid outcomes, and compare contribution with kitchen, table, delivery, and catering capacity. Keep customer and payment data in approved systems.

This is an educational checklist, not food-safety, allergen, legal, pricing, financial, or automated adz.so advice. Consult Google Ads Help and local owners.

1. Define scope and stages

[ ] Record dates, locations, hours, menus, ordering and reservation platforms, phones, pages, kitchens, tables, delivery areas, campaigns, budgets, and conversions.
[ ] State whether the question concerns dine-in, reservations, takeout, delivery, catering, events, cuisine, location, or group performance.
[ ] Separate click, menu view, call, reservation, confirmed reservation, order, pickup, delivery, catering inquiry, completion, payment, cancellation, refund, repeat, and contribution.
[ ] Separate suppliers, jobs, support, wrong numbers, and duplicates.
[ ] Record currency, time zone, attribution window, consent assumptions, daypart, menu, staffing, platform, and capacity changes.

2. Check local and dining intent

[ ] Map campaigns to location, cuisine, occasion, channel, page, menu, phone route, reservation or ordering platform, and owner.
[ ] Review location targeting, exclusions, presence assumptions, radius or city settings, location assets, hours, and delivery areas.
[ ] Classify restaurant, cuisine, menu, reservation, date-night, family, lunch, takeout, delivery, catering, event, price, hours, dietary or allergen, job, supplier, competitor, and irrelevant intent.
[ ] Confirm location, hours, menu, channel, delivery area, and capacity match the promise.

3. Validate menus, offers, and claims

[ ] Follow searches through ad, location or menu page, phone, reservation, order, and confirmation.
[ ] Check address, hours, menu freshness, prices, availability, photos, reservation rules, pickup or delivery, fees, catering minimums, event terms, and expiration.
[ ] Flag unavailable dishes, stale prices, unsupported dietary or allergen claims, guaranteed delivery times, hidden fees, misleading discounts, and wrong-platform pages.
[ ] Confirm offers and prices are current.

4. Test calls, reservations, and orders

[ ] Use an approved test identity; do not submit real payment or personal data to an uncontrolled system.
[ ] Test mobile and desktop journeys during lunch, dinner, closing, weekend, and holiday conditions.
[ ] Check number ownership, host or manager routing, response, voicemail, missed-call handling, reservation availability, waitlist, order menu, modifiers, payment, coupon, tax, delivery area, platform handoff, confirmation, and cancellation.
[ ] Distinguish menu view, call, reservation request, confirmed reservation, order, pickup, delivery, catering, completion, payment, refund, and repeat.

5. Reconcile reservations and orders

[ ] Compare ad events with calls, menu views, reservations, seated guests, orders, pickups, deliveries, catering, payments, cancellations, refunds, no-shows, and repeats.
[ ] Break down by location, channel, cuisine, campaign, query, page, device, daypart, platform, and cohort.
[ ] Check source IDs, reservation and order definitions, deduplication, third-party imports, service fees, cancellation timing, delivery attribution, and revenue lag.
[ ] Mark recent reservations and orders immature.
[ ] Do not send offline values into bidding before the join is proven.

6. Review contribution and capacity

[ ] Record spend, reservations, orders, collected revenue, platform fees, delivery, food, packaging, labor, discounts, refunds, comps, chargebacks, no-shows, catering labor, and kitchen or table capacity.
[ ] Keep menu price, gross order, net payment, and contribution separate.
[ ] Compare demand with seating, kitchen, pickup, delivery, catering, and front-of-house capacity.
[ ] Mark missing fees, costs, cancellation, repeat, and cohort evidence unknown.

7. Check privacy, food claims, and offers

[ ] Review forms, calls, analytics, customer lists, remarketing, reservation and ordering imports, payment handoffs, access, retention, and consent.
[ ] Keep payment, contact, and customer data in approved systems.
[ ] Review menu, allergen, ingredient, dietary, price, discount, delivery, catering, event, and testimonial claims with responsible owners.
[ ] Escalate food-safety, allergen, consumer, legal, tax, and privacy questions.

8. Close findings and retest

For every failure, capture location, channel, daypart, campaign, query or page, device, evidence, impact, owner, priority, action, proof condition, retest result, and limitation. Prioritize broken ordering or reservation paths, wrong-location routing, stale menus, unsupported claims, hidden fees, missing consent, and order-stage gaps.

After each repair, repeat the same journey and compare comparable cohorts. Annotate menu, staffing, seasonality, platform, price, and capacity changes.

Restaurant handoff

End with what is proven, what must be corrected, what requires food or consumer review, what should be tested, and what remains unknown. For context, see how to audit Google Ads for restaurants, free Google Ads audit for restaurants, and best Google Ads audit tools.