Sigma Store Locator - WordPress Plugin

Guide to Setting Up and Using Sigma Store Locator

Sigma Store Locator is not just for dropping a map onto a WordPress page. Its job is broader: bring addresses, contact details, business hours, categories, location search, and map styling into one clear workflow so visitors can quickly find the nearest location and understand how to get there.

This guide walks through the practical path after installation: what to check before turning it on, how to prepare a Google Maps API key, where to place the shortcode, how to configure the display, how to add stores, categories, photos, and business hours, how to verify the result on the site, and what to do if the map, search, or geolocation do not behave as expected.

This material is written for a site owner, WordPress administrator, or developer who inherits an already installed plugin and needs to turn it into a working store locator. So the focus here is less on marketing copy and more on practical logic: input data, settings, output, verification, and troubleshooting.

What a WordPress Store Locator Is Actually Good For

A store locator is useful when visitors are not looking for a generic contact page, but for a specific physical location: a store, showroom, service center, restaurant, clinic, pickup point, partner office, or dealer network. A basic map with a single marker handles this poorly because it does not help people choose the nearest address, filter locations by category, or compare details.

Sigma Store Locator is built around three parts. First is the location database in the admin panel: name, address, city, ZIP code, phone number, email, website, coordinates, category, marker, and business hours. Second are the map and listing settings: Google Maps type, zoom level, starting point, radius, controls, number of items, and the visibility of distance, filters, and the list itself. Third is page output through a shortcode that you can place in Elementor, on a regular WordPress page, or in the block editor.

This approach is especially useful when you have more than one address and need to maintain them regularly. With only a few locations, the locator saves visitors time. With many locations, it also reduces admin overhead: addresses can be grouped by category, coordinate status can be checked, entries can be edited from a shared list, and if the relevant feature is enabled, data can be synced through Google Sheets or transferred via CSV.

When a Searchable Map Really Makes Sense

There are several cases where Sigma Store Locator makes more sense than a standard contact block:

• The company has several branches in one city, and visitors need to choose the closest one by neighborhood or ZIP code.
• The chain operates across multiple regions, so filtering by category, distance, and keywords matters.
• You need to show business hours, phone number, website, and location photos next to the map instead of hiding everything on separate pages.
• The marketing or operations team updates addresses often, and maintaining a static map by hand becomes impractical.
• The site has a landing page such as "Where to Buy," "Find a Store," "Find a Dealer," or "Pickup Locations."

If the site has only one office, one restaurant, or one workshop, a full store locator may be overkill. In that case, a contact block, a standard embedded map, and a clear directions button are enough. The plugin really shines when users need to choose between multiple locations.

How Sigma Store Locator Differs From a General Map

The main difference is the data structure. In a generic map setup, the marker often lives separately from the business information: the phone number sits in page text, business hours are in another block, and category data may not be stored anywhere at all. In Sigma Store Locator, the store record becomes the unit of control. That keeps things organized: if the address or hours change, the administrator edits a specific location instead of hunting for a marker in code or in a third-party builder.

The second difference is user search. Visitors can search by address, city, ZIP code, or keyword, and with geolocation enabled, they can start from their current location. For a store network, that matters more than a decorative map. People arrive intending to find the nearest place quickly, not just to confirm that the company has multiple branches.

Who Sigma Store Locator Fits Best, and When Another Solution May Be Better

This plugin is a good fit for sites where the map is part of the user journey. That could be a dealer page, a showroom directory, a service center catalog, a restaurant map, a pickup locations page, or an office listing. If visitors need to do more than just see an address - if they need to filter locations, choose a category, check business hours, and open directions - then the locator becomes a real working tool.

For the administrator, two things matter most: a clear admin panel and predictable data maintenance. The official documentation shows separate sections for settings, categories, adding a store, and listing all stores. That is a sensible structure for a WordPress plugin: first configure global settings, then create categories, then add locations, and only after that place the shortcode on a page.

Who the Plugin Usually Works Well For

