Locator & Local Pages Guide

This guide explains how to set up and manage the Store Locator & Local Pages: a searchable store locator and individual location pages that you add to your own website. The location data shown comes straight from your PinMeTo account, so it stays consistent with what you publish to networks like Google and Apple. To manage that underlying location information, see the Listings guide.

Are you a developer? For technical documentation, read our Locator Quick-Start Guide 🔗

Table of Contents

Section 1: What You Get

• Locator
• Local Pages

Section 2: Setting Up the Locator & Local Pages

• Overview of the Steps
• Adding the Widgets to Your Website
• Google Maps API Key Requirements

Section 3: Configuring the Appearance

• Map
• Information
• Cover Image on Local Pages
• Design

Section 4: Custom Fields — Subheader & Page Footer

• What They Are and When to Use Them
• Step 1: Publish the Custom Field via the Public API
• Step 2: Select the Custom Field in Locator & Local Pages Settings

FAQ

Section 1: What You Get

The product has two parts that work together: the Locator (a searchable widget) and the Local Pages (a dedicated page for each location).

Locator

A search-enabled widget that helps visitors find your locations. It includes:

• Search by address or city — visitors type a location and see nearby results ranked by distance.
• Adjustable search radius — filter results by distance, in kilometers or miles.
• Interactive map — locations shown as pins on a Google Maps view.
• List and map views — switch between a list of results and a full map. On desktop, visitors see the list and map side by side; on mobile, the layout stacks vertically.
• Subheader — a short custom line of text shown below each location name (also shown on the Local Page). See Section 4.

Local Pages

A dedicated page for each of your locations, with:

• Opening hours — regular and special hours displayed clearly.
• Contact information — phone, email, and physical address.
• About — the location's long description, shown as an "About" section.
• Get Directions — a link that opens Google Maps with the location pre-filled.
• Static map — a map image showing the location's position.
• Cover image — the Google cover image for the location (optional, see Section 3).
• Subheader — a short custom line of text shown below the location name, the same one that appears in the Locator. See Section 4.
• Page footer — a longer block of custom text at the bottom of the page, above the map (Local Pages only). See Section 4.

Each location page has its own URL (for example, yoursite.com/locations/store-name), which makes it easy to share and link to a specific location.

Section 2: Setting Up the Locator & Local Pages

Back to top

Setting up the locator involves both PinMeTo (handled by an Owner) and a few changes to your website (handled by your webmaster or IT team). The steps below are a summary. Your technical team should follow the full Locator Quick-Start Guide 🔗 for the exact snippets and server configuration.

Overview of the Steps

1. Contact PinMeTo. Reach out to your Customer Success Manager or support to request the locator and access to its settings.
2. Choose where the locator will live. Decide with your webmaster which path on your website will hold the locator and local pages (for example, /locations).
3. Add the widgets to your website. Your webmaster or IT team adds the widget snippets to your site (see below).
4. Configure server URL rewrites. Because each location has its own URL, your server must be set up to serve your page for all paths under the location directory. This is a standard URL rewrite rule, with examples available for Nginx, Apache, Vercel, Netlify, and others in the Server Configuration guide 🔗. Without it, visitors who open a shared location link would see a "Page Not Found" error.
5. Customize the appearance. Once the locator and local pages are working, configure the look and feel to match your brand (see Section 3).

Adding the Widgets to Your Website

This step is for your webmaster or IT team. The widgets are lightweight and run independently from your site's existing code. They are hosted by PinMeTo on public.pinmeto.com, so there is nothing to download or maintain.

The data-account-id and data-app-id used in the snippets are found in Account Settings > Public API. Full snippets and all available options are in the Public API 🔗.

Google Maps API Key Requirements

The map in the locator uses Google Maps, so you need a Google Maps API key from the Google Cloud Console. Request this from your IT team or webmaster.

The two widgets use different Google Maps APIs, so the key you configure must have both enabled in the Google Cloud Console:

• Maps JavaScript API — used by the locator widget for the interactive map.
• Maps Static API — used by the local page widget for the static map image.

A key with only one of these enabled will work for one widget but not the other. The most common issue after rotating a key is that Maps Static API was not re-enabled.

A few more requirements for the key:

• If the key has HTTP referrer restrictions, your website's domain (including any subdomains) must be in the allowed referrers list. The same applies to any IP or application restrictions.
• The Google Cloud project that owns the key must have billing enabled.

You add the key in the locator settings under Map (see Section 3). For steps to verify a key is working, see the Locator Quick-Start Guide 🔗.

Section 3: Configuring the Appearance

Back to top

Once the widgets are live on your website, you configure how they look in Account Settings > Locator & Local Pages. Use the Preview panel on the right to see the Locator and Local Pages views as you make changes, then click Save. You can also use Reset to default to undo your styling.

The preview is a visual guide. Details may differ from the live version on your website, and changes can take a few minutes to sync.

Map

• Show map — check this to display the interactive map in the locator.
• Map API key (from Google Cloud Console) — paste the Google Maps API key here. See Google Maps API Key Requirements above.
• Map ID (optional) — add a Map ID if you have configured custom map styling in your Google Cloud Console.

