Google Maps

How to track Google Maps rankings for a restaurant

A defensible way to measure map visibility across a catchment — and how to tie ranking movement back to directions, calls and booking actions.

Alex Opsenica · Founder, Moolah Media

Published 16 January 2026

4 min read

On this page

There is no single Google Maps ranking for a restaurant. Map results are computed relative to where the searcher is, so a venue can hold position one on its own street and be invisible six hundred metres away. Any report that gives one number for "our map ranking" has quietly chosen a location and hidden that choice.

Key takeaway

Measure map visibility as an area, not a position: sample the same points across your catchment on the same schedule, then corroborate movement with Business Profile Performance and covers.

Why checking your own phone proves nothing

You are usually inside or beside the venue, the most favourable point on the map
Results are personalised by account history and previous visits
A single check has no baseline, so it cannot show a trend
Different staff checking from different places will report contradictory "rankings", and both will be right

Grid-based local rank tracking

Grid tracking: Sampling a query's map results from a fixed lattice of geographic points across a catchment, so visibility is recorded as a map of positions rather than one number.

A workable setup for a single restaurant is a grid covering the realistic catchment — walking distance in a dense city centre, a wider radius for a destination venue — sampled on a fixed cadence for a small, stable set of queries. The output is a shape: where you are visible, where you fade, and how that boundary moves month to month.

Setting up tracking that holds up

Fix the grid once: same centre, same radius, same spacing every run
Track five to ten queries a guest would genuinely type, not thirty variants of one
Include category and occasion queries, not just the restaurant name
Run on a fixed cadence — weekly or fortnightly — at a consistent time
Record the date of every profile or site change so movement can be read against it
Keep the same competitor set in view so gains can be read as relative

Worth avoiding

Screenshots of position one, taken from inside the restaurant, are the most common form of misleading local SEO reporting. If the location the check was run from is not stated, the number means nothing.

Corroborating with the profile's own data

Ranking data describes visibility. It does not describe behaviour. Business Profile Performance is the second half of the argument — it counts what people did once they saw the profile.

Business Profile Performance

Discovery searches

Searches where the guest did not use your name. The closest available proxy for new demand arriving through category and map queries.

Business Profile Performance

Directions requests

Map-native intent. A rising trend alongside a widening visible radius is a strong indication the two are connected.

Business Profile Performance

Website and booking clicks

Where visibility becomes commercial behaviour, and the number worth putting in front of an owner.

Source: Google Business Profile Help — Performance reporting — What the profile's own metrics count and how they are grouped.

Reading a month honestly

What a month of data can and cannot support

Observation	Fair conclusion	Overreach
Visible radius widened for cuisine queries	Relevance or prominence work is landing	"We now rank first in Dublin"
Discovery searches up, branded flat	New demand, not existing guests searching your name	"SEO delivered X covers"
Directions and booking clicks up with the radius	Visibility is converting into intent	A precise revenue figure attributed to search
Rankings up, actions flat	Investigate the profile's presentation: photos, reviews, hours	Report the ranking gain as a result

Visible radius widened for cuisine queries

Fair conclusion: Relevance or prominence work is landing
Overreach: "We now rank first in Dublin"

Discovery searches up, branded flat

Fair conclusion: New demand, not existing guests searching your name
Overreach: "SEO delivered X covers"

Directions and booking clicks up with the radius

Fair conclusion: Visibility is converting into intent
Overreach: A precise revenue figure attributed to search

Rankings up, actions flat

Fair conclusion: Investigate the profile's presentation: photos, reviews, hours
Overreach: Report the ranking gain as a result

See this in practice

Entering an occupied market and ranking ahead of it.

Chef-led landmark restaurant · name withheld · Dublin city centre restaurant corridor

#7Google local results position · recorded in BrightLocal · Local Finder

From no non-branded visibility to a #7 Google local results position on Dublin's most contested restaurant discovery term.

See tracked local pack movement in a real engagement

What to put in a monthly report

The grid map for the two or three queries that matter commercially, versus last period
Discovery versus branded searches on the profile
Directions, calls, website and booking actions, period on period
What changed on the profile or the site, and when
Covers or booking data from your own system for the same period
One paragraph stating plainly what is proven and what is inferred

Turning a grid into a decision

A grid is only useful if it changes what gets done next month. Read it as three questions rather than as a picture.

Where are we visible but not chosen? Usually a review, photo or menu problem rather than a ranking one.
Where are we invisible inside the catchment we actually serve? A relevance problem — categories, services, website content.
Where are we invisible far outside it? Distance. Leave it alone and stop paying to chase it.

Example · hypothetical

A hypothetical grid read

Imagine strong presence within a kilometre, patchy at two, absent at four. If most covers already come from within two kilometres, the useful work is conversion inside the visible area — photos, reviews, the booking path — not an attempt to rank four kilometres away where a nearer restaurant will always win on distance.

Worth avoiding

Do not report grid averages alone. An average hides the difference between being fifth everywhere and first in half a catchment and absent in the other half, which need opposite responses.

Common questions

What is a good Google Maps ranking for a restaurant?

There is no single ranking to be good at. A realistic target is holding the local pack across the area your guests actually search from, for the cuisine and occasion queries that bring covers — not position one at your own front door.

How often should map rankings be tracked?

Weekly or fortnightly on a fixed grid is enough to see trend without reacting to noise. Daily checks mostly record normal volatility.

Do rank tracking tools affect our rankings?

No. They sample results from simulated locations; they do not interact with the profile.

Working on this yourself? Measurement and reporting.

Where does your restaurant actually appear on the map?

A visibility audit checks your local pack positions from multiple points across your catchment area — not from one phone in one place.

Get Your Free Visibility Audit

Written 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.

More about how Moolah works.