• Retail chains that need to show stores, salons, showrooms, or pickup locations.
• Franchise and dealer networks where location category, region, and partner contact details matter.
• Service companies that need to display offices, workshops, repair centers, or drop-off points.
• Restaurants and local services where visitors choose the nearest location based on area and business hours.
• Marketing teams that need a manageable "where to buy" section without constant developer involvement.

When to Be More Careful

Sigma Store Locator depends on accurate addresses, coordinates, and a functioning mapping service. If the site is not ready to prepare a Google Maps API key, configure key restrictions, and verify the domain, rollout may take longer than expected. If the organization does not want to use Google Maps on a public page, you should confirm up front whether the intended setup supports another map engine. In the official materials currently available for Sigma Store Locator, the focus is clearly on Google Maps.

The plugin can also be excessive for a site with a single address, or for a directory that needs separate SEO pages for each branch with long descriptions, reviews, directions, and local offers. In Sigma Store Locator, the main user flow revolves around the map, search, and location list. If you need a full branch directory with separate publishing logic, compare it with solutions built around dedicated location pages.

Rule of thumb: if users need to choose a location on a map, Sigma Store Locator makes sense. If they need to read a long branch profile as a standalone page, first make sure the store card and listing format are enough for your use case.

What to Check Before Installation and Initial Setup

Before installation, it helps to prepare more than just the plugin ZIP file. Most store locator issues do not come from the installation itself, but from the next step: the map does not load, geolocation does not request permission, the address resolves inaccurately, the page breaks after script optimization, or the administrator adds locations without coordinates.

Start with a simple checklist: the site should run over HTTPS, WordPress should give you an administrator role, the theme should render a page with a wide enough content area, and the site should not be using aggressive JavaScript optimization without exclusions. Browser geolocation usually requires a secure context, so you should not expect consistent automatic location detection on a test domain running over HTTP.

Google Maps API Key and Access Restrictions

The official Sigma Store Locator documentation shows a Google API Key field in the settings section. This key is required to load and run Google Maps on the page. It is best to prepare it before you start adding stores, because that makes it easier to test the map, address search, coordinate autofill, and the public page layout right away.

For a public site, the key should not be left unrestricted. A practical minimum is to restrict it by HTTP referrers, including the live site domain and the staging domain if you are working on a test copy. If the key is used in the client-side map, do not apply IP restrictions the way you would for a server key. Google specifically notes that client-side Maps JavaScript API services require a restriction model suited to browser requests.

After creating the key, verify three things:

1. Maps JavaScript API is enabled in the Google Cloud project.
2. Billing and quotas are configured so the map does not show a dark overlay or a key-related error.
3. The key restrictions include the actual domain where the locator page is opened.

Store Data and Address Discipline

A good locator starts with a clean address table. Before installation, gather at least the basics: location name, full address, city, region, ZIP code, phone number, email, website, category, and business hours. If you have exact latitude and longitude, save them separately. If you do not have coordinates, Sigma Store Locator can auto-fill them through address lookup, but the official guide specifically notes that the location finder works with saved Google Maps data, and any missing details still need to be added manually.

Do not mix a marketing name for the location with the actual address. For example, "Downtown Showroom" works well in the list, but geocoding is more reliable when you also have the full address with city and ZIP code. The more precise the source string, the lower the risk that the marker lands in the wrong neighborhood or in a different city with a similar name.

Cache, Script Optimization, and a Test Page

Maps often depend on external JavaScript files, requests to Google, and the load order on the page. If the site uses script combining, deferred loading, or minification, first create a test page without complex content blocks, place the shortcode there, and test the locator with optimizations turned off. Once the baseline works, enable caching and optimization one rule at a time so you can quickly isolate conflicts.

For the test page, it is convenient to use a draft or a non-indexed private page. The key is to test not just the admin panel, but the public-facing page as a normal visitor would see it: in incognito mode, at mobile width, with a geolocation permission request, and with several search phrases.

Installation, Activation, and the First Path to the Settings

