Key takeaways
- Maintain a versioned source of truth for each real entity and location, including identifiers—not just name, address, and phone.
- Propagate openings, moves, closures, rebrands, mergers, and phone changes as controlled events with effective dates.
- Prioritize customer-used and authoritative platforms; more listings do not automatically mean more trust or visibility.
- Verify the rendered record, resolve duplicates and old locations carefully, and retain the change history.
01
A spreadsheet of listings is not yet an identity system
The business moves. Marketing updates the website, operations updates the phone system, an agency changes Google, and an aggregator republishes the old address from a legacy feed. Six months later the old location still receives calls and the team “fixes” whichever directory a customer mentions that day.
Create an authoritative entity record with legal and trading names, real-world display name, location ID, store code, address components, service area, coordinates, primary and additional phone numbers, canonical URL, categories, hours source, opening and closure dates, parent entity, profile IDs, and evidence. Version it. A change should be an event, not an unexplained overwritten cell.
Swipe to compare every column
| Change event | Required decision | Common residue |
|---|---|---|
| Move | Old-place status and new-place verification | Both locations shown as open |
| Rebrand | Continuity versus a genuinely new entity | Old and new names split across sources |
| Phone change | Canonical number and forwarding period | Dead number in high-use directories |
| Closure | Temporary or permanent status | Deleted record recreated from stale feed |
02
Choose propagation priority from customer use and authority
Update the owned location page and operational systems, then the primary search and map profiles, relevant industry or government sources, navigation providers, major customer-used directories, and lower-priority listings. The order depends on the business. A healthcare directory or licensing register can matter more than a generic directory with a high domain metric.
Do not buy hundreds of listings because a dashboard offers a larger count. A listing is useful when it accurately represents a real business where customers or data systems rely on it. Low-quality duplication creates more surfaces to maintain and more opportunities for stale data to return.
03
Handle duplicates and closures as identity decisions
Compare platform IDs, coordinates, phone, URL, photos, reviews, opening date, and business history before merging, closing, or reporting a duplicate. Two departments at one address may be distinct; two spellings may be the same entity. A mistaken merge can strand reviews or erase a valid customer destination.
Keep old URLs useful where possible, explain a move to customers, preserve appropriate forwarding, and mark the old place accurately rather than pretending it never existed. Follow each platform’s correction process and save confirmation, case IDs, and evidence.
04
Reconcile what the platforms actually show
A submitted update is not a completed update. Fetch or inspect the live record after propagation, normalize harmless formatting differences, and route material conflicts for review. Watch for user edits, licensed data, and an old vendor feed overwriting the authoritative value.
Measure time to consistent customer-facing data, priority-source accuracy, duplicate resolution, reopened stale records, wrong-number calls, misdirected visits, and unresolved exceptions. Citation operations succeed when a person reaches the correct business—not when a tool turns every row green.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- Google: Guidelines for representing your business
- Google Business Profile APIs: Work with location data
- Schema.org: LocalBusiness
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem



