Presence Surfaces
Each surface reads a different slice of the record.
A business appears across search, local, commerce, publishing and AI surfaces. Each one consumes a different subset of facts, so each one can be wrong in a different way.
10 surface classesPer-surface expressionDrift classification
Surface classes
What each class consumes
| CLASS | READS FROM RECORD | FAILURE MODE |
|---|---|---|
| Search engines | Identity, categories, structured data, entity relationships | Conflicting names and categories weaken entity resolution. |
| Maps | Addresses, geocodes, hours, service areas | Duplicate pins and stale hours send customers to closed doors. |
| Directories | Core identity and contact information | Legacy entries persist for years after a change. |
| Marketplaces | Catalog, services, offers, pricing | Incomplete catalog data removes the business from consideration. |
| Review platforms | Identity, locations, response history | Reviews attach to the wrong location record. |
| Social platforms | Brand, media, contact, hours | Profiles drift from the canonical brand and contact facts. |
| Publisher networks | Narrative, media, credentials | Outdated descriptions circulate widely and get cited. |
| Local media | Identity, events, offers | Local coverage repeats old facts as current. |
| Knowledge graphs | Identifiers, relationships, verification | Missing relationships break the entity's connections. |
| AI systems | Machine-readable record, citations, schema | Unstructured information is summarized incorrectly. |
Surface classes describe categories of destination, not confirmed integrations with named platforms.