The official guide describes installation through the standard WordPress screen: the administrator opens Plugins, chooses Add New Plugin, uploads the ZIP file, clicks Install Now, and then Activate Plugin. This is the standard path for a commercial plugin that does not come from the public WordPress.org directory.

After activation, a Store Locator section appears in the left-hand WordPress menu. The documentation points to WP Dashboard > Store Locator > Settings > License as the initial path to the settings. This guide does not cover purchase flow, key retrieval, or license workarounds. The important thing is the practical logic: until service activation is complete, some settings may be unavailable, so the first goal is to get the plugin into a state where the general settings page opens normally.

A Quick Check Right After Activation

Do not jump straight into creating dozens of locations. First make sure the plugin is visible and working properly in the admin panel:

• Sigma Store Locator appears as active in the Plugins list.
• A Store Locator or Sigma Store Locator menu item appears in the left-hand WordPress menu.
• The settings section opens without a white screen or JavaScript errors in the browser console.
• A shortcode copy button or similar element described in the documentation is available at the top of the settings page.
• After adding a test store, you can open the All Stores list and see the record in the table.

This check may seem basic, but it saves time. If something is already broken at this level, there is no point in tuning the map design or styles yet. First resolve the plugin, theme, or permission conflict.

Where to Get the Shortcode and Where to Place It

The Sigma Store Locator documentation states that the shortcode is available in the top-right corner of the settings page: the Use Shortcode button copies it to the clipboard. From there, there are two main ways to display it.

In Elementor, use the shortcode widget: place the widget in the desired part of the page, paste the copied shortcode, and publish the page. In the WordPress block editor, use the Shortcode block. The official WordPress documentation confirms that this block is meant for inserting shortcodes and is listed in the Widgets category; you can also insert it with the /shortcode command.

Always test the output on the published page, not only inside the editor. Page builders sometimes render shortcodes differently in preview mode than they do on the live page. For a locator, real conditions matter: whether Google Maps scripts load, whether the map is visible inside the theme container, whether search works properly, and whether there are console errors.

Core Settings: Map, Search, Styling, and List Behavior

After installation, the main working area is Store Locator / Settings. The documentation divides settings into General Settings and Support, and within General Settings it shows the tabs General, Display, Style, and Advanced. That is a practical flow: first make sure the map works technically, then configure how it is displayed, then align the style with the site design, and only after that touch advanced parameters.

General: Key, Starting Logic, and Baseline Behavior

In the General tab, the first step is adding the Google API Key. After saving, open the test page with the shortcode. If the map does not appear, do not immediately change styles or templates. First check the browser console, the domain restrictions on the key, whether Maps JavaScript API is enabled, and whether billing is active in the Google Cloud project. Errors such as missing key, billing not enabled, or unauthorized referrer are Google Maps setup issues, not locator design issues.

If the map loads, move on to the starting area. For sites with locations in a single city, it makes sense to center the map on that city with a moderate zoom level. For a nationwide chain, a broader starting view may be better, or you can use search as the primary entry point. Choose the default radius so that the first result does not feel empty. A radius that is too small can make it look like there are no locations even when they are only slightly farther away.

Display: What the User Should See

In the display settings, decide what should be visible immediately and what should only appear after a location is selected. For most "find a store" pages, a solid starting configuration looks like this:

• The map and location list are visible together, so users can search both visually and by text.
• Search by address, city, ZIP code, or keyword is available above the map or next to the list.
• Distance is shown when geolocation is enabled or when the user enters an address.
• Categories are visible only if they genuinely help users choose a type of location, such as store, service center, partner, or pickup point.
• The number of items on the page does not overload the mobile screen.

Do not enable every available element just because you can. If all locations share the same category, a category filter only adds noise. If the site has only five addresses, an overly complex filter panel may feel heavier than the map itself.

Style: Match the Site Without Breaking the Theme

The official product page mentions list and grid variations, customizable layouts, light, dark, and branded map themes, as well as support for Snazzy Maps styles. In real projects, it is better to move from simple to complex. First make sure the structure is clear: the map is readable, the list does not get pushed below the first screen, and the location card shows the fields that matter. Only then start adjusting colors and spacing.

