Instance · Locator
Locations Introduction
Last updated 1 November 2026
One place in your Locator, with address, map position, hours, contacts, media and FAQs.
A location is one place in your Locator: a store, a clinic, a branch or an office. Each location holds its address and map position, opening hours, contact details, social links, images, FAQs and search settings. Your website reads locations to show a map and a store finder.
Where to find locations
In the admin, open Locator and choose Locations. From the list you can add a location, open one to edit it, and import or export locations as CSV.
The tabs of a location
| Tab | What you set |
|---|---|
| Content | Name, slug, descriptions and category |
| Address | The address and its map position |
| Contact Details | Phone, email and other contact details |
| Social Media | Social links |
| Open Hours | Opening times for each day of the week |
| Media and Gallery | Images and files |
| FAQs | Questions and answers for this location |
| Metadata, Open Graph, Sitemap, Schema | How the location page appears in search and when shared |
| Custom Fields, System Fields | Your own fields and the configurable dropdowns |
The address field suggests addresses as you type. It uses the Google Maps key set in the CRM integrations.
From code
The Locator API manages locations at /locator/api/v2/locations, with full create, read, update and delete. Updates use PUT, not PATCH. Custom-field values are sent as custom_field.<name>.
Note
The docs instance has no locations, so none was read. The fields come from the Locator module reference in the Insites Logic Engine.
Common mistakes
- No Google Maps key. The address search does not work until the key is set.
- Using PATCH on the API. Locator updates use PUT.
- Typing opening hours into the description. Use Open Hours, so your site can show them in a standard way.