Your GBP Listing Isn't the Entity — Here's What Actually Ranks

Search Engine Land recently published a breakdown of how Google Maps actually works under the hood, based on documentation around Google’s Geostore system. If you run local SEO for a multi-location business, this changes how you should think about the work — not the tactics, but the underlying model.

The listing you edit isn’t the thing that ranks

Most local SEO advice treats a Google Business Profile as the source of truth: fix the name, fix the phone number, pick the category, done. That mental model is wrong, and it explains a lot of frustrating cases where correct edits get silently reverted.

Geostore, the system behind Maps, maintains a canonical object for every place — an entity — that is separate from the listing you see and edit. That entity is built from 793 different data sources, and it tracks 72 distinct ranking-relevant signals. Your GBP dashboard is one interface into this system, and your edits are treated as one piece of evidence, not a direct write to the entity.

When you change a phone number or category in GBP, you’re not overwriting Google’s internal record. You’re submitting a claim into a conflict-resolution process that weighs your edit against everything else Google has ingested — data aggregators, your website, review platforms, citations, government registries, and dozens of other feeds. If those sources disagree with your edit, Google can and does side with the majority, or with whichever source it trusts more for that attribute.

This is why business owners report the same maddening pattern: they fix the category or address in GBP, it looks correct for a few days, then it reverts. It’s not a bug. It’s the system re-resolving a conflict where your edit lost.

What this means for how you build local presence

If GBP is just one input into a bigger resolution system, the practical takeaway is that you need to win the majority of sources, not just the one you can directly edit.

Consistency is the actual lever. Name, phone, address, and category need to match across your own website, your GBP profile, and every directory or citation source that carries your business data. Inconsistency isn’t just a minor trust signal anymore — it’s literally evidence that the resolution system weighs against your preferred version of the entity.

Your own website carries more authority than people assume. It’s a first-party source that Google can crawl and cross-reference directly, which makes it one of the stronger pieces of evidence in the conflict-resolution stack. That means your site’s NAP data, location pages, and structured markup aren’t just there for users — they’re one of the 793 inputs actively competing to define the canonical record.

Structured data does real work here. Proper Schema.org markup — LocalBusiness, PostalAddress, and related types — gives Google a machine-readable, unambiguous version of your business attributes straight from your own domain. That’s a stronger signal than a free-text field in a directory listing, and it’s something entirely within your control, unlike third-party aggregators that may be pulling stale data from years ago.

Don’t fight incorrect attributes with GBP edits alone. If a wrong category, old phone number, or outdated address keeps reappearing, editing GBP again and hoping it sticks is treating a symptom. Audit where the conflicting data actually lives — data aggregators, old directory listings, outdated citations — and correct it at the source. The entity resolves toward whatever the weight of evidence supports.

For multi-location businesses, this compounds

If you manage dozens or hundreds of locations, inconsistent data at scale means each location entity is fighting its own version of this conflict-resolution problem independently. A single stale aggregator feed can quietly degrade location data across an entire network, and it won’t show up as an obvious error — just gradually worse visibility, wrong hours, or listings that revert after every fix.

The fix is systemic: audit citation consistency across all locations, standardize structured data templates across location pages, and treat GBP as a maintenance interface rather than the master record. If you want a structured way to find where your location data is conflicting and fix it at the source rather than chasing symptoms in GBP, that’s exactly what our local SEO service is built to handle.