Google Business Profile
How Google Business Profile connects into SGEN — local visibility synchronized with site identity.
Google Business Profile (GBP) connects into SGEN as the local-business-visibility layer. Once configured, GBP synchronizes with the per-site SGEN identity so the business listing on Google reflects the same name, address, hours, and contact details as the SGEN site. This page is the Reference definition of the GBP integration — what it covers, what stays in sync, and what the dependency posture looks like.
What is this for?
Read this page when you want the structural definition of the GBP integration in SGEN — what role it plays in local business visibility, what fields synchronize between SGEN and GBP, and what the operator should expect when the connection is healthy versus unhealthy.
Good use cases
- You are scoping a multi-location site and need to know how GBP fits.
- You are explaining to a stakeholder how SGEN handles business-listing sync.
- You hit a "the GBP listing does not match the site" question and want the model laid out.
- You are designing internal SOPs around local SEO handoff.
What NOT to use this for
- Step-by-step GBP setup procedures — open the relevant Guide.
- GBP product documentation — Google's documentation, not here.
- Per-customer reputation management — out of scope.
- Per-release shipped behavior change — open What's New or Changelog.
How this connects to other features
- Integrations Overview — parent Reference area.
- Google Analytics 4 — sibling integration covering analytics.
- Google Search Console — sibling integration covering search performance.
- SG-Admin Overview — where GBP-paired identity fields live (Locations module, Site Settings).
Definition
GBP in SGEN is a connected local-visibility service. The platform synchronizes per-site identity fields with the GBP listing so the listing on Google Maps and Google Search reflects the same business detail as the SGEN site.
The defining property is bidirectional sync of identity fields. SGEN site identity flows out to GBP for the synchronized fields; GBP listing-state signals flow back into SGEN for surfacing.
Purpose
The purpose of this page is to define the GBP integration as a Reference layer rather than as a configuration walkthrough. It explains what synchronizes, where the operator sees the GBP state, and how the integration pairs with the admin Locations module.
Scope
This page covers the GBP integration at the Reference level.
The page covers:
- The connection role of GBP in SGEN's local-visibility layer.
- What fields synchronize between SGEN identity and the GBP listing.
- Where GBP-related signals appear in the admin.
- The dependency posture (healthy vs unhealthy).
- The boundary against GBP product documentation.
- GBP product detail — Google documentation.
- Per-step setup procedures — Guides.
- Reputation management or review-response workflows beyond surfacing — out of scope.
Connection model
GBP connects into SGEN through the platform's standard integration surface. The connection is per-site (each SGEN site can be paired with its own GBP listing).
Per-site listing
Each SGEN site can be paired with a GBP listing. The pairing happens in the per-site settings. Once paired, the synchronized fields stay in sync at the platform's defined cadence.
Synchronized fields
Business name, address, phone number, website URL, business hours, business categories. The synchronized set is the canonical identity layer; per-listing GBP-side fields outside the synchronized set are managed in GBP directly.
Site · Locations · GBP
Google Business Profile sync
Where GBP signals appear
GBP-related signals surface in the admin.
Locations module
The Locations module inside the admin shows the GBP-paired listing state, including the synchronized fields and the listing's current verification status.
Site Settings
The Site Settings surface inside the admin shows the GBP connection status as part of the site's integration health.
Dependency posture
GBP in SGEN depends on the listing being claimed and verified on the GBP side, and the connection between the listing and the SGEN site staying valid.
Healthy connection
Synchronized fields stay in sync. The listing reflects the latest SGEN identity within the platform's sync cadence. Listing-state signals (verified status, hours displayed) surface accurately inside the admin.
Unhealthy connection
Synchronization stops. Field changes on the SGEN side do not propagate to the GBP listing. The connection panel surfaces the unhealthy state with a status indicator and a reconnect prompt.
Constraints and boundaries
GBP is a Reference area for the connected local-visibility service. It is not a substitute for GBP product documentation or for reputation-management work.
Use this Reference for:
- Understanding the GBP connection role in SGEN.
- Confirming what fields synchronize.
- Diagnosing connection-health questions at the structural level.
- GBP product configuration — Google's documentation.
- Reputation management or review responses — out of scope.
- Step-by-step setup — Guides.
Public boundary
This page is intentionally public-safe. It does not expose GBP credentials, exact API surfaces, or protected operational identifiers.
Examples
Example 1 — Operator updates business hours
The operator updates business hours in the admin Locations module. The synchronized field flows out to the GBP listing within the sync cadence. The listing on Google Search and Maps reflects the new hours after the next sync completes.
Example 2 — Stakeholder asks "why does our listing show old hours?"
The platform lead opens this page (Where GBP signals appear + Dependency posture sections) and walks the stakeholder through the sync cadence and the connection-health check. The Reference resolves the question structurally before any deeper diagnosis is needed.
Example 3 — Connection goes unhealthy after re-verification
A re-verification event on the GBP side resets the connection. SG-Admin surfaces the unhealthy state. The operator opens this page, confirms the symptom matches, and reconnects via the Locations module connection panel.
Documentation guidance
Use this page as the structural definition for the GBP integration. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.Reading order
Open this page when scoping local visibility or troubleshooting listing-sync questions. Pair with SG-Admin Locations Reference for the per-site surface, and with Integrations Overview for the broader connection model.
Related reading
- Integrations Overview — parent Reference area.
- Google Analytics 4 — sibling integration.
- Google Search Console — sibling integration.
- SG-Admin Overview — where GBP-paired identity fields live.
Vocabulary cross-reference
- GBP listing is the Google-side configuration that defines the local business presence.
- Synchronized field is a per-site identity field that flows between SGEN and GBP automatically.
- Sync cadence is the platform's defined frequency for propagating field changes.
- Verification status is the GBP-side state indicating whether the listing is claimed and verified.
- Listing-state signal is the GBP-side data SGEN surfaces inside the platform.
Maintenance discipline
When the GBP integration changes across releases (new field synchronized, new connection panel, new verification flow), update this Reference and log the change in Changelog. The page stays valuable because the synchronized-field set stays small and the connection model stays stable.