Restaurant SEO playbook for searches without website clicks
Check what guests see on Google and your website in about an hour. Use a local SEO checklist and a three-month plan that keeps profile actions, website sessions, and orders separate.

Loading audio…
—:—
A guest looking for somewhere to have dinner sees a map, hours, photos, and reviews on Google. They open the menu, call, get directions, or order delivery straight from the restaurant’s profile. If none of that takes them to your site, your website analytics will not record a visit.
This happened before AI Overviews, too. Google now answers more questions on the results page. Website traffic never counted every guest who found a restaurant through search, so it cannot show the full picture of search performance. For restaurant SEO, start by checking whether Google has the right information and whether a guest can call, get directions, and order from there.
Allow about an hour for the first review of one location. The repair and measurement plan below covers three months.
Where a restaurant appears in search
A Google results page can feature a restaurant in three places:
- A map with nearby businesses, known as the local pack. It often appears at the top for searches such as “ramen near me.” Selecting a restaurant there or in Google Maps opens its Google Business Profile, with hours, a phone number, photos, reviews, a menu, and buttons for calls, directions, and orders.
- A regular website result. Your site has information or actions the profile may lack: a full menu with prices, online ordering, and a page for each location.
- An AI Overview above the results. It does not appear for every search. It draws on several sources and may link to your site or to other sites.
ChatGPT and Gemini operate separately from Google Search. A guest asks a question in a conversation, and each assistant chooses whether to provide sources and which ones to use.
What Google shows depends on the search. A Whitespark study in May 2025 tested 540 searches across three US cities and six industries. Searches with local intent almost always returned a map and rarely an AI Overview. For informational searches, AI Overviews were much more common than maps. For local searches such as “where to eat near me,” review the profile first.
Pew Research Center found that about one in five Google searches by US adults in spring 2025 included an AI Overview. Questions and longer searches were more likely to have one, but not every such search did (Pew study). To find out whether a specific search produces an overview, try it: “dim sum for a party of 12 on Sunday” or “gluten-free pizza near the stadium,” for example.
Google has no additional technical requirements for AI Overviews or AI Mode. A page must be indexed and eligible to appear with a snippet in ordinary search results. Meeting those conditions does not guarantee inclusion in an AI answer (Google Search Central).
Pew also examined the browsing of 900 US adults in 2025. People clicked a regular result on 8% of visits to pages with an AI Overview, compared with 15% on pages without one. Links within the overview received clicks on 1% of visits. The researchers reconstructed results by repeating the searches a few weeks after the visits, and the searches covered unrestricted topics. This is an observed difference, not evidence that overviews caused it, and it cannot be applied to restaurant searches.
Fewer search sessions alone do not tell you how many guests Google brought in. Only a handful of facts have to match everywhere: name, address, hours, phone, menu, prices, and where to order. Compare them across your profile, website, POS, and delivery apps. Resolve conflicting copies, then reduce the number of places where someone must enter the same information by hand.
A quick review of one location
The hour-long review checks what a guest sees and records what needs fixing. Markup, indexing, and a review of an entire chain require separate technical work.
Sign out of Google and use a phone to run three searches: the restaurant’s name; its category and area, such as “ramen near me” or “tacos in Midtown”; and a condition that matters to guests, such as “kid-friendly restaurants” or “vegan brunch with outdoor seating.” Record which result comes first (the map, an AI Overview, or regular links) and whether your restaurant appears. Note the overview’s sources and check the hours, phone number, and menu.
Search from somewhere your guests might search. If many come from another neighborhood, repeat the check there. Google ranks local results mainly by relevance, distance from the guest, and the business’s prominence (Business Profile Help). Treat the result as a snapshot: another location or another day may produce a different result.
Profile checks
| Check | Expected result |
|---|---|
| Verification | The profile is verified and uses the name on your sign |
| Primary category | It matches what you serve, such as “Pizza restaurant” |
| Hours | They match the sign on the door, including special hours for the next holiday |
| Phone | Calls reach someone who answers during opening hours |
| Menu | The link opens a page with dishes and prices; uploaded menu photos or PDFs are current |
| Order links | There is a link to your own ordering page |
| Attributes | Service options, accessibility, parking, and payments are filled in where available for your category and country |
| Photos | Recent photos show dishes, the dining room, and the entrance |
| Reviews | Recent reviews have replies |
A guest can order straight from the profile without opening your site, so open every link in the ordering block and record where it goes: Google and delivery services add some links themselves. Schedule repairs for days 15 to 30, using Google’s instructions to manage online ordering:
- Add your own ordering page if its link is missing.
- Mark your preferred option. For a service that supports both pickup and delivery, Google lets you choose separately for each.
- Request removal of unwanted third-party links. The provider must remove a link within five business days.
- Do not disable ordering in the profile to remove delivery apps: that removes your own link as well.
With several locations, checking each profile in Google by hand takes a long time. When your locations are linked to Google locations in Eatery Club™, the panel shows for each one whether its Google location is verified, whether menu upload is enabled, its result, and the current order links, including delivery apps. Check the preferred status of your own link in Google itself. The image below is an Eatery Club Control Center design mockup with sample US data, not the live panel; tab and status names may differ.

