Platform · Google Maps module
Where you rank on Google Maps, point by point.
A business is not “number 3 on Maps”. It is number 1 at its own door, number 6 a mile east and absent two miles north, and the enquiry goes to whoever holds the top 3 where the customer is standing. The Google Maps module measures exactly that, on a grid, and compares each month with the last.
From the demo workspace
Real engine output on synthetic scans: a 5×5 grid, 1 mile apart, three terms, scan of 2026-09-10.
The module
This is the application’s own output, not a picture of one.
The grid on the left is the demo workspace’s scan for the term with the clearest gap; the figures on the right are the pooled coverage for all its terms.
“laser hair removal bradford”. Rank 1 at the centre, top 3 across 20% of the area, weakest to the east. That sentence is the finding the engine writes into the opportunity queue.
Coverage, defined. Valid points only; failed queries excluded and counted; all terms pooled so a term with few valid points cannot distort the headline.
What you see
Six views of one measurement
The workspace turns each scan into the questions an owner actually asks: where am I strong, where do I vanish, which way, what changed, who is taking it, and is the scan current.
The definitions are the GridTracker’s own, so a figure in the workspace equals the figure on its report. They are listed at the foot of every Maps page in the application.
The grid
One square per point with the rank inside; the centre outlined; a compass around it. Pick a term for its own grid, or pool every term.
By distance and direction
Coverage per ring outward from the door, the furthest ring where a top-3 majority holds, and the weakest side named.
Change, paired
Points better and worse since the previous scan on the same grid, with a change map that shows what each point was.
Who holds the top 3
From the JSON export: the competitors that appear where you do not, by how often and at what position.
Findings in the queue
A gap or a decline becomes a recommendation beside your paid and organic findings, classed as measured, with the ring and direction evidence attached.
Currency
A scan older than 45 days is flagged; the trend keeps every comparable scan so a month is never compared with the wrong one.
How a scan becomes a page
From export to evidence
- Scan
The HighRegard GridTracker searches Google Maps from each grid point for each term (UK results, mobile, coordinate-pinned), matching your listing by its identifiers rather than its name.
- Export
One scan is exported as CSV (points only) or JSON (points plus the listings seen at each point). Raw provider responses stay in the tracker.
- Import
The workspace stores the scan as an immutable measurement with its fingerprint: grid size, spacing, centre and depth. Re-importing the same scan replaces it; nothing edits one.
- Measure
Coverage, average rank, rings, directions and competitors are computed from valid points only. Points awaiting an identity decision in the tracker are quarantined here too.
- Compare
The previous scan on the same fingerprint is the baseline. Deltas are paired; below 80% paired coverage they are suppressed and the page says why.
- Act
Gaps and declines enter the opportunity queue as measured findings with the evidence attached, ranked beside everything else, and recorded when you decide.
What it does not claim
Professional judgement A grid position is a close proxy for what a searcher at that point sees, not a guarantee; results vary by device, time and personalisation. The module measures Google Maps results only, which are related to, but not the same as, the local pack inside web search, organic web rankings, and AI-assistant answers. It counts positions; it does not count customers, and no figure on it forecasts enquiries. Measured observation Our own calibration found the grid and an on-foot check agreeing at the centre and differing by one place 232 yards away; the note publishes the runs, the failures and the costs.
Which plans include it
A monthly Google Maps scan on your core terms, imported into your workspace and compared with the last, is part of HighRegard Local and HighRegard Growth. The Audit and the Repair Sprint use a scan where Maps visibility is in scope, so the before and after is measured rather than described. Software-only access is not sold yet; the module comes with the work.
Questions
Common questions about the Maps module
What is a geo-grid scan?
A grid of points around a business (for example 5×5, one mile apart). From each point, Google Maps is searched for a term as if the searcher stood there, and the business’s position in the results is recorded. The grid shows where a business is visible and where it is not, which a single “position” never can.
Is the position at each point exactly what a customer sees?
It is a close proxy, not a guarantee. Results vary by device, time and personalisation. Our calibration note records an on-foot check where the grid said 2 and a phone at the same spot said 1, 232 yards away; the centre point matched exactly. We publish that rather than hide it.
What counts as “not found”?
A query that returned results and did not include the business within the result depth (usually the top 20). A query that failed at the provider is not a ranking: it is excluded from every figure and counted separately, never recorded as “not found”.
How are two scans compared?
Only when they share the same grid, spacing, centre and depth, and only over the points measured validly in both. Below 80% paired coverage no change figures are shown, because a change in what was measured is not a change in ranking.
Which plans include it?
A monthly geo-grid scan on your core terms is part of HighRegard Local and HighRegard Growth. The Audit and the Repair Sprint use a scan as evidence where Maps visibility is in scope. The public demo shows the module on synthetic scans.
See the module on synthetic scans, then on your own.
The demo needs no sign-in. Your own scans come with the monthly plans, and with the audit where Maps is in scope.