A canonical location is the full, provider-recognized place name RankGear sends to a search API so a localized query resolves to the exact area you meant — not the broader region a loose “City, ST” abbreviation can quietly collapse into.
| Term | Canonical Location |
|---|---|
| Category | Search and SERP Data |
| Also known as | Provider Location Target |
| Where it appears | SerpApi localized searches |
What it means in RankGear
When RankGear pulls a localized SERP through SerpApi, it does not pass a loose string like “Austin, TX” straight to the provider. It first resolves that input to the location target the provider actually indexes — the canonical location — so results come back for the specific city you asked about rather than a metro area, county, or state. That resolved string is stored with the run, which is what lets every later comparison reference the same geography instead of drifting.
How to interpret it
Read the canonical location as one of the fixed inputs that defines a run, alongside provider, country, language, and device. Two SERP snapshots are only comparable when their canonical locations match exactly — a mismatch there can explain a ranking gap that has nothing to do with the page itself. Before you compare runs or trust a position, confirm the location resolved to the granularity you intended (a city, not the surrounding region).
Example
You request a Top 20 localized pull for “Springfield, IL.” Because more than a dozen U.S. towns share the name Springfield, RankGear resolves it to the provider’s canonical target — for instance “Springfield, Illinois, United States” — before the first API call. That Top 20 run may take several paginated provider calls, and each one reuses the identical canonical location, so all twenty results describe the same city rather than a mix of Springfields.
Important considerations
- An abbreviated or ambiguous input can silently resolve to a wider area; verify the canonical form matches the granularity you wanted before reading the results.
- Every call in a multi-page or Top 20 run must carry the same canonical location — if it varies, the merged result set mixes geographies and the comparison breaks.
- Localized SerpApi results are comparative snapshots of what a provider returns for a place at a moment, not Google’s own ranking scores — a position here does not mean a page “ranks” that way for every searcher in that city.
- Search results shift over time and by location, device, provider, and personalization, so holding the canonical location constant is what isolates real change from noise.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.