Next, open the website on a phone without signing in or using a saved delivery address. Check the following:
- The menu and prices are visible before a guest enters a delivery address.
- Each location has a separate page with its name, address, phone number, and hours written as text.
- The page title and main heading, H1, identify the restaurant and the specific location.
- On a multilingual site, such as one in English and Spanish, each language has its own URL. The menu and page text match that version’s language.
An Eatery Club ordering site draws each location page’s information from its restaurant card in the admin panel (restaurant settings). Fix the name, address, hours, or phone number in the card, then check the published page. With “Show the product catalogue?” enabled (“Відображати каталог продуктів?” in the card’s Ukrainian interface), the site displays the POS menu with prices. With it disabled, guests see the PDF menu. Use the brand and street in location names so guests can distinguish them.
Enter the same search with conditions into ChatGPT and Gemini. Record whether each names the restaurant, gets the facts right, and provides sources.
Prioritize incorrect hours, phone numbers, addresses, incorrect “closed” statuses, and outdated menus. These errors can prevent a guest from reaching the restaurant, contacting it, or choosing a dish; a high search ranking does not fix them. Next, add missing actions: a menu link or a way to order from the landing page. Everything else can wait until next month.
Technical checks
This stage needs Search Console, panel access, and time for each location. It is outside the hour-long review.
- Use URL Inspection in Search Console to check whether the location page is indexed and which canonical URL Google selected. A page outside the index will not appear in regular results or as a link in an AI Overview.
- Test the structured data: JSON-LD code describing the restaurant to search engines. Schema Markup Validator checks all schema.org types; Rich Results Test identifies potential Google rich results (testing tools). Neither tool compares the code with the visible page, so check the name, address, phone number, and hours yourself. Before adding code to “JSON-LD Data” under “Website Settings,” inspect the published page’s existing markup. Conflicting descriptions of the same restaurant can confuse search engines.
- Check every language version. Each has its own URL, such as
/en/for English. The site gets translated names and addresses from the card’s “Translations” (“Переклади”) block. The versions reference each other for search engines, but you still need to check that each is indexed. - Check static page titles and headings in “Custom Page Titles” and “Custom Headings” (ordering website settings).
- If Google menu upload is enabled, review each location’s result in the panel, then inspect its profile a few days after changes.
- For a chain, select locations for manual review using the plan below. You do not need to check every location every month.
Local SEO checklist for one location and for a chain
Every location
- Keep one verified profile and name one person responsible for its category, hours, and phone number.
- Enter holiday hours at least a week before each holiday.
- Point the menu link to that location’s menu on your own site. If you also upload menu photos or PDFs to Google, replace them when prices change. Updates can take 24–48 hours to appear on Google Maps and Search (menu editor).
- Point your own order link to that location’s ordering page.
- Check the result of each upload part. For an Eatery Club restaurant linked to a Google location, menu upload sends Google several independent parts: the structured POS menu, if the Google location supports it; the menu link; the order link; and dish photos. Photos are sent in a separate pass after the menu. Each part has its own result, and a delivery app may already occupy the order-link slot. A successful status confirms that data was sent, not that it is visible: profile updates can take 24–48 hours. When the menu arrives through the API, Google’s menu editor may be unavailable. Change prices in the POS and check the next upload.
- Publish the location’s name, address, phone number, and hours as text on its own page.
- Keep hours consistent across Google, the site, and all delivery apps. The Eatery Club site uses the restaurant card’s hours; Google profile hours are edited separately in Google.
- Reply to reviews, including critical ones.
A chain
- Keep a single record of hours and phone numbers. In Eatery Club, restaurant cards supply that record for the site. Manually update profiles and delivery apps from those values, rather than copying values back from them.
- Give each profile’s website link a separate tag so you can distinguish traffic by location.
- Compare raw interaction counts alongside interactions per 100 profile views. The ratio accounts for different view volumes and helps select profiles for review; it does not count guests.
- Menu upload can be enabled for one location or for several at once. Before sending, the panel shows the menu link, section and item counts, photos Google will reject, and items it will skip, such as dishes without prices.

