When a user pulls up Google Maps to find a coffee shop or a hardware store, the result they see feels simple—a pin, a name, and a set of business hours. However, this interaction is the final output of a gargantuan, multi-layered computational system that has remained largely opaque to the public.

New research, based on the reverse-engineering of a non-public binary associated with "Geostore"—Google’s internal system for managing geographic entities—has pulled back the curtain on how the search giant truly perceives the physical world. By cross-referencing this data with network traffic, mobile service protocols, and the seismic 2024 Google leak, investigators have mapped the architecture that governs local SEO and the future of conversational search.

The Canonical Entity: A Reality Beneath the Interface

The most critical takeaway for businesses is that a Google Business Profile (GBP) is not the "entity" itself. In Google’s internal architecture, a "Feature" is the canonical representation of a place. This Feature is a digital container that holds identity, geometry, relationships to business chains, Knowledge Graph references, and ranking data.

The familiar Maps listing is merely a rendering—an interface layer. What a business owner inputs into their dashboard is treated by Google as "evidence" that competes with hundreds of other data streams. This explains the long-standing frustration of business owners who edit their hours or descriptions, only to see the information revert or remain unchanged. Google isn’t just updating a database field; it is performing a complex "conflation" process where multiple sources—government records, web crawls, user reports, and provider APIs—are weighed against one another to determine the "truth" of an entity.

Chronology of Discovery and System Evolution

The understanding of how Google handles geography has evolved in three distinct phases:

  1. The Era of Siloed Listings (Pre-2015): Google treated local listings as independent entries largely reliant on basic directory data and user-provided inputs.
  2. The Knowledge Graph Integration (2015–2023): Google began stitching local entities to its broader Knowledge Graph, allowing for semantic connections between physical locations and web-based concepts.
  3. The Generative AI Transition (2024–Present): With the introduction of Gemini and "Ask Maps," the system moved from simple keyword matching to high-level semantic reasoning. The internal architecture had to shift to support "conversational" queries, requiring a much denser web of attributes than the traditional "name, address, phone number" model.

The current research marks a breakthrough because it allows for the granular inspection of the "Geostore" schemas. By accessing 10,936 internal declarations, researchers can now see the underlying protobuf tags that dictate how Google categorizes everything from a 3D building model to a specific transit station.

Supporting Data: The 793 Sources and 72 Signals

The complexity of Google’s data ingestion is staggering. The Geostore system manages inputs from 793 distinct source providers. When these providers disagree—for instance, if one source claims a business is a restaurant and another claims it is a retail store—Google’s provenance system kicks in. It utilizes a trust hierarchy that determines which source is "super-trusted" and which should be blocked.

The Oyster Rank Framework

Perhaps the most scrutinized part of the research is the "Oyster Rank," an internal ranking system containing 72 distinct signals. While the specific weightings (coefficients) of these signals remain hidden, their existence provides a roadmap for what Google deems important. Among these 72 signals:

  • Historical Signals: Data points that track the long-term reliability of an entity.
  • User Interaction Signals: Aggregated data on how users engage with specific listings.
  • Deprecated Signals: 25 of the 72 signals are explicitly marked as deprecated, showing that Google is aggressively pruning its legacy ranking logic.

Importantly, these 72 signals are not the "algorithm." They are merely the input for the Geostore entity’s importance. Once a query is initiated, the system triggers a complex pipeline: query understanding, semantic matching, geographic retrieval, and finally, reranking based on the user’s specific context.

Implications for Local SEO and Digital Strategy

For the SEO community, these findings necessitate a fundamental shift in strategy. The traditional "checklist" approach—optimizing for one keyword in a title or stuffing reviews—is becoming less effective as the system matures into an AI-driven entity-matching engine.

The Death of the Fixed Radius

One of the most persistent myths in local SEO is the idea that Google uses a fixed radius (e.g., a 5km circle) to determine search results. The data proves otherwise. The geographic footprint of a search is dynamic, changing based on the query density and the nature of the entity. A search for a generic "pharmacy" yields a very tight geographic window, whereas a brand-specific search like "Carrefour" allows for a much wider candidate space. Geography isn’t just a filter; it is a fundamental part of the initial retrieval strategy.

The Web-Maps Connection

Perhaps the most consequential finding is the deep integration between web documents and physical entities. Google’s "webref" layer associates web pages with specific MIDs (Machine IDs). This means that a location page on a brand’s website is not just a destination for traffic—it is a piece of evidence. If that page is properly structured, it informs the entity’s overall "topicality" and "confidence" score within the Geostore.

Semantic Completeness

As Google integrates Gemini into Maps, the ability to answer complex, multi-variable questions (e.g., "Where can six people eat near my hotel tonight, with one vegetarian, little waiting time, and good recent feedback?") becomes the gold standard. To rank in this new era, businesses must provide a "semantically complete" representation of their entity. This includes:

  • Deep Concepts: Linking menus, specific services, and atmosphere to the entity through structured data.
  • Multi-Location Consistency: Ensuring that every location in a chain is consistently represented across all 793 potential data providers.
  • Entity Evidence: Treating the website, third-party mentions, and social signals as "proof points" that reinforce the entity’s identity in the eyes of the algorithm.

Moving Toward a Holistic Representation

The takeaway for the professional SEO is clear: Stop thinking about your "listing" and start thinking about your "entity."

The listing is merely the surface-level display; the entity is the deep, data-rich object that lives inside Google’s infrastructure. If a business wants to dominate local search, it must move beyond simply managing a Google Business Profile. It must curate a digital footprint that is so logically consistent and semantically rich that Google’s systems have no ambiguity when selecting it as the answer to a user’s complex, natural-language query.

As Maps transitions from a search tool to an AI assistant, the brands that win will be those that provide the most "evidence" of their existence, quality, and relevance. The battleground has shifted from the map pin to the underlying Knowledge Graph, and in this new, AI-first environment, visibility is earned through the completeness of one’s digital identity.


Summary of Key Findings:

  • Geostore is the Authority: The canonical entity lives in Geostore, not the public-facing dashboard.
  • Provenance is King: Google relies on 793 sources; your GBP edits are just one piece of evidence among many.
  • Proximity is Fluid: The search radius is dynamic and adapts based on query type and location density.
  • AI Readiness: Future ranking will be dictated by how well an entity can be parsed by LLMs (Gemini) to answer complex, conversational queries.
  • Entities over Keywords: Semantic completeness is the new requirement for high-level local visibility.

Leave a Reply

Your email address will not be published. Required fields are marked *