Local grid tracking

A grid scan checks the local pack from many points around a location at once, so you can see how visibility changes across a neighbourhood rather than at a single point.

<!-- docs-truth: metric=geogrid_scans; unit=one-grid-scan-up-to-49-cells; cache-hits=count; refund=all-cell-failure-only; cadence=on-demand; estimates=provider-observation -->

How a grid is collected

You choose a 3×3, 5×5, or 7×7 grid with a spacing and a zoom level. RankMeFast runs one Maps check per cell, all inside one metered scan.

Each cell stores the observed position, the size of the local pack it was found in, and the time of capture. The result is drawn as a heat grid with a mandatory accessible table beside it.

Reading a cell

A cell is one of exactly three things: an observed position, an explicit "not in the local pack", or a failed check. A failed cell stores no position and is never drawn as a rank.

Because every cell carries its own capture time, a grid is a set of observations taken close together — not a single instantaneous snapshot of the whole area.

Units and refunds

A scan with at least one usable cell consumes its unit. Only an all-cell failure is refunded, because a partial grid still carries usable observations.

Grids are an Agency base capability with 6 scans a month. Pro reaches them through the geogrid-scans-10 credit pack; Free and Starter have no grid allowance.

Honest limits

Coordinates are typed in, not picked from a map. RankMeFast uses no map-tile vendor, so there is no interactive map to click.

A grid describes what the provider observed from those coordinates at that time. It is not a prediction and not a statement about what any individual searcher will see.

For units and plan limits, see Pricing.

Before acting, compare this guide with the stored evidence and status shown in RankMeFast.

Back to the docs index