Measurement
Restaurant SEO measurement: proving the work earned covers
The full measurement stack for restaurant search: what each free report is genuinely good for, how to measure map visibility across a catchment, where attribution honestly ends, and what a monthly report should contain.
Alex Opsenica · Founder, Moolah Media
On this page
Most restaurant SEO reporting fails in the same way: it shows a position, a graph of impressions and a list of tasks, and leaves the owner to guess whether any of it filled a table. Measurement is not a monthly screenshot. It is a deliberate stack of four layers — visibility, interaction, website behaviour and commercial outcome — with the boundary between correlation and cause stated out loud.
Key takeaway
Measure four layers, in order: visibility across the catchment, guest interactions, website behaviour, and covers. Any report that stops before the fourth layer is describing activity, not results.
Why restaurant search is hard to measure
Google computes local results relative to the searcher's location, so there is no single ranking to report. A venue can sit first from the street outside and be invisible six hundred metres away. Add to that a booking journey that frequently ends on the phone or on a third-party platform, and single-number reporting stops being credible.
Source: Google Business Profile Help — How to improve your local ranking on Google — Relevance, distance and prominence — the documented basis for location-relative local results.
Worth avoiding
Any agency reporting a fixed "Google Maps position" for a restaurant is reporting one point on a map, usually measured from inside the restaurant. It is not wrong so much as meaningless on its own.
Layer one — visibility across the catchment
- Grid visibility
- The same query sampled from a fixed grid of geographic points across a defined catchment, on a fixed schedule. Progress is measured as the share of the grid where the venue appears in the local pack.
Grid rank tracking
Visible share of grid
The percentage of sampled points where the venue appears in the top three. It moves slowly, resists cherry-picking, and reflects an expanding or contracting radius rather than a single position.
| Measure | What it tells you | Reliability |
|---|---|---|
| Grid visibility over a fixed catchment | How much of your area can see you | High, if the grid never changes |
| Discovery searches on the profile | Whether non-brand demand is growing | High as a trend |
| Search Console impressions, non-brand | Whether website content is being surfaced | Moderate, sampled |
| A single local pack position | Almost nothing | Low |
Grid visibility over a fixed catchment
- What it tells you
- How much of your area can see you
- Reliability
- High, if the grid never changes
Discovery searches on the profile
- What it tells you
- Whether non-brand demand is growing
- Reliability
- High as a trend
Search Console impressions, non-brand
- What it tells you
- Whether website content is being surfaced
- Reliability
- Moderate, sampled
A single local pack position
- What it tells you
- Almost nothing
- Reliability
- Low
Layer two — interactions on the profile
Business Profile Performance records what guests did after seeing the profile: calls, direction requests, website clicks, booking clicks and message activity. This is the closest free data to intent, and it is the layer where visibility work first becomes visible commercially.
Source: Google Business Profile Help — Business Profile performance — Definitions for searches, views and interaction metrics used across profile reporting.
Business Profile Performance
Direction requests
A strong intent signal for a restaurant — a guest planning to arrive. It correlates with covers more closely than views, though it never proves them.
- Split discovery from direct searches before reading any interaction trend
- Compare like-for-like periods, and label seasonal effects rather than absorbing them
- Watch calls and direction requests together — a shift between them usually means a behaviour change, not a visibility change
Layer three — the website
Search Console covers the website only, and it is the only place to see whether menu, location and occasion pages are earning non-brand demand. Read it by page and by query group, not as one total.
Source: Google Search Console Help — Performance reports — Impression, click, CTR and position definitions, plus the sampling limits on query data.
The website questions worth asking monthly
- Is non-brand impression volume growing for the commercial pages?
- Which pages carry enquiry or booking intent, and are they being found?
- Did a page that used to earn demand quietly stop?
- Are mobile Core Web Vitals stable on real-user data?
- Did any technical change coincide with a drop?
Layer four — covers, and the honest limit of attribution
Only your own systems know what happened commercially: covers, average spend, enquiry volume, private dining bookings, no-show rate. Search data cannot see any of it, and no tool closes that gap for a business where a large share of bookings are made by phone.
State what is measured, state what is correlated, and never present the second as the first.
| Data | Status | How to report it |
|---|---|---|
| Profile views, searches, interactions | Measured by Google | Report directly |
| Grid visibility | Measured by sampling | Report with the method stated |
| Website clicks and conversions | Measured | Report directly |
| Covers and revenue | Measured by the restaurant | Report alongside, as correlation |
| "SEO generated X covers" | Not measurable | Do not claim it |
Profile views, searches, interactions
- Status
- Measured by Google
- How to report it
- Report directly
Grid visibility
- Status
- Measured by sampling
- How to report it
- Report with the method stated
Website clicks and conversions
- Status
- Measured
- How to report it
- Report directly
Covers and revenue
- Status
- Measured by the restaurant
- How to report it
- Report alongside, as correlation
"SEO generated X covers"
- Status
- Not measurable
- How to report it
- Do not claim it
See this in practice
What was recorded, and what it doesn't prove.
Premium steakhouse group · name withheld · Dublin 2
3,699Network covers · recorded in OpenTable
A Dublin 2 steakhouse grew covers 7% while its market fell 13%. OpenTable and Google data side by side, without claiming what they can't prove.
What was recorded, and what it doesn't prove.See this in practice
706,000 impressions — and the reservation page that leaks them.
Premium steakhouse group · name withheld · Dublin 2
706KSearch impressions · recorded in Google Search Console
The full funnel from impression to action, including a reservation page served 124,501 times at a 1.15% click-through rate.
See a full impression-to-action funnel, weak numbers includedSee this in practice
When the local market fell, this restaurant grew covers.
Chef-led landmark restaurant · name withheld · Dublin city centre
+33%Covers, year on year · recorded in OpenTable
Covers grew 33% year on year while a 75-venue OpenTable benchmark for the same area fell 9% — a 42 percentage-point spread.
See platform-recorded covers and the market comparisonA monthly report that stands up
- Discovery versus brand demand, with the split stated
- Grid visibility across the catchment, against the same grid as last month
- Profile interactions: calls, directions, website clicks, booking clicks
- Commercial page performance from Search Console
- Your booking numbers, presented as correlation
- What was done, what is next, and what got worse
Example · hypothetical
Hypothetical: the flat month that was not
Website impressions are unchanged and the report looks static. Grid visibility is up nine points, discovery searches are up a fifth and direction requests are up a third. The work landed on the map, not the website. A report built on website data alone would have recorded a month of nothing.
Set the baseline before any work begins. Measurement started three months in cannot describe what changed, and every honest reporting relationship depends on a baseline both sides agreed to.
Common questions
How do you measure restaurant SEO?
In four layers: grid visibility across the catchment, profile interactions such as calls and direction requests, website performance for commercial pages, and the restaurant's own covers and enquiry data reported as correlation.
Can SEO be attributed to restaurant covers?
Not directly, and anyone claiming otherwise is overstating it. A large share of restaurant bookings happen by phone or on third-party platforms. The honest approach is to report search outcomes as measured and booking outcomes alongside them as correlation.
How long before restaurant SEO shows in the data?
Profile interactions can move within weeks of accuracy and category fixes. Grid visibility and non-brand website demand usually take one to two quarters, and should be judged against a baseline taken before the work started.
What should a monthly restaurant SEO report contain?
Discovery versus brand demand, grid visibility against a fixed grid, profile interactions, commercial page performance, your booking numbers as correlation, and a plain statement of what was done, what is next and what got worse.
Is average position a useful metric for a restaurant?
Only directionally. Local results are relative to the searcher's location, so an average across locations does not describe what any real guest saw.
Working on this yourself? See how Moolah reports.
Not sure which numbers to trust?
The audit sets out what your current reporting can and cannot prove, and which measures would actually tell you whether search work is paying.
Get Your Free Visibility AuditWritten by
Alex Opsenica
Founder, Moolah Media
Founder of Moolah Media, a founder-led restaurant marketing specialist based in Ireland, working with restaurants worldwide on websites, SEO and Google Maps, and Google Ads. Around 20 years in hospitality, including hands-on restaurant management.
Continue exploring
Measurement
How to measure whether restaurant SEO is working
Which reports prove what, how to read ranking movement against covers, and what an honest monthly restaurant SEO report contains.
3 min readPublished 1 Jan 2026
Read Insight
Measurement
Search Console vs Business Profile Performance
The two free reports every restaurant should read: what Search Console and Business Profile Performance each measure, where they disagree, and which to trust.
3 min readPublished 23 Mar 2026
Read Insight
Measurement
Which SEO metrics actually matter to a restaurant?
Search Console, Business Profile Performance, GA4 and booking data: what each proves, and which numbers are worth reporting.
3 min readUpdated 13 Jan 2026
Read Insight
