What does centroid bias describe?

Jed Schaible’s local-search lecture notes use “centroid bias” to describe a preference for businesses near a city centre. Treat that as an attributed practitioner explanation. Understanding a particular result still requires checking the search context and what the available evidence can establish.

Ask what location the observation represents

A city name can appear in a search query, a report title or a location setting. Those labels do not necessarily describe the same thing. Before interpreting a difference in rankings, identify the result being compared and the location information that came with it.

Start with Google’s published explanation

Google’s local-ranking guidance describes relevance, distance and prominence. Its distance section concerns how far a business is from the customer searching. If the customer does not share their location, Google says it uses what it knows about that location.

The same guide says Google keeps algorithm details confidential. Its public explanation does not give a mathematical city-boundary formula or a conversion between extra reviews and distance.

Distinguish the search location from the report point

Google’s location help describes estimation from available sources, including device location, home or work information, previous activity and an internet address. It also explains that the bottom of the results page can indicate how location was estimated. This is broader than assuming every nearby search uses a precise GPS fix.

BrightLocal’s Local Rank Tracker help describes its report as a search from a single point based on the selected city, town or ZIP code. It calls the central point a centroid and explicitly distinguishes that report from an average of rankings across the city.

A provider’s chosen search point is part of the report’s method. Check that method before applying its result to customers elsewhere. A point described as central in a reporting tool does not by itself establish the reference point or formula behind every Google search.

A fictional cycle shop comparing two records

Imagine a fictional Juniper Cycle Works operator with a city-named rank report and a separate nearby search capture. The following constructed worksheet identifies what the operator needs to check. It contains no real search results, coordinates, ranking positions or measured change.

Illustrative Juniper Cycle Works comparison checks
FieldQuestion for the two recordsWhy it matters
QueryWhat exact words were used in the report and the separate search?A city-named query and a different nearby query do not isolate the effect of location.
Result surfaceDoes each record concern Search, Maps or another specified result view?The operator needs to know which result is being compared.
Location contextWhat point does the report represent, and what location source did the search page show?A report label should not be substituted for the other record’s actual location information.
Time and setupWhen was each record captured, and what settings or collection details were recorded?Changes in context remain possible explanations to examine.

If the records differ in both wording and location context, the operator has more than one difference to investigate. A useful next comparison starts by deciding what should stay consistent and what question the observation is meant to answer. Naming the pattern does not supply that comparison.

Proximity Factor addresses the broader distance question. Geo-Grid Rank Tracking addresses observations from multiple points. A single-point report and a grid have different coverage; neither format alone reveals the algorithm’s numerical weights.

Choose a comparison you can explain

Keep the exact query, result surface, location context and capture time with the observation. When reviewing a later report, check whether the collection method or settings changed. Describe the scope that was actually observed instead of presenting one point as the experience of an entire city.

Ask the provider what an unclear location label or result field means. If the search context cannot be recovered, retain that uncertainty when discussing the result. The next useful check may be a better-specified observation rather than another change to the business’s profile or website.

Do not turn a pattern into a ranking formula

A competitor’s location and review count do not isolate what produced its position. Avoid translating a review-count difference into an equivalent number of miles, or treating a changed ranking after content work as proof of which hidden signal changed.

The same caution applies to a city-centre explanation. A reporting pattern can suggest a question to investigate without proving that explanation, and a limited public description cannot prove the opposite claim that a central location could never matter.

Use the report to choose the next check

For a business-information problem, start with the actual operation: its location model, services, hours and customer contact route. The Local SEO guide addresses that review. Keep it separate from an attempt to infer ranking mechanics from one report.

For a measurement problem, return to the missing field in the comparison record. Clarifying the report point or the query can make the observation more useful without promising a ranking improvement. No review quota or fixed recovery period follows from the worksheet.

Use the linked guides for the distance, reporting or business-information task you need to resolve. Keep the original observation and its context available as the team discusses what to check next.

Sources

Google’s pages supply the published ranking and location explanations. BrightLocal supplies its own report method. Schaible’s notes establish the cited use of the phrase, not a verified current Google rule. The Juniper worksheet is fictional.