Classic rank tracking and local rank tracking: what your SEO tool cannot see

A national tracker records one position per keyword. On a query with local intent that position does not exist: there is one per place, across three different result surfaces.

A classic rank tracker records one position per keyword, from one measurement point, in the organic results. On a query with local intent, all three assumptions fail at once: position varies by place, and most of the traffic goes through the local pack and Google Maps, which the tool does not measure. It remains useful — it simply does not answer this question.

What a national tracker measures on "service + city"

Take "plumber Manchester". A classic tracker returns a number: your page ranks seventh. That number is accurate, and it describes something precise — where your web page sits in the organic list, measured from the tool's query point.

What it does not say: whether your Business Profile appears in the local pack that occupies the top of the screen; where you rank on Google Maps; and what someone typing the same thing from another part of the city would see.

On a local query those three blind spots compound. You can be seventh organically, second in the local pack from the centre, and absent from the pack in the suburbs — three simultaneous truths, of which the tracker reports one.

The single measurement point bias

A national tracker queries Google from a fixed location: a data centre, a reference city, sometimes an entire country. That point is not documented in the report, and it matches none of your customers.

This is not a design flaw: for a query with no geographic dimension, a single point is sufficient, since the result is much the same everywhere. It is the use on a local query that is off-topic, distance being — per Google's documentation — a central local ranking factor.

The practical consequence: a position trend from a national tracker on a local query can move without anything changing for your customers, and stay flat while your visibility collapses in two neighbourhoods out of three.

Organic, local pack and Maps: three separate rankings

This is the most useful distinction in the article, and the one missing from most reports.

SurfaceWhat gets rankedDepthMeasured by a classic tracker
Organic resultsWeb pagesSeveral dozenYes
Local packBusiness Profiles3 visible, then "More places"Rarely, and without the geographic dimension
Google MapsBusiness ProfilesTwenty and moreNo

These three surfaces share neither criteria nor winners. A well-optimised page can dominate organic while a poorly filled profile stays out of the local pack. The reverse is just as common, and in fact more so among retailers: an excellent profile, a non-existent website.

Adding them into a single "average position" produces a number describing none of the three. It is the first thing to separate in a dashboard.

Implicitly local queries

The most expensive trap is not "plumber Manchester" but "plumber" on its own. Google treats a large share of service queries as local even with no city named: it knows the searcher's location and substitutes it for the missing place name.

Those queries are often the highest-volume ones, and they are precisely the ones a national tracker measures worst — since it has no location to substitute other than its own. A city-by-city keyword list therefore structurally understates the subject.

The quick test: if the results page shows a map and three businesses, the query is local, with or without a city name. If it shows ten blue links, it is not.

What to track locally

A local tracking block has four components, all tied to a named location and a date.

The local tracking block

  1. Local pack presence: are you in it, and where among the three.
  2. Google Maps position, which runs deeper and captures searches made inside the app.
  3. How many competitors appear ahead of you at that location, and which ones.
  4. Movement by area from one reading to the next — the gap carries the information, never a single reading.

How to choose those locations — and how not to pay for them needlessly — is covered in the tracking points article.

When classic tracking is still enough

It would be dishonest to conclude that a national tracker is useless. It remains the right tool in several situations, and telling them apart avoids paying for two setups where one will do.

Avantages

  • Informational queries with no local intent: "how to descale a boiler"
  • National sites or e-commerce with no physical location
  • Tracking content pages, blog posts, documentation
  • Competitive monitoring on web pages, not on profiles

Inconvénients

  • Service queries, with or without a city name
  • Anything that triggers a local pack or a map
  • Retail networks, franchises, multi-location businesses
  • Businesses whose customers come from within a few miles

The simple rule: if the results page shows a map, you need a geolocated measurement. Otherwise a classic tracker does the job, and does it well.

Add the dimension your tracking is missing

Pinperf records the local pack and Google Maps from the locations you choose, alongside your existing organic tracking tool. One trend line per location and per keyword, comparable month to month.

Explore Pinperf
It is not wrong, it is partial: it describes where your page sits in the organic results, from the tool's query point. It says nothing about your presence in the local pack or on Google Maps, nor about what a searcher elsewhere in the city would see.
No. The two setups measure different things and complement each other: one follows your web pages, the other your Business Profile across a territory. Swapping one for the other creates a blind spot in both directions.
Look at the results page: if it shows a map and a three-business card, the query is being treated as local, with or without a city name. If it only shows links, it is not.

Sources

Read next

All posts