If the site theme already has a strong design system, do not try to make the locator feel like a completely separate visual island. Choose a calm map style, category markers, and button colors that do not clash with the theme's existing buttons and forms. For a branded page, one or two accent colors, a readable list, and strong contrast for the selected location state are usually enough.

Advanced: Turn It On Only After Baseline Testing

Advanced settings are worth touching only after the test page is already working. If Sigma Store Locator includes data caching, asynchronous loading, lazy output, or other optimization modes, enable them one at a time and test the public page after each change. On sites with cache plugins and script optimizers, conflicts often show up as "the map is blank," "search does not respond," or "geolocation only works after a refresh."

Quick summary: first make the map work technically, then shape the results layout, then style it, and only then optimize. Doing this in reverse makes troubleshooting harder.

How to Add Stores, Categories, and Accurate Coordinates

The most important part of a locator is not the look of the map, but the quality of the records behind it. Sigma Store Locator provides separate sections for categories, adding a store, and the master list. If you start entering addresses without categories or naming rules, the locator can quickly turn into a messy list with inconsistent phone formats, incomplete addresses, and unclear markers.

Categories: When You Need Them and How Not to Overcomplicate Filters

The categories section is located at WP Dashboard > Sigma Store Locator > Category. The documentation shows the fields Name, Slug, Description, and Marker Icon URL. Categories are useful only when users genuinely need to distinguish between location types, such as retail store, service center, dealer, pickup point, or showroom. If categories reflect internal business structure but do not help visitors make a choice, it is better not to expose them as a public filter.

For markers, use a simple principle: the color or icon should quickly explain the difference. Do not create a separate marker for every city or owner if visitors do not make decisions based on that distinction. The more marker types you introduce, the harder the legend becomes and the greater the risk that the map turns decorative instead of useful.

Adding a Store Through Location Finder

The add-store section is located at WP Dashboard > Sigma Store Locator > Add Store. The official documentation highlights Location Finder as a key element: the administrator searches for an address, clicks find, and the plugin fills in the location data. To fine-tune the position, you can click on the map or drag the marker.

Fill out each store as a complete profile. The name should make sense to a person, such as "Service Center on Main Street," not an internal branch code. The address should be complete. The phone number and email should belong to that location unless the chain uses a single central contact center. The website can be the main site or a local branch page if locations have separate pages.

Even if Location Finder finds the address, still verify the coordinates. On the map, place the marker not just on the street, but on the actual entrance, shopping center, or building wing if that matters to visitors. The documentation specifically notes that missing information must be completed manually. This is especially important for malls, industrial zones, campuses, and addresses where multiple organizations share the same building.

Business Hours and Open Status

The store card includes Operating Hours. You can use the Open All button for the full week or set days manually. For visitors, business hours are often more important than a decorative photo: if someone is choosing the nearest store, they want to know whether it is open now, when it closes, and whether the weekend schedule is different.

Check business hours not only at the individual record level. If the chain has seasonal changes, holiday exceptions, or different schedules by region, decide in advance who owns the accuracy of that data. A locator with outdated hours creates more problems than having no locator at all, because users make decisions based on incorrect information.

All Stores and Coordinate Status

The All Stores section helps you control the locations you have created. The documentation says the list shows the name, location status, categories, and creation date, and if latitude and longitude are missing, the location status becomes unavailable. That is an important signal to review before publishing. A record without coordinates may look complete in the admin panel, but it will not behave correctly on the map.

Before launching the page, review all locations:

• Make sure there are no records without coordinates or with unavailable status.
• Make sure all addresses follow the same format.
• Check that categories and markers are assigned correctly.
• Verify that phone numbers and websites are present where visitors actually need them.
• Remove any test locations created during setup from the live output.

Photos, Google Sheets, and Data Transfer

The official Sigma Store Locator page highlights several capabilities that matter in real use: photos for each location, Google Sheets integration, CSV import and export, and settings backup and restore. You may not need all of them on day one, but they determine how easy the locator will be to maintain a few months later.

