Locations
| Field | Value ||---|---|| Audience | public || Page type | reference || Area | sg-admin || Updated | 2026-05-14 |The SG-Admin Locations module — physical business locations with hours, contact, GBP integration.
The Locations module in the admin is the per-site surface for physical business location records — address, hours, phone, services, GBP listing pairing. Multi-location businesses use this module to administer every location from one place. This page is the Reference definition.
What is this for?
Read this page when you want the structural definition of the Locations module — the location record, multi-location administration, and the GBP integration relationship.
Good use cases
- You are scoping a multi-location business site.
- You are explaining to a stakeholder how SGEN handles location data.
- You hit a "where do we update store hours?" question.
What NOT to use this for
- Step-by-step procedures — open the relevant Guide.
- GBP product detail — open Google Business Profile Reference.
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- SG-Admin Overview — parent surface.
- Google Business Profile — integration that consumes location records and syncs hours, address, and contact to the public Google listing.
- Events — event records reference location records when a venue corresponds to a stored physical location.
- Templates — public location pages and location-list pages render through templates the site author can adjust.
Before you start
You need the following before adding locations to a site that has not used them before:
- The full list of physical locations the site represents — name, full address, phone, email, regular hours, special hours / holidays, services per location.
- Image assets (location photos) for each location. Place these in the Media Library first.
- A decision on GBP pairing — whether each location should be linked to a Google Business Profile listing so updates sync.
- A decision on the public surface — a per-location page, a single location-list page, or both.
Where to find it
The Locations module lives in the admin under the content / business group. The exact menu position is documented in the platform's current navigation.
Steps
The steps below cover adding the first location to a site that has not used Locations before.
1. Open Locations and add a new location
Open SG-Admin, go to Locations, choose Add new location. Fill the identity fields:
- Name — the public name of the location (often the city or branch label).
- Slug — the URL fragment for the per-location page.
- Internal ID — auto-assigned by the platform; surfaced for reference.
2. Fill address, contact, and hours
Enter the full address (street, city, region, postal code, country). Enter contact details (phone, email, website where it differs from the site root).
Set the regular hours per day of the week. Mark closed days. Add special hours for known holidays or exceptions in advance — the platform supports holiday entries with a date and an alternate hours range (or closed flag).
Site · SG-Admin · Locations · New location
3. Add services and media
Add the per-location services if the site differentiates services by location. Add location photos. Media references the Media Library; the photos do not need to be re-uploaded if they already exist there.
4. Pair with Google Business Profile (optional)
If the location should sync to a Google Business Profile listing, pair it. The pairing is a one-time step per location; once paired, updates to address, hours, and contact in the location record sync to the GBP listing on the next sync cycle.
5. Publish and confirm the public surface
Publish the location. The per-location page surfaces at the location slug; the location appears in the location-list page if the site has one.
What success looks like
A site running Locations behaves as follows:
- Each physical location has its own record with current hours and contact details.
- The public location-list page shows every location with at-a-glance hours and contact.
- Per-location pages render the full record — full address with map, hours, contact, services, photos.
- Paired GBP listings reflect the location record within the sync window.
- Events that reference a location pull the venue details from the location record; updates to the location automatically reach the event display.
What to do if it does not work
- A location does not appear in the public list. Confirm the location is published, not draft. Confirm the listing template includes the location.
- Hours show as wrong on the public page. Confirm the regular hours and special hours are set in the right time zone. Special hours override regular hours on the affected date.
- GBP listing does not reflect the latest changes. Sync is not instantaneous; wait for the next sync cycle. If the change still does not appear, re-confirm the GBP pairing is active and the integration token is valid.
- An event references a venue that does not match the location record. Re-open the event and re-select the location record. The event display pulls the venue from the linked location at render time.
- A pop-up or temporary location should hide after a date. Set the location to draft after the temporary date, or schedule the change.
Definition
A location record in the admin represents one physical business location. It carries identity (name, slug), address (full street + city + region), contact (phone, email), hours (per-day hour ranges, closed days, special hours), services (per-location service list where applicable), media (location photos), and GBP pairing (where the location is paired with a GBP listing).
The defining property is per-physical-location. Multi-location businesses have multiple records; single-location businesses have one.
Purpose
Define the Locations module as a Reference layer.
Scope
Covers the location record, multi-location administration, GBP pairing. Does not cover GBP product config (GBP Reference) or per-step procedures (Guides).
Location record
Identity
Name, slug, internal ID.
Address
Street, city, region, postal code, country.
Contact
Phone (often the tap-tracked number), email, website (typically the site root).
Hours
Per-day hour ranges, closed days, special hours (holidays, exceptions).
Services
Per-location service list where applicable.
Media
Location photos.
GBP pairing
Optional pairing with a Google Business Profile listing.
Site · SG-Admin · Locations
Business locations
| Name | City | Phone | Hours today | GBP |
|---|---|---|---|---|
| Manila Main | Manila, PH | +63 2 8XXX | 09:00-18:00 | Connected |
| Cebu Branch | Cebu, PH | +63 32 XXX | 10:00-19:00 | Connected |
| Davao Pop-up | Davao, PH | +63 82 XXX | Closed today | Not connected |
GBP pairing
Each location can be paired with a Google Business Profile listing per the GBP Integration Reference. Once paired, location-record updates (hours, address, contact) sync to the GBP listing automatically.
Constraints and boundaries
Locations is a Reference area for physical business location records.
Do not use for: GBP product config (GBP Reference), per-step procedures (Guides), per-release shipped change.
Public boundary
This page is intentionally public-safe.
Examples
Example 1 — Operator updates hours for a holiday
Operator opens the affected location, adds a special-hours entry for the holiday. The location surface updates; the paired GBP listing reflects the change after the next sync.
Example 2 — Operator adds a new pop-up location
Operator clicks Add location, fills address + temporary hours. The location appears on the public site location list / map.
Example 3 — Stakeholder asks "where are we?"
Operator opens the Locations list, exports for the stakeholder.
Documentation guidance
Use this page as the structural definition for the Locations module.
Reading order
Open this page when scoping multi-location sites. Pair with GBP Reference for the integration relationship.
Related reading
- SG-Admin Overview — parent surface.
- Google Business Profile — GBP integration.
Vocabulary cross-reference
- Location record is one physical business location.
- GBP pairing is the configured link between a location and a Google Business Profile listing.
- Special hours are exception entries on the per-day hour calendar.
Maintenance discipline
When Locations changes across releases (new field, new GBP sync rule, new hours model), update this Reference.
When the GBP integration changes its sync cadence or its supported field set, update the GBP pairing section and the troubleshooting entry on stale syncs.
When the relationship with Events changes (new linkage field, new auto-sync rule), update the cross-link in "how this connects to other features".
Governance — locations as structured place-aware records
Locations occupy a structural category that ordinary content cannot. A page describing a venue is editorial; a location record is operational. The platform preserves the distinction deliberately.
A location record holds the source of truth for a physical place — address, hours, contact, services, photos — and other modules pull from it. Events reference it. GBP listings sync to it. Templates display it. Treating a location as "a page about a place" loses the operational meaning; updates to the page would not flow to events, would not sync to GBP, and would not stay consistent across the location-list and per-location pages.
The Locations module exists so the site can administer place-aware records once and have downstream surfaces reflect the change.
When to use Locations vs Pages
Use Locations when:
- The site represents one or more physical places that visitors can find or contact.
- Hours and address matter and may change.
- The site uses GBP and wants the listing to stay in sync with the platform record.
- Events reference venues that correspond to stored physical places.
Use Pages when:
- The "place" is editorial only (a page describing the company's history at a site, for example) and not used for visitor wayfinding.
- No GBP sync is needed.
- No event venue linkage matters.
Module vs dashboard linkage
Locations as a module record differs from dashboard-level business linkage. The module governs the structured location content — address, hours, photos. The dashboard governs the business association (the entity that owns the site) and the local-presence linkage where the platform supports it.
The two work together: dashboard-level business identity gives the site its overall business posture; module-level location records hold the per-place detail.
Site · SG-Admin · Locations · Multi-location view
| Location | City | Hours today | GBP | Last update |
|---|---|---|---|---|
| Manila Main | Manila, PH | 09:00 – 18:00 | Synced | 2026-05-19 |
| Cebu Branch | Cebu, PH | 10:00 – 19:00 | Synced | 2026-05-15 |
| Davao Pop-up | Davao, PH | Closed today | Not paired | 2026-05-21 |
Hours hygiene
Hours are the most-read field on a location record. Two habits keep them trustworthy.
Set holiday hours in advance
Most visitor confusion at a location comes from finding the place closed when the published hours say open. Add upcoming holiday entries as soon as they are known; do not wait for the day. Holiday entries override the regular weekly hours on the affected date.
Treat hours as a recurring review
On a multi-location site, review the hours per location on a regular cadence (monthly or quarterly). Hours drift; locations open earlier or close earlier seasonally; staff capacity changes. A scheduled review prevents the type of stale-hours problem that visitors notice first.
Services per location
The services field per location is for the case where the site offers different services in different places. A single-location site (or a multi-location site where every location offers the same services) does not need per-location service lists; the site-level services are enough.
When per-location services do differ, keep the per-location list short. Long lists are hard to scan and visitors generally only need to know whether a specific service exists at a location.
## Related reading| Topic |
|---|
| SG-Admin |
| Google Business Profile |