Location-Specific Content vs Global Content
Overview
Marketplace content can be global or location-specific.
Location-specific experiences are driven by a single Location document. Global pages can still surface location data through selected sections and modules.
Location-specific content
Location detail pages
A location detail page is designed to represent one physical location.
Common characteristics:
- A single Location document is the primary data source.
- The layout renders a predefined module structure.
- Hours, address details, department information, and other operational data come from the Location and connected Place records.
Global content
Content pages with location sections
A global content page can include location-driven sections, such as:
- A Locations section that shows selected locations as cards
- A Reviews section that can be configured to show reviews for all locations or only selected locations
On these pages, the page content is still authored as content blocks, and the location data is pulled into specific sections.
Other location-driven controls
Form selector visibility
A Location can be shown or hidden in specific form selectors without changing whether it has a public location page.
Labels and text overrides
Per-location label overrides allow specific text strings to be customized for that location. These changes apply only where that Location is used.
Inventory filtering
Location-based inventory filtering typically depends on identifier matching. This can power filters without needing content page configuration.
Practical guidance
- Use location detail pages when you want a dedicated page for each store or service center.
- Use global pages when you want one page that highlights multiple locations using location sections.
- Treat form selector visibility as a separate control from public page visibility.