## TL;DR

And pull up to 100 results per call with the pagination args instead of firing ten separate queries. For local rank tracking, pass the city-level location (coordinates where you have them), not just gl.

## Fix

1. And pull up to 100 results per call with the pagination args instead of firing ten separate queries.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Zenserp geo feature.
- The symptom matches: city-level location with coordinates beats a bare gl code.

## When NOT to use

- Unrelated Zenserp geo issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Zenserp geo.

## Variant phrasings

### city-level location with coordinates beats a bare gl code

## Why it happens

Web (Hackernoon SERP benchmark comparison): in their vendor table, Zenserp supports city-level geolocation with coordinates, all languages Google supports, desktop and mobile devices, up to 100 results in a single call plus pagination arguments, and basic custom error codes. If you track local rankings, the city location parameter is what keeps results stable; a bare country gl code gives you generic national results.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.