Store Photos: When They Actually Help

Location photos are useful when visitors need to recognize the place: the storefront, entrance, display window, pickup counter, or showroom interior. For restaurants, salons, and retail stores, that can reduce uncertainty. For offices and service centers, a single clear photo of the entrance or building is usually enough.

Do not upload random attractive images that do not help users find the location. If someone is arriving at the address, they need a visual cue. A good rule is this: the photo should answer the question, "How do I know I am in the right place?" If the image only answers, "What does the brand look like when presented nicely?" then it may not belong in the locator card.

Google Sheets: When Syncing Is Worth It

On the official page, Google Sheets integration is described as a way to manage and sync store locations directly from a spreadsheet, as well as import, export, and back up data through CSV. This is useful when addresses are maintained not by one WordPress administrator but by a team: regional managers update the sheet, a content manager checks the format, and the site receives more structured data.

But spreadsheets require access discipline. Google Drive lets you assign view, comment, and edit permissions. For a store locator, it is better not to grant edit access to everyone. A typo in an address, a deleted row, or a changed column header can lead to a bad import. Before syncing, lock down the column template and assign someone responsible for final review.

CSV, Backups, and Staging

CSV is useful for bulk rollout and migration. If you already have addresses in a CRM, ERP, or spreadsheet, it is easier to normalize them to a template and import them than to create every location by hand. Backup and Restore solves a different problem: you have configured the map, filters, list, and visual layout on a staging site, and now you want to move that configuration to production or save it before experimentation.

Do not test a bulk import on the live page without a backup. First test 3 to 5 rows: one standard store, one location with an unusual address, one categorized location, one location with a custom marker, and one with special business hours. If every field maps correctly and the public page shows what you expect, then import the rest of the dataset.

Placing the Locator on a Page: Elementor, the Block Editor, and the Theme

The shortcode is the most flexible way to output the locator, but it is also where theme issues often become visible. The map needs enough width and height, the list needs to fit next to or below the map, and the page's parent containers must not clip search suggestions or Google Maps controls.

A Page Built with Elementor

In Elementor, give the locator its own section. Do not place the map in a narrow column next to a long block of text if you have many locations. A locator works better in a wide area: page heading, short instruction, search block, and the map with the list. If you need supporting content around it, place that below the locator: FAQ, tips, or support contact details.

After inserting the shortcode, test the page at three widths: desktop, tablet, and mobile. On a phone, the list and the map should not compete with each other. They should appear in a clear order. If the map takes up too much space before the results, reduce the map height or move some filters higher up.

A Page in the WordPress Block Editor

In Gutenberg, insert the Shortcode block, add the locator code, and publish the page. If you need to scope styles, you can wrap the block in a Group block and assign it an additional CSS class from the Advanced panel. That is safer than editing theme files or relying on the plugin's internal classes.

Here is a small CSS enhancement that does not depend on Sigma Store Locator's internal classes and only affects your page container:

.store-locator-page {
  max-width: 1180px;
  margin: 0 auto;
  padding: 24px 16px;
}

.store-locator-page iframe,
.store-locator-page .wp-block-shortcode {
  width: 100%;
}

@media (max-width: 640px) {
  .store-locator-page {
    padding: 16px 12px;
  }
}

Where to use it: add the store-locator-page class to the page group or container in the editor, and place the CSS in the theme settings, a child theme, or a safe custom CSS tool. The validation is simple: the locator should stay inside the container, avoid sticking to the edges of the screen, and not break other pages. Rollback is just as simple: remove the class from the group or remove this CSS block.

Testing with the Theme and Cache

After publishing, test the page in incognito mode. If the map is visible to the administrator but not to a guest, the issue is often cache, deferred script loading, or different permissions for external requests. At this stage, do not start changing store addresses. First make sure the page loads scripts correctly and is not blocking requests to Google Maps.

