Search engines and AI assistants often cannot see your store finder. When they visit the page, your stores are not on it yet: they only appear later, on the visitor's screen. So your stores can be missing from search results and from the answers AI assistants give.

After these steps, every store finder page arrives with its stores already on it, with names, addresses and opening hours. Search engines and AI assistants can find each of your stores and show it. Your visitors see the store finder as usual.

It works for a store finder already on your site and for a new one. It takes four steps. Some steps depend on how your site is set up: each of those says how to find out, and what to do in each case.

What you need

TYPO3 10.4, on PHP 7.2 to 7.4. On another TYPO3 version? Ask Uberall before you start.

A TYPO3 backend user with system maintainer rights, or access to your site's Composer setup

The Uberall Store Finder extension, a zip file: uberall_store_finder.zip

Your render token, from Uberall

Your locator key, from Uberall. If the store finder is already on your site, it is the data-key of its snippet:

• <div id="store-finder-widget" data-key="YOUR_LOCATOR_KEY"></div>

Your store finder's address: the page it is on, such as https://www.example.com/store-locator. Each store gets its own address under it

Step 1: Install the extension

Find out how your TYPO3 is installed: look at your project's root folder. If it has a composer.json with typo3/cms-core in it, your TYPO3 is installed with Composer. Otherwise it is a classic installation.

a) Installed with Composer

Unzip the file into a folder of your project, such as packages/uberall_store_finder.

Run, from the project's root:

1. composer config repositories.uberall-store-finder path packages/uberall_store_finder
   composer require uberall/typo3-store-finder
   vendor/bin/typo3 extension:activate uberall_store_finder

If you deploy from a repository, such as Git: commit the folder, composer.json and composer.lock, and deploy as usual.

b) Classic installation

1. In the backend, go to Admin Tools, Extensions.
2. Click the upload icon at the top, choose the zip file and click Upload!.
3. Activate Uberall Store Finder in the list.
4. If you deploy from a repository, such as Git: the next deployment would remove the extension again. Install it on a copy of the site instead, then commit typo3conf/ext/uberall_store_finder and typo3conf/PackageStates.php, and deploy as usual.

Then, either way, go to Admin Tools, Maintenance, and click Flush cache.

Step 2: Add your render token and your store finder's address

Go to Admin Tools, Settings, Extension Configuration, and open uberall_store_finder. Fill in:

• Render token: the token from Uberall. To keep it out of the configuration, see below.
• Store finder pages: the address of your store finder page, without the domain.
  • a) One store finder page: its address, such as /store-locator.
  • b) A store finder page for each language: each of them, comma-separated, such as /store-locator,/de/filialfinder.

Click Save. The token stays on your server. Visitors never see it.

TYPO3 saves these settings in typo3conf/LocalConfiguration.php.

a) That file is not in your repository, or you do not deploy from one: nothing more to do.

b) That file is in your repository: commit the change and deploy as usual. To keep the token out of the repository, leave Render token empty and set it in typo3conf/AdditionalConfiguration.php from an environment variable instead:

• $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['uberall_store_finder']['renderToken'] = getenv('UBERALL_RENDER_TOKEN');

Every address under a store finder page belongs to the store finder: TYPO3 shows the store finder page for it, and the store finder shows the store. Do not put other pages under it: a page with the store finder page as its parent shows the store finder instead.

Step 3: Put the store finder on its page

The extension puts your stores into the store finder's div on the page TYPO3 sends. So the div has to be in that page, not added later by a script.

Find out where your snippet is: open your store finder page in the browser, right click, and choose View page source. Do not use the browser's developer tools: they show the page after scripts have changed it. Search the source for store-finder-widget.

a) The store finder is not on your site yet

Open the store finder page in the Page module and add a content element of the type HTML (under Special elements) with the store finder snippet. Replace YOUR_LOCATOR_KEY with your locator key:

<div id="store-finder-widget" data-key="YOUR_LOCATOR_KEY"></div>
<script src="https://locator.uberall.com/locator-assets/storeFinderWidget-v2.js"></script>

b) You found store-finder-widget in the source

The snippet is in the page already: in a content element, in your page template, or in TypoScript. All of these work. Leave it where it is, and check its settings, as described in If the store finder is already on your site.

c) The store finder shows in the browser, but store-finder-widget is not in the source

A script adds it after the page has loaded, for example a tag manager such as Google Tag Manager. The extension cannot reach it there. Move the snippet into the page:

1. Add it as in a), with the settings it has today.
2. Remove it from the tag manager, or wherever the script adds it, so it is not on the page twice.

Either way, keep the div empty, as above: the extension puts the stores inside it. If the div has anything inside it, even text, the page is served without them.

The extension sends Uberall the div's data-key, data-language, data-countries and data-widgetoriginurl, so the stores in the page always match what the store finder shows. To show the store finder in another language, set it on that page's snippet, such as data-language="de". If your store finder is on more than one page, such as one for each language, also set data-widgetoriginurl on each page's snippet to that page's full address, such as https://www.example.com/de/filialfinder.

If your snippet loads storeFinderWidget-v2-withoutMap.js, the store finder shows no map, and its pages arrive without one too. Nothing to add.

If its addresses have #! in them today, check with Uberall that your store finder is set up without it.

If the store finder is already on your site

After these steps, your store finder pages use only the settings saved at Uberall. What is set on the page itself no longer applies there:

• attributes on the store finder's div, other than data-key, data-language, data-countries and data-widgetoriginurl
• settings your site's scripts pass to UberallStorefinderMount or UberallStorefinderRestart, other than withoutMap

To find them, look in two places:

• The store finder's div, in the page's source: any data- attribute other than the four above.
• Your site's scripts, in the page's source and in your site's JavaScript files: calls to UberallStorefinderMount or UberallStorefinderRestart.

If you find any of these settings, send them to Uberall before you go on, to be saved with your store finder. Until then, leave the page as it is: the store finder keeps working as it does today.

Step 4: Check

Open your store finder in the browser, right click, and choose View page source. Search the source for __ubSfSsr. If you find it, it works.

Then open one of your stores and copy its address into a new tab. The store's page should open, with the store's name as the page title.

What changes on your store finder pages

On the store finder's pages, the extension replaces part of what TYPO3 puts in the page's head with what Uberall sends for each store:

• the title, the canonical link and the description
• the Open Graph tags, with the twitter: tags that go with them
• the structured data (application/ld+json)

It only replaces what Uberall sends. What Uberall does not send for a page stays as your site has it. For example, if no description is set up at Uberall for your store finder's main page, the page keeps the description from its page properties.

If it does not work

When the store finder content does not arrive

The store finder keeps working in every case. If the content does not arrive, because your server cannot connect to Uberall, the connection takes too long or it returns an error, the page loads without it, and the store finder appears on the visitor's screen as usual.

When changes show

A change at Uberall, to your stores or to your store finder's settings, takes a few minutes to show on these pages.

TYPO3's own page cache does not delay it: the extension adds the stores after it. A cache in front of TYPO3 does, such as Varnish or a CDN: each store finder page in that cache keeps the content it had when it was cached, until the cache stores it again. The extension sends Cache-Control: no-cache with a page without its stores, so a cache that respects it does not keep that page, and a later visit tries again. A cache that does not respect it, such as a static file cache like the staticfilecache extension, may keep it anyway: exclude the store finder's addresses, such as /store-locator/*, from it.