Feature · Analyse
Local SEO: grid-level visibility across a service area
See where a business actually shows in Google Maps — block by block — instead of hiding behind one citywide rank. RankGear checks the rank at every point on a grid you define and maps the result.
Set up the grid
You draw the field in coordinates
Maps mode is precise by design — you set exactly where to look:
- Business keyword & target
- The query and the business you’re tracking.
- Coordinate center
- An exact latitude and longitude the grid is built around.
- Zoom, grid size & spacing
- How large an area, how many points, and how far apart — from a tight neighborhood to a whole metro.
- Provider
- SerpApi or RapidAPI Local Business Data, on your own account.
Read the map
Rank, NF, or ERR at every point
RankGear queries each grid point and marks it, then paints them onto an OpenStreetMap basemap with a complete point audit beneath:
- A rank
- The business’s position at that point, within your Top N.
- NF
- Not found within the Top N at that point — you’re invisible there.
- ERR
- The provider request for that point failed.
Correlation, not causation. A grid shows observed rank at selected coordinates and a moment in time — not permanent coverage, and not a reason the rank changed.
Beyond the grid
The local field, in full
Local-pack & Maps factors
The local-pack results and a Maps factor analysis for the query — not just the map.
Places evidence
Attractions, Landmarks, Map Tokens, and Service Areas sheets that describe the local field.
Nearby-place reports
Optional HTML reports on the places around your point, for context you can share.
Near vs coordinate Maps
Two ways to go local
| Organic ‘Near’ | Coordinate Local Grid | |
|---|---|---|
| Where it lives | Inside Analysis Run | Here, in Maps mode |
| Input | A Near city or state | Exact latitude/longitude + a grid |
| Answer | The organic field as seen from a place | Block-by-block Maps visibility across an area |
Boundaries
What to expect
Maps mode needs exact latitude and longitude — the Near box is hidden here because the workflow requires coordinates. One provider request is made per grid point, and the grid phase can’t be cancelled once it begins, so size the grid before you start.
Correlation, not causation. Grid results describe observed local visibility at a point in time — evidence for where to focus, not a guarantee of Maps position.
Questions, answered
What do NF and ERR mean?
NF = the business wasn’t found within your Top N at that point; ERR = the provider request for that point failed.
Which providers does it use?
The coordinate Maps analysis and Local Grid run through SerpApi or RapidAPI Local Business Data, using your own keys.
Can I cancel a running grid?
No — once the grid phase begins it runs to completion, because each point is a separate billable request. Size the grid before you start.
How is this different from a Near organic run?
A Near location gives the organic field as seen from a place (that’s Analysis Run). The Local Grid gives block-by-block Maps visibility across a whole area.
See the blocks where you disappear.
Map local visibility across a whole service area, point by point.
macOS 14+ (Apple silicon) · Windows 11 (x64/ARM64) · bring your own provider accounts