If the site uses cookie consent or blocks external maps until consent is given, test the flow before and after consent. Users should understand why the map is not loaded and how to enable it. Otherwise, the "find a store" page will look broken even though it is technically behaving according to the site's privacy policy.

Practical Example: A "Where to Buy" Page for a Showroom Network

Let us look at a concrete use case. Imagine a furniture brand with several showrooms and partner locations. The goal is to build a "Where to Buy" page where visitors enter a city or allow geolocation, see the nearest locations, filter them by type, and open a card with the phone number, website, business hours, and a photo of the entrance.

Goal

Create a page where visitors can understand in one or two actions which location is closest and whether it is open. For the business, the goal is not to show a map for its own sake, but to reduce "Where are you located?" calls and send people to the right showroom.

Preparation

Before setup, create an address table. It should include these fields: name, location type, full address, city, ZIP code, phone number, website, business hours, photo URL, and an internal note for the administrator. Separately, verify the Google Maps API key and the test page in WordPress. In Sigma Store Locator, create the categories "Showroom," "Partner," and "Service" in advance. Choose clear markers for each category.

Setup Steps

1. Open Store Locator > Settings, add the Google API Key, and save the settings.
2. In the display section, enable search by address, city, ZIP code, or keyword.
3. Set the default radius so that in a typical city the user sees several relevant locations instead of an empty result.
4. Create location categories and assign markers to them.
5. Use Add Store to add the first test location, find the address through Location Finder, and manually verify the coordinates.
6. Add the phone number, website, business hours, and a photo of the entrance.
7. Open All Stores and confirm that the coordinate status is available and the category is assigned.
8. Copy the shortcode through Use Shortcode and place it on the "Where to Buy" page.
9. Publish the page and test it as a guest.

Validating the Result

Validation should be scenario-based, not just visual. Enter a city where a location exists. Then enter an area where none exists. Allow geolocation and check whether the result order changes. Open a store card and verify the phone number, website, business hours, photo, category, and marker. On mobile, make sure the search field is not pushed below the map and that the list is easy to scroll.

If everything works, add the remaining locations in batches. After each batch, review All Stores and look for records without coordinates. For large networks, it is worth assigning a separate data quality check: one person imports the data, another opens the public page and verifies 5 to 10 random locations.

A Detail People Often Miss

Not all addresses resolve equally well automatically. If a showroom is inside a mall, near multiple entrances, or in a building with several wings, the automatic coordinates may be technically correct but still inconvenient for visitors. Sigma Store Locator lets you refine the marker position on the map. Use that for locations where the entrance does not match the center of the building.

How to Check the Quality of the Result Before Publishing

A locator should only be considered ready after you have tested it on the public-facing site. In the admin panel, everything may look filled in, but the user-facing page depends on the map, theme, container, cache, external requests, browser geolocation permissions, and address accuracy.

Functional Test

Run through five quick checks:

1. Open the page as a guest and confirm that the map loads without a dark overlay, warnings, or an empty container.
2. Enter a city or ZIP code where a location exists and verify that the list updates without reloading the page if AJAX suggestions are enabled.
3. Allow geolocation and confirm that the nearest locations appear in a logical order.
4. Select a category and verify that the markers and list show the correct type of locations.
5. Open a store card and check the address, phone number, website, business hours, and photo.

Data Review

Open the full store list and sort records by category. Look for empty values, inconsistent phone number formats, duplicate addresses, test records, and locations without coordinates. If the list contains location status unavailable, fix those entries before publishing the page.

For addresses with automatically generated coordinates, check at least a sample. You do not need to open every single location if there are hundreds, but you do need to test different cities, different categories, and unusual addresses. If the sample reveals frequent geocoding errors, it is better to go back to the source address table and normalize the format.

Performance and Privacy Review

A page with a map is usually heavier than a standard text page. Check that the locator is not loading on every page of the site if it is only needed on one. If you have lazy loading or data caching options, enable them carefully and re-test both search and the map.

If the site's policy requires consent for external maps, provide a clear fallback message. Users should not see an empty rectangle. Give a short explanation that the map will load after consent to external services, and keep the address list available if your configuration allows it.

