How to Read a Local Rank Report: A Real Maprix Example

A local rank report can show similar averages on mobile and desktop while describing very different visibility across an area. The average only becomes useful when you know which points contributed to it.

The public Maprix example below records one search for ankara hotel. Use it to practise reading a report, then apply the same questions to your own scans.

Start with the measurement settings

Confirm the business, exact search phrase, scan date, device and grid before reading a score. In this example, the scan date is 28 July 2026 in Türkiye time. It uses a circular grid with 61 points and 1 km spacing. Those settings define the sample; they do not describe every search across Ankara.

Keep the scan date separate from this guide’s publication date. Opening an old public report today does not refresh its results. The geo-grid setup guide explains how the area and spacing affect what a scan can show.

A real report with two different coverage patterns

Desktop appears at 49 of the 61 points; mobile appears at 21. Their averages round to 5.6 and 5.7 respectively. Read those as positions within two different sets of found points. They do not establish that mobile and desktop had nearly equal visibility across the grid.

This dated snapshot shows one measurement; it does not establish a before-and-after change or an outcome attributable to Maprix.

Read average rank and coverage together

Maprix averages the positions where the business was found within the first 20 results. For desktop, 49 positions contribute to that average. For mobile, 21 positions contribute. Points where the business was not found remain visible in coverage; they receive no penalty position in the average.

Consequently, an average can improve when weak points disappear from the found set. Always ask whether coverage also changed before describing an improving average as progress. The measurement methodology gives the calculation rules.

In this scan, desktop coverage is about 80.3%; mobile coverage is about 34.4%. These are shares of sampled points, not shares of customers or geographic surface area. Each point has equal weight in this calculation; the report does not weight a busy street more heavily than a quiet one.

Inspect points and result bands

Look beyond the summary to see where the business appears and which neighbouring points return different positions. The bands separate positions 1–3, 4–10, 11–15 and 16–20. A point in the last band still counts as found. Outside the top 20 means the business was not found within that measurement’s search depth.

A failed measurement has a different meaning: there is no usable result for that point. It is excluded from the average and the valid-point coverage denominator. This sample has zero failed points on both devices, so both coverage calculations use 61 valid points.

Where the report provides a point’s competing results, inspect those before deciding what to investigate. A weak point can identify a question about relevance or nearby competitors; its colour cannot tell you which profile edit will fix it.

Keep device results and metric names separate

Compare mobile with mobile and desktop with desktop over time. The device comparison guide covers the controls needed for that comparison.

For the target business, Maprix’s visibility percentage is top-20 coverage. The competitor list’s weighted visibility score is a separate measure. Check the metric label before comparing values from different parts of a report; similar-looking percentages can answer different questions.

Turn the reading into a repeatable check

Record the phrase, language, grid centre, shape, point count, spacing and device. Repeat that setup and note the time of each scan. If you change the measured area or query, establish a separate baseline instead of treating the new result as a continuation of the old one.

Then investigate a specific observation. For example, check whether the same mobile points repeatedly fall outside the top 20. Review accurate profile details and the competing results at those points. Google’s local ranking guidance describes relevance, distance and prominence; it does not provide a formula that turns a report colour into a guaranteed action.

Use Reports for the account’s recorded history and comparisons. An open share link presents one selected snapshot. When explaining it to someone else, include the date, settings, average and coverage together, and state which next measurement would test your interpretation.