If you run a multilingual WordPress site with WPML, your store locator should switch language with the rest of your content. The official Storepoint plugin handles that automatically: your WordPress store locator switches to match each visitor's WPML language. One block. One dashboard. Every language.
This guide covers the full setup, from installing the plugin to translating your locator phrases.
Before You Start
You'll need:
- A WordPress site with WPML installed and at least two languages configured
- A Storepoint account on the Pro plan or higher (multiple languages are a Pro feature)
- The official Storepoint Store Locator plugin for WordPress (free, from wordpress.org)
If you're new to Storepoint, follow the Quick Start Guide first to set up your account, add a few locations, and configure a map provider. Come back here when you're ready to make the locator multilingual.
Start your free trial See WordPress store locator
Step 1: Install the Storepoint Plugin
In your WordPress admin, go to Plugins > Add New and search for Storepoint. Install and activate the Storepoint Store Locator plugin.
After activation, go to Settings > Storepoint and paste your Public Locator Token. You'll find your token on the Embed page in your Storepoint dashboard.
The plugin connects to your Storepoint account once and uses that connection for every locator block on your site.
If you currently use the embed snippet inside a Custom HTML block or a page builder, the plugin still works alongside it. The plugin's WPML auto-detection only applies to the Storepoint block and shortcode it provides, not to manually-pasted embed code. To use WPML auto-detection, switch to the block. WordPress install guide.
Step 2: Add Languages in Your Storepoint Dashboard
Open Phrases in your Storepoint dashboard. From the language dropdown, select + Add New Language and pick the language you want to add.
Add one language for each WPML language on your site. If WPML serves English, French, and German, add French and German to Storepoint (English is your default and doesn't need to be added).
Step 3: Translate Your Phrases
For each language you added, you'll see a table of every translatable string in your locator: search placeholder, "Get Directions", days of the week, error messages, and so on.
Translate each one in the right column. You can translate:
- UI text: search box placeholder, "Get Directions" button, "Back to results", days of the week, error messages, "no results" copy
- Filter group names: your tag group labels like "Store Type" or "Services"
- Tag names: individual tags like "Authorized Dealer" → "Revendeur Agréé" or "Vertragshändler"
- Custom field labels: labels for any custom field buttons you've added like "Book Now" or "View Menu"
If your locator has a lot of text, prioritize the search placeholder, the "Get Directions" button, your filter labels, and your tag names. Those are the pieces customers interact with most. You can always come back and translate the rest later.
Click Save Settings when you're done with each language tab.
Step 4: Add the Storepoint Block to Your WordPress Page
In the WordPress block editor, open the page where you want the locator. Click the + button, search for Storepoint, and add the Storepoint Store Locator block.
In the block sidebar settings, set Language to Auto.
That's it. WPML serves the page in the visitor's language and the locator follows along. A French visitor lands on /fr/find-a-store/, gets the page and the locator both in French. Same for German, Spanish, or any other language you've added.
You only need one Storepoint block regardless of how many languages WPML manages. No need to embed a separate block per language or per WPML translation of the page.
Using the Shortcode (Classic Editor, Elementor, Divi)
If you're not on the Gutenberg block editor, the Storepoint plugin also exposes a shortcode that supports the same auto-detection:
[storepoint language="auto"]
Drop this into a Classic Editor page, an Elementor HTML widget, a Divi text module, or anywhere else that accepts shortcodes. The language="auto" attribute triggers the same WPML detection as the block.
To filter the locator by tags as well, combine attributes:
[storepoint language="auto" tags="dealer,premium"]
This shows only locations tagged with dealer or premium, in the visitor's WPML language.
Translating Filters and Tags
If your locator uses filter dropdowns and tags, translate both. The filter group label ("Filter by Store Type") and the individual tags ("Premium Dealer", "Open Sundays", "Pickup Available") need their own translations to make sense across languages.
Tag translations live in the same Phrases dashboard, alongside UI strings. Translate each tag once and it applies everywhere: filter dropdown, location card, custom marker rules.
For example, an "Authorized Dealer" tag might become:
- French: Revendeur Agréé
- German: Vertragshändler
- Spanish: Distribuidor Autorizado
When a French visitor uses the filter, they see "Revendeur Agréé" instead of the English original. The underlying tag stays the same in your data so analytics and exports stay clean.
Polylang Works the Same Way
Same setup. The plugin auto-detects Polylang's active language, so add languages in Storepoint, translate phrases, and use the block (or shortcode) with Language: Auto.
With neither WPML nor Polylang installed, the plugin falls back to your WordPress site's default language. Single-language WordPress sites in non-English locales pick up the right language too.
Page Content Stays in WPML
The Storepoint plugin handles the locator's UI. Page content around it (your page title, intro paragraph, headings, footer) stays in WPML's hands. Use the standard WPML workflow: duplicate the page, translate the surrounding content, and the Storepoint block renders the locator in the matching language automatically.
Common Questions
Do I need to set up the Storepoint block on every WPML translation of my page?
No. Once the block is on the original page and WPML duplicates the page for translation, the block carries over. WPML's "Translation Editor" treats the block as a shared component, so the locator stays in place across every language version of the page.
What happens if I add a new language to WPML later?
Add the matching language in your Storepoint Phrases dashboard and translate your phrases. The locator picks up the new language automatically. No code changes needed.
Can I preview a specific language without changing my browser?
Yes. Add ?sp_lang=fr (or any language code) to your page URL to preview that language in the locator. Useful for QA-ing translations before going live.
Does this work with WooCommerce Multilingual?
Yes. WooCommerce Multilingual is built on WPML, so the same auto-detection works. Your store locator on a WooCommerce product page or category will display in the active WPML language.
Will the locator translate location names and addresses?
Location names and addresses stay the same across languages. Street addresses don't usually need translation. If you need different content per region, create separate location entries and filter by tag.
What happens if a visitor lands on a language I haven't translated yet?
The locator falls back to your default language (English in most cases). Visitors still get a fully working locator while you finish translations in the dashboard.
Can I use a different language for a specific block on a specific page?
Yes. In the Storepoint block settings, change Language from Auto to a specific language (fr, de, es, etc.). That block will always render in that language regardless of WPML's active language. Useful for pages that have a fixed locale.
Does any of this slow down my WordPress site?
No measurable impact. The locator widget loads asynchronously from our CDN after WordPress finishes rendering.
Troubleshooting
The locator shows English even on my French WPML pages.
Three things to check:
- The Storepoint block's Language setting is set to Auto (not a fixed language).
- You've added French to your Storepoint Phrases dashboard with at least the search placeholder translated.
- WPML flips the page language correctly. Add
?sp_lang=frto the URL to confirm Storepoint can render French. If that works, the issue is WPML's language switch, not Storepoint.
My filter labels aren't translating.
Filter group names and tag labels live in the same Phrases dashboard but in their own sections. Scroll past the UI strings to find the filter and tag rows for each language tab.
WPML translates the page but the Storepoint block disappears.
This is usually a WPML translation editor setting. In WPML > Settings, make sure the Storepoint block is set to "Copy" in the Translation Editor's block-level settings, not "Translate". The block self-translates, so WPML doesn't need to extract its content.
Still stuck?
Email [email protected] with your site URL and a description of what's happening. We'll help sort it out, usually within a few hours.
Learn More
- WordPress install guide: full setup walkthrough for the Storepoint plugin
- Multilingual store locator: language setup overview, not WordPress-specific
- Filters & Tags: setting up the categories you'll translate
- Custom Fields: per-location buttons whose labels you can translate
- Storepoint for WordPress: platform overview and feature list