Useful Improvements Without Editing Plugin Files

There is no need to edit Sigma Store Locator files directly. Those changes disappear on update and make maintenance harder. It is safer to use the plugin settings, custom CSS, theme settings, a child theme, or a standard code snippets tool. For a store locator, the most useful improvements are usually not complex hacks, but small, careful enhancements around the output.

Limit the Width and Create a Comfortable Reading Area

If the theme stretches content full width, the map can become too wide and the list harder to read. Add a page container and confirm that the locator looks like part of the site. The CSS example above solves exactly that container problem and does not interfere with the plugin's internal classes.

Add a Short Intro Above the Locator

A short instruction above the map helps users. For example: "Enter a city or allow location access to see the nearest showrooms." This does not require code, and it reduces confusion when users do not understand why the browser is asking for geolocation permission.

Create an Internal Test Page

For large networks, it is useful to keep a private page with the same shortcode but without marketing design around it. On that page, the administrator can quickly verify the map after a CSV import, plugin update, or API key change. If the issue appears on the internal page, it is technical. If it appears only on the public page, look for a conflict with the design, builder, or extra content blocks.

Limitations and Practical Tradeoffs to Know Up Front

Sigma Store Locator is strong at one thing: providing a manageable store locator with a map, search, categories, location data, and a shortcode. But every solution of this type has boundaries. It is better to understand them before launch so you do not promise the business something the plugin was never meant to do.

It Is Not a CRM or the Company's Master Data System

The plugin stores and displays store data on the website. It does not replace an internal system for managing branches, contracts, employees, inventory, or partner statuses. If addresses come from a CRM, it is better to define a single source of truth and sync data regularly rather than editing multiple versions manually.

Automatic Coordinates Still Need Verification

Auto-filled latitude and longitude save time, but they do not remove the need for review. Google Maps may resolve an address approximately, especially if the input string is incomplete or ambiguous. For important locations, verify the marker manually. For bulk imports, do spot checks.

Geolocation Depends on the Browser and User Consent

The plugin may offer automatic location detection, but the browser asks the visitor for permission. If the user declines, blocks the request, or opens the site in a context where geolocation is unavailable, the workflow should still work through manual search by address, city, ZIP code, or keyword.

Performance Depends on the Number of Locations and Page Settings

The official page mentions smart caching, lightweight map scripts, async loading, and request minimization. That is useful, but it does not mean you can safely place thousands of locations, dozens of photos, and a heavy theme on a single page without testing. If the network is large, enable optimization modes, use categories, limit the number of items, and test the page as a regular guest would see it.

Common Sigma Store Locator Issues and How to Diagnose Them

Store locator problems almost always fall into four groups: Google Maps API, store data, shortcode output, and site optimization. Do not start troubleshooting by reinstalling the plugin. It is much faster to work from the symptom toward the likely cause.

The Map Does Not Load or Shows a Dark Overlay

Symptom: instead of the map, you see an empty block, a darkened map, a Google Maps error message, or a development watermark.

Possible cause: the Google API Key is missing, Maps JavaScript API is not enabled, billing is not configured, the key is restricted to the wrong domain, or the wrong restriction type is being used.

What to check: open the browser console, look for Google Maps errors, check the API key field in Sigma Store Locator settings, and then review the Google Cloud project. Google notes that many map errors are tied to the key, billing, and access restrictions.

How to fix it: enable the required API, add the site domain to HTTP referrers, save the key in the settings, clear the page cache, and open the page in incognito mode. If the map does not recover immediately after changing restrictions, wait a bit and clear the cache again.

Search Does Not Find the Address or Returns the Wrong City

Symptom: the user enters a city or street, but the result is empty, the marker lands in another country, or the search chooses a similar-sounding place.

Possible cause: the address is incomplete, the map settings do not reflect the correct regional logic, Google interprets the name ambiguously, or the store coordinates were entered incorrectly.

