Store locators and find-a-store maps

A store locator can load maps from outside your site

A store locator can keep shop addresses in WordPress while loading map scripts and tiles from an outside service. Some plugins use Google Maps, Mapbox, or OpenStreetMap; others embed a named locator platform. A current-location search may ask for browser permission, but that prompt alone does not show where the coordinates are sent. Map-tile plugins without a store search have a separate page. This table describes the setups below; your settings can change which requests run.

Based on plugin documentation, not tests of your site. Your settings can change what is sent. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group store locators

We compare store records, outside map requests, geocoding features, and browser-location controls in the named setups. Store records in WordPress do not mean map requests stay there. Loading a script or tile, obtaining browser coordinates, and sending coordinates to a service are different steps. The sources below do not establish every location-data recipient. Consent timing has not been tested, and vendor data retention has not been assessed.

How a find-a-store search reaches a map service

Store list in WordPress; maps from outside services

WP Store Locator, Agile Store Locator, and Locatoraid can store locations in WordPress while loading maps from outside services. The WP Store Locator setup below requests OpenStreetMap tiles; Agile and Locatoraid load Google Maps scripts. Geocoding can also involve outside services, depending on the setup. A browser-location prompt does not by itself prove an onward transfer of precise coordinates. The host column covers documented browser requests only.

A named store-locator platform

LocateStore, Store Locator Widgets, and Storemapper load a locator from their own hosts. That can be an iframe or a widget script, sometimes with Google Maps as well. A script or iframe host is a visitor request to that platform. It is not by itself proof of every geocode or geolocation endpoint the platform uses.

Before consent

Consent timing is not tested here. A consent placeholder or the browser location prompt is not a test of your site. The Before consent column is not a scan finding. The site scan linked below checks for third-party requests on your pages; it does not access your WordPress database.

Store locator plugins

No paid placement. Plugins with a WordPress store list appear first, then named locator platforms, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented outside browser hostsHow long data is keptBefore consentLinksSource
Agile Store Locator

This row covers Agile Store Locator when Google Maps is connected. Store records can stay in WordPress. Visitor pages load the Google Maps JavaScript API from maps.googleapis.com, including Places. A current-location control can run on the map. Consent timing is not tested here.

Store list in WordPress; uses outside map servicesmaps.googleapis.comNot assessedNot tested
  • None
Locatoraid

This row covers Locatoraid with Google Maps. Locations are stored in WordPress and geocoded through Google. Visitor pages load maps.googleapis.com. Store records in WordPress do not keep map or geocode requests on the shop server. Consent timing is not tested here.

Store list in WordPress; uses outside map servicesmaps.googleapis.comNot assessedNot tested
  • None
WP Store Locator

This row covers WP Store Locator when the OpenStreetMap engine is selected. Store records stay in WordPress. Default OSM tiles load from tile.openstreetmap.org. A current-position search can use the browser geolocation prompt. Google Maps, Mapbox, and Stadia Maps are other engines and send tiles or geocodes to those services instead. A consent placeholder can delay the map. Consent timing is not tested here.

Store list in WordPress; uses outside map servicestile.openstreetmap.orgNot assessedNot tested
  • None
LocateStore

This row covers LocateStore. The plugin embeds an iframe from locatestore.com and allows geolocation on that frame. Store data is managed in Google Sheets and plotted with Mapbox on that host. Consent timing is not tested here.

Connected to a named store-locator platformlocatestore.comNot assessedNot tested
  • None
Store Locator Widgets

This row covers Store Locator Widgets when Google Maps is selected. Visitor pages load widget scripts from cdn.storelocatorwidgets.com and the Google Maps JavaScript API from maps.googleapis.com. Mapbox is another mapping option on the same widget host. Automatic geolocation can run when the locator loads. Consent timing is not tested here.

Connected to a named store-locator platformcdn.storelocatorwidgets.com, maps.googleapis.comNot assessedNot tested
  • None
Storemapper

This row covers Storemapper. Visitor pages load a widget script from www.storemapper.co. That script host is not by itself a geolocation or geocode endpoint. The listing describes a Google geocoder; a Google host is not cited in the plugin source here. Consent timing is not tested here.

Connected to a named store-locator platformwww.storemapper.coNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named store-locator setups, not requests measured on your site. Store records in WordPress can still be paired with outside map tiles, geocoders, or a locator platform. The host column covers documented visitor browser requests, not every server geocode, and a script host does not by itself establish a geolocation or geocode endpoint. Other page requests are not covered. Map-tile plugins without a store search have a separate page. Plugins marked Not reviewed have not been assessed. Consent timing has not been tested, and vendor data retention has not been assessed. The linked site scan checks for third-party browser requests; it does not access your WordPress database or verify server-to-server geocoding.

Documentation snapshot: Oct 6, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-store-locator-privacy