Information

• Widget language — the language used for the widget's labels and buttons.
• Subheader (optional) — a short line of text shown below each location name. This is populated from a string-type custom field (see Section 4).
• Page Footer (optional) — a block of text shown at the bottom of each Local Page, above the map. This is also populated from a string-type custom field (see Section 4).

Cover Image on Local Pages

• Show Google cover image — check this to display the location's Google cover image at the top of its Local Page. To manage the cover images themselves, see the Listings guide.

Design

Set these to match your website's branding:

• Font family
• Background color
• Text color
• Accent color — used for buttons and links.
• Accent text color — the text color on accent-colored buttons.
• Pin color — the color of the location pins on the map.

Styling applies to all text in the locator and local pages. It is not possible to style individual fields separately.

Section 4: Custom Fields — Subheader & Page Footer

Back to top

You can display your own custom field information in the locator and local pages, using two placements: a subheader below the location name, and a page footer at the bottom of the Local Page. Only string-type (text) custom fields can be used for this.

Custom fields are set up on your PinMeTo account first. If you don't have the custom field you need, contact support to create it. For background on custom fields and the supported data types, see the Listings guide.

What They Are and When to Use Them

Subheader. Best for short information about the location that matters to your business but isn't sent to the networks as a standard data field. Because space is limited, keep it short. Examples: "Flagship store", "Warehouse", "Appointments only", "Self-service", or "HQ".

Page footer. Best for longer text such as descriptions, FAQs, or similar blocks of content, since it doesn't have the same space limitation as the subheader.

The custom field you select is applied to all locations in your locator. Each location shows its own value for that field. Locations where the field is empty will simply not show a subheader or footer.

Step 1: Publish the Custom Field via the Public API

The custom field must be made public before it can appear in the locator. This step can be done by an Owner.

1. Open Account Settings.
2. Go to Public API.
3. Find the app connected to your Locator & Local Pages.
4. At the bottom of the app, use the Custom field (make public) dropdown to select the custom field you want to use as a subheader or page footer. You can add more than one custom field to the same app.
5. Click Save.

Important:

• For the Locator & Local Pages, only string-type custom fields can be used as a subheader or page footer. For other uses of the Public API, any custom field type is allowed.
• If you have more than one Public API app, each app has its own list of published custom fields. Make sure the field is published to the app that your Locator & Local Pages uses.

For more on the Public API and how to set up app access, see our API guide.

Step 2: Select the Custom Field in Locator & Local Pages Settings

Once the field is published, choose where it appears. This step can also be done by an Owner.

1. Go to Account Settings > Locator & Local Pages.
2. In the Information section, open the Subheader or Page Footer dropdown and select one of the custom fields you made public in Step 1.
3. Click Save.

Important:

• Only string-type custom fields appear in these dropdowns.
• You can set only one custom field as the subheader (and one as the page footer). The field you choose applies to all locations.
• Changes to these settings can take a few minutes to sync before they appear on your website.

FAQ

Q: Why can't I see the custom field I want in the subheader or page footer dropdown?

A: Two things to check. First, only text (string) fields appear here. Fields that store other types (boolean TRUE/FALSE values, open hours, and so on) are not available. Second, the field must be published to the Public API app used by your locator. Go back to Step 1 and confirm it has been added.

Q: Can I show more than one custom field in the subheader?

A: No. You can set only one custom field as the subheader. The field you select is shown for all locations in your Locator & Local Pages.

Q: Some locations show a subheader and others don't. Why?

A: The custom field is probably empty for those locations. Make sure every location has a value set for the field. You can set the value via the API, or manually at the bottom of the location's details page in Listings.

Q: I saved my settings but my changes aren't showing yet.

A: Updates can take a few minutes to reach the locator. Wait 10 to 15 minutes, then hard-refresh the locator page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac).
If it still isn't showing, confirm that the test location's field isn't empty. If you have updated a custom field, make sure that the field appears in the Public API app's custom fields list (Step 1), and that it is selected in your Locator & Local Pages settings (Step 2). If everything looks correct, contact support.

Q: I changed the information in a custom field, but the locator still shows the old value. Why?

A: Updates take some time to be reflected in the Locator & Local Pages. If it hasn't updated after a day or so, contact support.

Q: Is there a risk of exposing private data through custom fields?

A: Only the fields you explicitly add to the Public API app are visible in the Locator & Local Pages. It is your responsibility to make sure the custom fields you publish don't contain any sensitive or personal data.

Q: Can I style the custom field text separately?

A: No. You can change the font and text colors for all text in the Locator & Local Pages from the settings page, but you can't style individual fields on their own.

Q: I have multiple Public API apps. Can I set different custom fields for each?

A: Yes. Each Public API app has its own list of published custom fields, and fields published in one app aren't available through another. If you use the Locator & Local Pages, make sure the fields you want as subheader or page footer are published to the app that the locator uses.

Keywords

store locator, local pages, location pages, custom fields, subheader, page footer, public API, Google Maps API key, store finder, location search

Updated on: 16/07/2026