What to check: open the store record and review the full address, city, ZIP code, and coordinates. Manually look up the address in Google Maps and compare the point. If similar place names exist in different countries, include the region and ZIP code.

How to fix it: normalize the address table, refine coordinates manually on the map, use a more complete address format, and review the radius settings. If the issue affects many records, fix the source data first rather than the locator styles.

Geolocation Does Not Ask for Permission

Symptom: the location-detection button is visible, but the browser never asks for permission, or the feature does not change the results.

Possible cause: the site is not running over HTTPS, the user previously blocked geolocation, the browser is blocking the request, or the feature is disabled in settings.

What to check: open the page over HTTPS, check the permission icon in the browser address bar, try incognito mode and a different browser. Make sure manual search still works, because geolocation should not be the only way to use the locator.

How to fix it: enable HTTPS, reset site permissions, review the locator settings, and leave a clear prompt for the user. If a visitor declined geolocation, you cannot force it back on, so manual search should remain the main fallback.

The Location Exists in the Admin Panel but Does Not Appear on the Map

Symptom: the store was created, but it does not appear in results or disappears after filtering.

Possible cause: there is no latitude and longitude, the location status is unavailable, the category does not match the filter, the location is outside the selected radius, or the record is saved as draft/inactive if your configuration supports that status.

What to check: open All Stores and review the location status. Then open the store itself and check the coordinates, category, address, and business hours. Temporarily expand the search radius and disable the category filter.

How to fix it: fill in coordinates through Location Finder or manually, assign the correct category, save the record, and clear the cache. If import is involved, verify the CSV or spreadsheet column mapping.

The Shortcode Appears as Text or Does Not Render the Locator

Symptom: the page shows the shortcode itself, an empty block, or no locator after publishing.

Possible cause: the shortcode was inserted into the wrong block, the builder escapes it as plain text, the plugin is not active, or cache is serving an older version of the page.

What to check: insert the shortcode into the standard Shortcode block or the Elementor shortcode widget. Open the page publicly, clear the cache, and confirm that Sigma Store Locator is active.

How to fix it: use the built-in block or widget, copy the shortcode again from the plugin settings, save the page, and clear the cache. If the problem appears only in one builder, test the output on a regular WordPress test page.

The Map Breaks After Optimization Is Enabled

Symptom: the map worked before caching was enabled, but after script minification or deferred loading, search stops responding, the map becomes blank, or buttons stop working.

Possible cause: the optimizer changed the JavaScript load order, combined external Google Maps scripts, or deferred a file that needed to be available earlier.

What to check: temporarily disable JavaScript minification and deferred loading for the locator page. If everything starts working again, the issue is not with addresses or the plugin, but with the optimization rules.

How to fix it: add the locator page or related scripts to the cache plugin exclusions, clear the site cache and CDN cache, and run the test again. If you are not sure which files to exclude, start by excluding the entire page and narrow the rule gradually.

When Sigma Store Locator Is the Right Choice

Sigma Store Locator is worth using if you need a managed store locator on WordPress: several or many locations, a Google Maps map, search by address or ZIP code, categories, contact details, business hours, photos, shortcode output, and control over the visual presentation. It is especially well suited to "Where to Buy," "Find a Store," "Find a Service Center," and "Pickup Locations" pages.

Before launch, verify three things: whether the Google Maps API key is ready, whether you have a clean address table, and whether the team understands who will keep the data updated after publication. The plugin itself handles locator display and management, but the accuracy of the result depends on the quality of the addresses, coordinates, categories, and page testing.

If, after reviewing everything, you decide the product fits your use case, you can move to the download section and download the installation package for a test site. The safe rollout order is simple: first use staging or a draft page, then add 3 to 5 test stores, then verify the map, search, geolocation, and cache behavior, and only after that import the full address list.

The main selection criterion is straightforward: visitors should be able to find the right location faster than they could through a standard contact page. If Sigma Store Locator helps them spot the nearest store, understand the business hours, open the contact details, and avoid getting lost on the map, then the plugin is doing its job.