Your Average Map Rank Improved. Did Your Visibility Actually Improve?
Use a matched-grid comparison protocol to separate ranking depth, coverage and missing observations, with a worked example of misleading averages.
An average local-map rank can improve while a business appears in fewer places. The apparent contradiction comes from the denominator: an average calculated only where the business was found excludes the locations where it disappeared.
What matters most
- A found-only average can improve while geographic coverage falls.
- Compare identical grid settings and retain incomplete observations separately.
A useful map report needs both ranking depth and geographic coverage, along with a record of what was measured. This protocol shows how to compare scans without turning a favorable-looking number into a broader claim than the evidence supports.
How to compare the same search experiment
Google explains that local results depend largely on relevance, distance and popularity. Location is therefore not incidental context when interpreting map observations. Google's local-ranking guidance.
Before calculating change, compare the keyword, business identifier, exact grid coordinates, search surface, language, device/settings where applicable, requested result depth and completion status. Record the tool and metric definition too. A grid's radius label can be ambiguous unless you know whether it describes an edge, corner or another distance.
If the footprint or keyword changes, show the old run as historical context and start a separate comparable series. Do not label the difference a clean growth percentage.
A small example that exposes the problem
The following values are invented for explanation, not client results. Both runs contain 49 completed search locations with identical settings. “Not found” means absent within the same requested search depth, not proven absent from every possible result.
| Metric | Run A | Run B |
|---|---|---|
| Found positions | 2, 5, 9, 12, 15, 18, 23 | 1, 2, 4, 5 |
| Found locations | 7 of 49 | 4 of 49 |
| Found coverage | 14.3% | 8.2% |
| Found-only average position | 12.0 | 3.0 |
| Top-three locations | 1 of 49 | 2 of 49 |
| Top-ten locations | 3 of 49 | 4 of 49 |
Run B has stronger positions where it appears and more top-ten locations, but lower overall found coverage. “Rank improved from 12 to 3” is mathematically true for that found-only average. “Visibility improved everywhere” is not.
The calculation is reproducible: Run A's found positions sum to 84, divided by seven equals 12. Run B's sum is 12, divided by four equals three. Found coverage uses all 49 completed locations as its denominator.
Keep missing data separate from not-found results
A failed or unfinished query is unknown, not automatically a poor rank. Record expected locations, completed locations, found locations and not-found locations separately.
If runs have different completion patterns, disclose the gap and consider a matched completed-location subset, clearly labeled with its own denominator. Do not silently drop missing points from one run while comparing it with the full footprint of another.
Put the comparison protocol into practice
- Identity: exact keyword, business and search surface.
- Geometry: retained coordinates and an unambiguous footprint definition.
- Depth: the same requested search depth and not-found treatment.
- Completeness: expected, completed and missing observations.
- Metrics: found coverage, top-three/top-ten counts and clearly labeled rank summaries.
- Timing: observation dates and the time span between them.
- Interpretation: what changed, what did not, and what remains uncertain.
Provider visibility indexes may apply their own weighting or scoring. Retain their definition and version rather than assuming that two tools' scores are interchangeable.
What the map comparison cannot prove
State a specific finding: “Coverage fell while remaining positions strengthened.” Then identify the affected keywords and areas for investigation. A pair of scans does not prove that a website edit caused the movement, and a map appearance is not a website visit, inquiry or booked job.
This is the kind of measurement discipline Mendola.Tech's managed website work should support: retained evidence, explicit comparisons and a next action that follows from the actual result—not simply the greenest number in a dashboard.
Official references
- Google's local-ranking guidance — consulted September 5, 2026; supports the linked technical guidance above.