Newly surfaced analysis of a recovered Google Maps binary offers an unusual look at the infrastructure behind local search. The material identifies an internal system called Oyster Rank, operating over a Geostore entity model, and lists 72 ranking signals. It also points to a far broader data environment than the familiar Google Business Profile view: 793 data-source providers and 446 local search intent types are referenced in the recovered materials.
The most important takeaway for businesses is not that Google has revealed a 72-factor checklist. The reporting indicates that these signals are internal terms used across multiple scoring and retrieval stages, rather than a single public formula with fixed weights. Local visibility appears to depend on how Google represents, connects and retrieves information about a business as an entity across Maps, the web, location-aware systems and related data sources.
Search Engine Land’s reporting on the recovered Google Maps data describes the discovery as a view into this architecture, not a definitive guide to a static local-ranking algorithm. That distinction matters. Businesses should resist treating a list of internal signal names as a set of direct ranking controls.
What the recovered data says about Google Maps
According to the analysis, Oyster Rank enumerates 72 ranking signals, of which 25 are explicitly marked deprecated in the recovered data. Deprecated signals are particularly important context: the list is not a clean inventory of active, equally influential factors. It is evidence of an evolving internal system with historical components, rather than an operational recipe for reaching the top of Maps results.
The Geostore model is the more consequential finding. The recovered materials reportedly describe a business or place through an entity-based system that can combine information from numerous providers and interpret many kinds of local intent. This supports a model in which a map listing is one representation of a business, not the whole object Google evaluates.
| Recovered component | What the analysis identifies | Why it matters for local visibility |
|---|---|---|
| Oyster Rank | 72 named ranking signals, including 25 marked deprecated | The names should not be treated as a single weighted ranking formula. |
| Geostore entity model | 793 distinct data-source providers and 446 local search intent types | Google Maps appears to rely on distributed, entity-centric information rather than a listing alone. |
| Map rendering and search data | About 50,998 Mapcore styles, 12,936 label styles and 10,936 searchable Geostore declarations | Map presentation, searchability and ranking are parts of a much larger technical environment. |
The reporting also identifies separate offline or on-device scoring and distinguishes ranking from map visibility. In practical terms, appearing in a particular map context is not necessarily the same process as ranking for a conventional local query. The recovered material does not provide public weights, a definitive list of active signals, or a way to predict an individual business’s placement.
Why the entity model changes local SEO priorities
For years, local SEO work has often centered on listing completeness, reviews, categories, proximity and citations. Those elements can still be useful evidence about a business, but the recovered architecture suggests a more accurate mental model: Google is attempting to reconcile many signals about a real-world entity and then match that entity to a specific local intent.
That means changes in a Google Business Profile should be viewed as inputs to a wider evidence system. The reporting characterizes profile edits as evidence or votes within the ecosystem, not commands that directly instruct Google to rank a business. A complete profile is therefore valuable, but it cannot compensate indefinitely for conflicting, incomplete or weak information elsewhere in the data environment.
A practical local visibility program should focus on consistency and relevance across the places where business facts can be established. For a location-based company, that can mean checking whether its name, address, phone details, category information, operating hours and website location pages accurately reflect the business. It can also mean ensuring that the website clearly connects services to the locations the company genuinely serves.
The useful shift is from chasing an isolated ranking factor to reducing ambiguity about the business entity. This is not a claim that every source is equally influential, or that every possible directory deserves attention. The recovered data does not establish that. It does show why a narrow optimization strategy, focused only on editing a profile, is unlikely to capture the full way Google Maps organizes local information.
For measurement, businesses should separate outcomes that are often blended together. Track visibility for meaningful local searches, but also monitor whether business facts remain consistent, whether service and location pages accurately describe the offering, and whether profile updates are reflected correctly. Because the reporting distinguishes ranking from map visibility, a change in one measurement may not explain every change in another.
A sensible response to this discovery includes:
- Audit core business facts across the Google Business Profile, website and relevant third-party listings.
- Strengthen entity clarity by using consistent names, service descriptions, location information and contact details where they are genuinely applicable.
- Measure by intent and location, rather than relying on one generic keyword or a single map position.
- Treat profile maintenance as ongoing evidence management, not as a one-time ranking tactic.
- Avoid formula-based promises built around the 72 signal names, because the recovered list includes deprecated terms and does not disclose weights.
For businesses that depend on local discovery, the opportunity is to replace fragmented reporting with a clearer view of customer intent, location data and visibility signals. Scalevise’s AI consultancy can help assess where disconnected business data is creating avoidable ambiguity, prioritise practical measurement improvements and identify automation opportunities that reduce manual upkeep. The goal is not to chase a secret Google formula, but to build a more reliable foundation for search visibility. Request a consultation to map the next practical steps.
Frequently Asked Questions
What are Google Maps’ 72 ranking signals?
They are 72 internal signal terms enumerated in recovered Google Maps material associated with Oyster Rank. The reporting does not show that they are a single public ranking formula, and 25 are marked deprecated.
What is Oyster Rank?
Oyster Rank is the name used for an internal Google system identified in the recovered analysis. It is described as operating over the Geostore entity model and using multiple scoring and retrieval stages.
What is Geostore in the recovered Google Maps data?
Geostore is described as an entity model for places and businesses. The recovered materials reportedly reference 793 data-source providers and 446 local search intent types within that model.
Do Google Business Profile edits directly improve Maps rankings?
The reporting characterizes profile edits as evidence or votes in a wider ecosystem, not direct commands to rank. Accurate and complete information remains useful, but the materials do not support a guaranteed ranking outcome from any single edit.
Conclusion
The recovered Google Maps data is valuable because it reinforces how complex local visibility has become. Oyster Rank, Geostore and the large number of referenced data sources point to an entity-centric system that goes well beyond a standalone map listing. For businesses, the practical response is to improve the clarity and consistency of real-world business information, measure local performance by intent and location, and avoid simplistic claims about a fixed list of ranking factors.
Top comments (0)