What Google counts, what you count, and what you can only check by hand

Google’s data
The Business Profile performance report is available only for verified profiles and shows metrics applicable to the business. These include profile views, counting a person at most once a day; searches; call-button clicks; direction requests; website clicks; menu interactions; and bookings through a booking provider, if you use one.
Search terms in the report update monthly. They show what people typed to find your profile, not a keyword tool’s estimate of market-wide search volume. Views, searches, and actions from Google Ads are included, too. Record paid activity during the reporting period before attributing a change to SEO.
Search Console shows your site’s clicks and impressions in Google Search; AI Overviews and AI Mode are included in the overall Web search data. The separate Generative AI performance report counts appearances of website links in these features by page, country, device, and date. Google dates the worldwide rollout to August 31, 2026. It does not report clicks, mentions without links, Business Profile citations, or orders. Google’s help page says a missing report can mean rollout has not reached the property or its links have appeared too rarely.
Website and ordering data
Add a UTM tag to the website link in your profile, such as ?utm_source=google&utm_medium=organic&utm_campaign=business_profile, and review the resulting sessions in Google Analytics 4 (GA4). A chain can add &utm_content= with a stable location identifier. Choose ? or & according to the existing link. If the site sends order events to GA4, you can see orders from tagged sessions. Without those events, sessions and orders remain separate counts.
GA4’s AI Assistant channel counts visits from ChatGPT, Gemini, DeepSeek, Copilot, Grok, and similar services when it recognizes the source. Visits from Google AI Overviews and AI Mode belong to Organic Search, not this channel. Mentions that produce no visit are not counted.
The ordering system keeps its own source records. Eatery Club uses Site, Mobile Site, QR Site, or app (order sources). Get monthly orders from the data export. Connect GA4 through “Google Analytics ID” in “Website Settings.” Changing the ID does not transfer historical data to the new property.
Manual checks and assumptions
Prepare ten searches guests use to find the restaurant. Run them monthly in Google, ChatGPT, and Gemini. Record mentions, factual accuracy, and cited sources, including answers without sources. This is a spot check, not a complete count: results vary with location, account, and day. If an answer is wrong, open the cited source and correct it if you own it.
A direction request does not establish a visit, nor does a call-button click establish a sale. Keep any assumptions about those events separate from measured data.
A sample month
This example uses a fictional restaurant with one location. All figures are hypothetical.
| What was counted | Source | Unit | Month |
|---|---|---|---|
| Profile views | Business Profile | person, at most once a day | 5,000 |
| Direction requests | Business Profile | direction request | 400 |
| Call-button clicks | Business Profile | click | 150 |
| Website clicks | Business Profile | click | 250 |
| Menu interactions | Business Profile | click on menu content (per user, per day) | 300 |
| Sessions with the profile tag | GA4 | session | 225 |
| All website sessions | GA4 | session | 3,000 |
| Online orders from the website and mobile site | Ordering system | order | 240 |
| Walk-in parties who named Google Maps | Door survey | party | 120 of 500 surveyed |
These rows use different sources and units. Do not add them to count guests or divide one by another to calculate conversion: several events may relate to the same purchase. None establishes revenue from SEO. Ratios within one source can be considered separately.
- The four profile action counts total 1,100 against 5,000 views, or 22 interactions per 100 views. Use that ratio to compare months and locations, not to claim 1,100 different guests. One person can call and request directions.
- The 250 website clicks and 225 tagged sessions measure different events. The profile counts clicks; GA4 counts sessions. Cookie consent, redirects, and tracking affect the difference.
- The 240 orders cover all website traffic. Identifying orders from profile-tagged sessions in GA4 requires the site to send an order event.
- Google Maps was named by 120 of the 500 parties surveyed, almost a quarter. The survey covers only guests who arrived. Some may have found the restaurant in Maps without requesting directions; some may have misremembered. Those who did not arrive are absent from the survey.
Calculate the three unverified assumptions separately, each in its own units. They do not describe independent groups of buyers: events can overlap.
| Hypothesis | Formula | Range | Result |
|---|---|---|---|
| A: share of direction requests followed by a visit and purchase | 400 × A | 20–50% | 80 to 200 visits with a purchase |
| B: share of call-button clicks ending in a purchase | 150 × B | 10–30% | 15 to 45 purchases |
| C: share of profile-tagged sessions ending in an online order | 225 × C | 4–12% | 9 to 27 orders |
Each range applies only to its own hypothesis; do not add them. Sending orders to GA4 can narrow C. Google’s reports provide no equivalent source for A or B. To investigate A, track direction requests and the share of surveyed parties naming Maps as separate series. If both rise for several consecutive months, that is a reason to examine the connection, not a measured share of visits with purchases.
A three-month plan
One location
Assign one person with about two hours a week for this work.
- Days 1 to 14. Before making changes, save the previous month’s profile metrics, GA4 sessions, and orders as a baseline. Run the quick review and fix hours, the phone number, the address, an incorrect “closed” status, and outdated menus that same week. Edit the restaurant card for website facts and the Google profile for Google facts. Verify the profile if needed.
- Days 15 to 30. Add the menu link and your own order link to the profile, and mark your preferred option in Google. If the restaurant is linked to a Google location in Eatery Club, enable menu upload and inspect the profile a few days later. Tag the website link and complete the technical checks. Write the ten searches and run them once for a baseline. Include searches in each language your guests use.
- Days 31 to 60. Keep a dated change log for the site and profile, and fix errors as you find them. Save the first month’s profile metrics, tagged sessions, AI Assistant channel data, orders by source, and Generative AI performance impressions if that report is available.
- Days 61 to 90. Collect the same metrics for the second month. Throughout the month, ask walk-in guests without reservations how they found the restaurant. Keep answers separate from direction requests. Repeat the ten searches and compare answers with the day 30 results.
- Day 90. Compare metrics with the baseline and, if available, the same month last year. Check remaining conflicts in facts and links, and record what you could not measure. Choose the next improvement from the facts and actions you can change.
A chain
There is no standard time allowance for a chain. Divide the work as follows:
- Assign a chain-wide owner and a manager at each location. Managers check hours and phone numbers and survey guests.
- List each location’s profile, Eatery Club card, menu upload status, link tag, and responsible person.
- Use available batch actions: upload menus for several locations and update hours from the single record.
- Each month, manually review a few locations with the lowest interactions per 100 profile views and a few selected at random. Before editing a profile, check whether hours, location, or demand explain the difference.
Use this list for ongoing reviews:
- Compare interactions per 100 profile views by location each month. If views increase without more interactions, inspect the query mix, photos, hours, reviews, and menu link before drawing a conclusion.
- Review branded versus other searches in the profile report monthly. The mix can help assess whether people find you more often without searching your name; it does not prove an increase in guests.
- Check profile-tagged sessions and the AI Assistant channel in GA4 each month.
- Save monthly online orders by source.
- Repeat the ten searches monthly, checking mentions, facts, and whether sources are supplied and which ones.
- Run the door survey once a quarter.
Comparing with the same month last year helps account for seasonality; it does not fully isolate it. Rolling four-week totals smooth weekly fluctuations. Google’s SEO Starter Guide says changes can take a few hours or several months to take effect and recommends waiting a few weeks before assessing a result.
After three months you will have corrected facts, two months of counts, the results of manual checks of AI answers, and a list of what cannot be measured. That is enough to decide what to fix next.
Related news: Google Business Management is now available to all Eatery Club clients.
Published in



