The employee who created the profile left eighteen months ago. The recovery email still points to an inbox nobody can open. A vendor has manager access, the regional director thinks the owner is corporate, and the company cannot change the map pin customers are following into a construction site.
The listing is visible. The business is not in control.
Business listings are not a submission project. They are a distributed local identity system: a network of public records that tells customers and platforms which locations exist, what each one does, when it operates, who may represent it, and where a person should go next. Our SEO and content systems work treats that identity as governed infrastructure rather than a temporary local-ranking campaign.
The directory-count model is broken
The old service pitch promised seventy-five or two hundred directory submissions. The number looked productive because it was easy to count. It said nothing about whether those directories had an audience, whether the business was eligible, whether the facts were correct, or who would maintain them after the subscription ended.
The four controls of local identity
A listing earns its place by representing, verifying, routing, and surviving change.
Represent
State the real business, location, category, services, and operating conditions accurately.
Verify
Distinguish the entity from duplicates, lead generators, former occupants, and unrelated names.
Route
Move a person to the right location, phone, appointment, product, service, or support path.
Survive change
Preserve ownership and accuracy through turnover, vendors, moves, closures, rebrands, and acquisitions.
If a listing cannot do those jobs, its presence in a vendor dashboard is not success.
Build the Local Identity Record first
Create one controlled record for every eligible location before editing external profiles. This is the approved source from which website pages, structured data, map profiles, directories, review platforms, appointment systems, and reporting configurations should draw. It is the location-level counterpart to the claim discipline in the Commercial Legibility Diagnostic: public statements should agree with inspectable operational truth.
| Field group | Examples | Source owner |
|---|---|---|
| Entity | Public name, legal name, brand, department, practitioner relationship, location ID. | Legal, operations, or executive owner. |
| Eligibility | Storefront, service-area, hybrid, customer contact, signage, staffed hours. | Operations and policy reviewer. |
| Place | Address, suite, entrance, map coordinates, service area, accessibility, parking. | Facilities or location operations. |
| Contact | Primary phone, local phone, tracking number, email, support path. | Customer operations and measurement owner. |
| Offer | Primary category, secondary categories, services, products, attributes, restrictions. | Business or service-line owner. |
| Time | Regular hours, holiday hours, seasonal dates, temporary closure, effective dates. | Location operations. |
| Destinations | Canonical location page, appointment link, menu, order link, UTM rules. | Web and measurement owner. |
| Governance | Primary owner, backup owner, managers, recovery, last review, next review. | Internal system owner. |
The record needs version history. “Current” is not enough when a relocation takes six weeks to propagate or a platform restores an older fact from another source. Record the effective date, approved value, previous value, approving owner, affected surfaces, and completion state.
Material consistency matters more than punctuation
“Suite 200” and “Ste. 200” may be harmless formatting. Two phone numbers that reach different teams, a storefront profile for an unstaffed office, or a category that describes a service the location does not provide are material contradictions. Govern the facts that change eligibility, trust, routing, and customer action before standardizing abbreviations.
Eligibility comes before optimization
Do not create the profile and hope it qualifies later. Google currently requires most eligible businesses to make in-person contact with customers during stated hours. Its business eligibility and ownership guidelines identify online-only businesses, lead-generation companies, many rental properties, and locations without the required business presence as ineligible, subject to stated exceptions.
| Operating model | Identity decision | Common failure |
|---|---|---|
| Storefront | Use the real staffed customer-facing location and its actual hours. | Virtual office, mailbox, missing signage, or an address where customers cannot be served. |
| Service-area business | Represent the real operating base and legitimate service area; hide a residential address when required. | Inventing offices to imply presence in target cities. |
| Hybrid | Represent both the staffed location and the area where service is delivered. | Expanding the service area beyond operational reality. |
| Individual practitioner | Determine whether the practitioner and organization are separately eligible under the platform rules. | Duplicating the organization or creating profiles for non-public staff. |
| Multi-location business | Create one governed record for each distinct, eligible, staffed location. | Cloning categories, hours, and services that are not true at every location. |
| Online-only organization | Use the website, organization profiles, and other appropriate discovery surfaces. | Manufacturing a local address to gain map visibility. |
Eligibility varies by platform and business model. Document the rule and the evidence supporting each decision. A desired keyword market is not evidence that a location exists.
Ownership is the first control
The business should own its profiles through durable company-controlled accounts. Agencies, scheduling providers, franchise partners, and specialists may receive the access required for their work, but they should not become the sole path back into the identity.
Google's guidance says only owners or authorized representatives may verify and manage a Business Profile. It also directs authorized representatives to encourage the business owner to own the profile and add representatives as managers. Separate user access is available, so password sharing is unnecessary.
| Role | Recommended control | Exit requirement |
|---|---|---|
| Business primary owner | Durable company-controlled account with full authority. | Transfer deliberately during ownership or organizational change. |
| Backup internal owner | Second accountable employee with current recovery and access knowledge. | Replace before departure; verify access quarterly. |
| Agency or vendor | Manager or least-necessary role using an individual authorized account. | Remove access and transfer records at contract end. |
| Location operator | Role limited to the locations and functions the person actually manages. | Remove or reassign immediately after role change. |
Maintain an access register containing the account, role, person, business reason, approval, recovery owner, grant date, and removal date. Review it after employee departures, vendor changes, acquisitions, and security incidents, not only when a listing needs an edit.
Use a source hierarchy when facts disagree
Platforms may use owner edits, website content, user reports, public records, licensed data, and other sources. The answer is not to keep resubmitting one field while the business continues publishing a conflicting value elsewhere. The Evidence Architecture framework applies the same principle more broadly: a claim needs an authoritative source, accountable owner, stable destination, and review cycle.
- Confirm operational truth. The location owner approves what is actually true and when it becomes effective.
- Update first-party systems. Correct the canonical location page, contact data, structured data, appointment system, store locator, and internal feeds.
- Update priority profiles. Change the platforms customers actively use for discovery, navigation, reviews, and action.
- Resolve duplicates and former records. Merge, mark moved or closed, or appeal according to the platform and real-world condition.
- Correct relevant downstream citations. Prioritize sources with actual audience, authority, or data influence.
- Monitor for reversion. Confirm the live result and retain evidence when an old value returns.
Do not use a false fact simply because it is already consistent across several sites. Consistency can distribute an error as efficiently as it distributes truth.
Choose platforms by customer use and verification value
Most location systems begin with Google Business Profile, Apple Business, Bing for Business, the business's own location pages, and the map, review, navigation, booking, ordering, or voice-assistant surfaces relevant to its customers.
Then add industry and institutional sources with a legitimate verification job: licensing bodies, health-system profiles, insurer directories, tourism organizations, dealer locators, professional associations, chambers, campus directories, distributors, or marketplace records.
Evaluate each surface with five questions:
- Does a real customer, referrer, or platform use it?
- What material fact does it verify or route?
- Is the business eligible and able to maintain it?
- Can ownership and corrections be governed?
- What happens if the relationship, location, or fact changes?
A platform that fails those questions does not become valuable because a software vendor can submit to it automatically.
Give each location a canonical page
Each legitimate public location should have a durable, crawlable website page that answers the local decision: what is available here, who it serves, when it operates, how to reach it, what access conditions matter, and what action follows.
The page should carry the approved Local Identity Record, meaningful local content, a working phone and destination, directions or service-area context, relevant proof, accessibility information where available, and structured data that describes the visible content accurately. Link to the location through ordinary navigation or a useful locator. Do not publish hundreds of city pages for places where the business has no distinct presence or service reality. The Reed Medical Group case study shows this architecture applied to a real multi-location healthcare organization.
When profile links use campaign parameters for measurement, preserve the canonical location URL and document the tagging convention. The customer destination should remain stable even when analytics parameters change.
Run location changes as controlled migrations
A move, closure, rebrand, acquisition, or practitioner departure is not a collection of unrelated profile edits. It is a migration with an effective date, dependencies, fallbacks, and verification. The Customer Continuity Contract helps define what promise, identity, state, ownership, recovery, and measurement must survive the handoff.
| Change | Primary action | Critical safeguard |
|---|---|---|
| New location | Confirm eligibility, approve the identity record, publish the canonical page, then create or claim priority profiles. | Do not publish before the location can satisfy its real-world representation. |
| Relocation | Update the existing eligible profile and first-party sources according to the platform process. | Google advises against creating a new profile merely because the business moved. |
| Temporary closure | Use the platform's temporary state and communicate dates and customer alternatives. | Do not erase the entity or imply normal availability. |
| Permanent closure | Mark the location closed, preserve necessary records, and route customers responsibly. | Do not repurpose the old identity for a different business. |
| Rebrand | Determine whether the platform treats the change as the same business or a new entity; update coordinated first-party evidence. | Preserve legal, customer, review, and redirect implications. |
| Practitioner departure | Update organization and practitioner destinations based on ownership, eligibility, and the continuing business relationship. | Protect patient or customer continuity and avoid misleading affiliation. |
Google's duplicate profiles and ownership guidance says a business should generally have one profile, separate service profiles should not be created for the same business, and a relocated business should update its existing profile rather than create a new one. Exceptions for distinct eligible businesses, departments, and practitioners require the actual facts, not a workaround.
Separate review operations from profile governance
Profiles host reviews, but the review program needs its own policy, privacy boundary, response standard, escalation path, and operational feedback loop. The profile owner should not improvise those rules inside a tense notification.
Our Off-Page SEO Field Manual covers legitimate review requests, public responses, customer-evidence reporting, editorial references, communities, and partnerships. The local identity system supplies accurate places and accountable access; the broader off-page system governs the public relationships forming around them.
Measure routing and integrity before ranking stories
Record whether priority profiles are owned, eligible, accurate, complete enough for the customer decision, and connected to the right destination. Track change time, rejected edits, duplicate resolution, recurring reversions, review-response coverage, calls, directions, bookings, website visits, and qualified business outcomes where observable.
Profile actions, analytics sessions, call records, appointment systems, and CRM outcomes will not reconcile perfectly. A tracking number may improve attribution while creating a public consistency risk if implemented carelessly. A direction request does not prove a store visit. A profile view does not prove incremental demand.
Use the SEO Evidence Stack to label what each system actually observed. Then use the Measurement Custody Chain to keep identity, implementation, platform processing, and commercial interpretation from collapsing into one convenient local-ranking story.
The quarterly local identity review
- Verify control. Confirm primary and backup owners, managers, recovery methods, and access removals.
- Revalidate eligibility. Check customer contact, signage, staffed hours, service areas, departments, practitioners, and exceptions.
- Reconcile material facts. Compare the approved identity record with the website and priority profiles.
- Inspect the customer route. Test phone numbers, map pins, directions, appointments, menus, orders, and location pages on a real phone.
- Resolve structural issues. Address duplicates, former occupants, merged entities, closed locations, and unauthorized profiles.
- Review public evidence. Hand review themes, coverage, community activity, and relationship changes into the off-page operating system.
- Record consequence. Preserve changes, incidents, platform actions, customer signals, and commercial outcomes without overstating causation.
Run additional reviews before holidays, seasonal openings, relocations, acquisitions, leadership or practitioner changes, phone migrations, appointment-system changes, and rebrands. Fold the review into the Pixl Envy process so governance continues after the launch ticket closes.
The promise is the route
A local profile makes a small public promise: this business exists here, does this work, is available at this time, and can be reached through this path.
Governance is the work that keeps the promise intact after the marketing meeting ends. It lives in the backup owner who can still access the account, the operations manager who approves holiday hours, the location page that matches reality, the duplicate that was resolved carefully, and the map pin tested from the driver's seat.
The blue line should end at the right door.
Editorial note
This article was originally published in 2016 and materially rewritten and reviewed by Jason George on August 31, 2026. Platform-specific eligibility, ownership, representation, duplicate, and relocation statements were checked against the current Google Business Profile materials linked in context. Apple Business and Bing for Business are linked as official management destinations, not endorsements or evidence that every business needs every platform. The four local identity controls, Local Identity Record, ownership model, source hierarchy, change-control matrix, and quarterly review are Pixl Envy's original operating framework based on professional practice. Platform eligibility should be verified against current rules and the actual business model; this article does not promise rankings, profile approval, or revenue.