Local grid tracking

A grid scan checks the local pack from many points around a location in one go. You see how visibility shifts across a neighbourhood instead of from a single spot.

<!-- 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 -->

Running a scan

Pick a grid size (3×3, 5×5, or 7×7), a spacing, and a zoom level. RankMeFast runs one Maps check per cell, and the whole grid counts as one metered scan.

For every cell it stores the position it saw, how big the local pack was, and when the check ran. Results appear as a heat grid, always with an accessible table beside it.

Reading a cell

Each cell shows one of three things:

• an observed position
• "not in the local pack"
• a failed check, which stores no position and is never drawn as a rank

Every cell has its own capture time. A grid is a set of checks taken close together, not one instant snapshot of the whole area.

Units and refunds

A scan with at least one usable cell uses its unit. You're refunded only if every cell fails, since a partial grid still has usable observations.

The Agency plan includes 6 scans a month. Pro gets grids through the geogrid-scans-10 credit pack, and Starter has no grid allowance.

See Pricing for units and plan limits.

Limits

You type coordinates in by hand. RankMeFast doesn't use a map-tile vendor, so there's no interactive map to click on.

A grid shows what the provider saw from those coordinates at that time. It isn't a prediction, and it doesn't tell you what any particular searcher will see.

Back to the docs index