Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    Sign In
    • Home
    • User Guides
    • Locator + Pages

    Locator Upgrade - Microsoft IIS Steps

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    FR French
    IT Italian
    JP Japanese
    DE German
    US English (US)
    ES Spanish
    • Getting Started
      New here Configuration and Connection Guides
    • Academy and Learning Resources
      Learning Resources - Best Practices Academy
    • User Guides
      AI What's New Platform Status and General FAQs Homepage The Dashboard Location Hub Review Management Messages Social Locator + Pages Analytics Directories Mobile App 'Near Me' 360
    • Connecting Tools
      Connection Troubleshooting API
    • Org Settings
      Users Billing API Keys Webhooks
    + More

    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, on a site of plain HTML files and on an ASP.NET site on the .NET Framework, such as one built with ASP.NET MVC 5. It takes five steps, on your web server and in your site's files. They are written for the developer or administrator who maintains the site. 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. For a case a step does not list, ask Uberall.

    What you need

    IIS 10, the IIS of Windows Server 2016 and later. On another version? Ask Uberall before you start. A site on ASP.NET Core cannot use these steps: ask Uberall.

    Administrator access to the server, and access to your site's files and its web.config

    The Uberall Store Finder module for IIS, a zip file: uberall-store-finder-iis-latest.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, and on a site with more than one language, its address in each of them. Each store gets its own address under 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, and data-baseurl, which you remove in step 4
    • 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 five 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 start, 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 1: Turn on ASP.NET for your site

    The module is a small piece of ASP.NET code that IIS runs for every page of your site. So IIS needs ASP.NET 4, even on a site of plain HTML files.

    Find out whether IIS has ASP.NET 4: on the server, open PowerShell as an administrator, and run the command for your Windows:

    • Windows Server: Get-WindowsFeature Web-Asp-Net45. It has it if Install State says Installed. If not, run Install-WindowsFeature Web-Asp-Net45.
    • Windows 10 or 11: Get-WindowsOptionalFeature -Online -FeatureName IIS-ASPNET45. It has it if State says Enabled. If not, run Enable-WindowsOptionalFeature -Online -All -FeatureName IIS-ASPNET45.

    Find out what your site's application pool runs: in IIS Manager, select your site, click Basic Settings, and note its Application pool. Then click Application Pools, and find that pool in the list. If your site is in a folder of its domain, such as https://www.example.com/shop, select that application under the site instead, here and in the steps below.

    • a) Its .NET CLR Version is v4.0 and its Managed Pipeline Mode is Integrated: nothing to change.
    • b) Its .NET CLR Version is No Managed Code: select the pool, click Basic Settings, and choose the .NET CLR version that starts with v4.0. If other sites use the same pool, this changes it for them too.
    • c) Its .NET CLR Version is v2.0, or its Managed Pipeline Mode is Classic: ask Uberall before you go on.

    Step 2: Install the module

    Unzip the file. It has one file in a folder, uberall-store-finder-iis\UberallStoreFinder.cs.

    Find out whether your site is built before it is deployed: look in your site's repository for a .csproj file, and in your site's folder on the server for a PrecompiledApp.config.

    a) Neither: your site's files are deployed as they are

    Put UberallStoreFinder.cs into the App_Code folder of your site's folder, the folder with your site's web.config, such as C:\inetpub\wwwroot\App_Code. Create App_Code if it is not there. ASP.NET compiles it on the site's next visit. If your site's files come from a repository, commit it there too, or the next deployment can remove it.

    b) Your repository has a .csproj file, or the site's folder has a PrecompiledApp.config

    Add UberallStoreFinder.cs to the project, in any folder other than App_Code, such as Uberall\UberallStoreFinder.cs, and deploy as usual. It is compiled with your site's code. It needs the references to System.Web, System.Web.Extensions and System.Configuration that ASP.NET projects have. On a precompiled site, an App_Code folder stops every page with "The directory '/App_Code/' is not allowed because the application is precompiled".

    c) You cannot add it to the project, such as on a precompiled site you have no project for, or in a Visual Basic project

    Compile it on the server. In PowerShell, in the folder with UberallStoreFinder.cs, run:

    & "$env:windir\Microsoft.NET\Framework64\v4.0.30319\csc.exe" /target:library /out:UberallStoreFinder.dll /reference:System.Web.dll /reference:System.Web.Extensions.dll /reference:System.Configuration.dll UberallStoreFinder.cs

    Copy the UberallStoreFinder.dll it makes into the bin folder of your site's folder.

    Step 3: Let your store finder page answer its stores' addresses

    Every store gets an address under your store finder page, such as /store-locator/l/berlin/.... That address has to show your store finder page: the store finder then shows the store.

    Find out what serves your store finder page:

    a) It is a file of your site, such as store-locator\index.html or store-locator.html

    Nothing to add: once it is on, in step 5, the module answers every address under the page with the page. For a folder, the page's file must have one of IIS's own default names: Default.htm, Default.asp, index.htm, index.html, iisstart.htm or default.aspx. Files of your site under the page, such as its images, stay as they are.

    The page also answers at addresses deeper than its folder, and without its folder's slash. So its own links to its styles, scripts and images must start with /, such as /css/site.css, not css/site.css.

    b) Your site's code serves it, such as an ASP.NET MVC controller

    Its route has to take every address under the page. In ASP.NET MVC, add a catch-all to the route, before your other routes:

    routes.MapRoute("StoreLocator", "store-locator/{*rest}",
        new { controller = "StoreLocator", action = "Index" });

    With attribute routing, the same on the action: [Route("store-locator/{*rest}")].

    To check, open your store finder page's address with /l/test after it, such as https://www.example.com/store-locator/l/test. It should show your store finder page, not a 404 error.

    Step 4: Put the store finder on its page

    The module puts your stores into the store finder's div in the page IIS 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 a private browser window. 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

    Add the store finder snippet to the page: to its HTML file, or to the view or template that your site's code makes it from. Replace YOUR_LOCATOR_KEY with your locator key, and the address with your store finder page's full address:

    <div
      id="store-finder-widget"
      data-key="YOUR_LOCATOR_KEY"
      data-widgetoriginurl="https://www.example.com/store-locator"
    ></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. Leave it where it is, and add data-widgetoriginurl with your store finder page's full address, if the div has none.

    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 module 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 module puts the stores inside it. Spaces and line breaks are fine. If the div has anything else inside it, even text, the page is served without its stores.

    If the div has data-baseurl, remove it. With any address in it other than https://locator.uberall.com, the store finder does not take over the stores in the page: it shows them again on the visitor's screen.

    The page must be saved as UTF-8, as most pages are. A page saved in another encoding, with letters such as ü or é in it, is served without its stores.

    The module 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. On a site with more than one language, each language's page has its own snippet: set its language and its own address on it, such as data-language="de" and data-widgetoriginurl="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.

    Step 5: Add your settings

    This step turns the module on, so do it last, with the module from step 2 in place: as long as IIS cannot find the module, these settings make every page of the site fail.

    First, your token. Create a file named uberall.config in your site's folder, next to its web.config. Replace YOUR_LOCATOR_KEY with your locator key, and YOUR_RENDER_TOKEN with your token:

    <appSettings>
      <add key="UberallStoreFinder:Token:YOUR_LOCATOR_KEY" value="YOUR_RENDER_TOKEN" />
    </appSettings>

    The token stays on your server: IIS does not serve .config files, and visitors never see it.

    Find out whether your site's files come from a repository.

    • a) They do not: you edit them on the server. Create uberall.config there.
    • b) They do. Keep uberall.config out of the repository, and create it on the server only. If your deployment removes files on the server that are not in the repository, exclude uberall.config from that.

    Then, your web.config. In IIS Manager, select your site, and click Explore: web.config is in the folder that opens. These are the lines to add:

    <configuration>
      <appSettings file="uberall.config">
        <add key="UberallStoreFinder:Pages" value="/store-locator" />
      </appSettings>
      <system.webServer>
        <modules>
          <add name="UberallStoreFinder" type="Uberall.StoreFinder.StoreFinderModule" />
        </modules>
      </system.webServer>
    </configuration>

    Find out what your web.config has:

    • a) There is none: create it with the lines above.
    • b) It has some of these sections: add each part to the section it already has, and add the sections it does not have. On its <appSettings>, add file="uberall.config".
    • c) Its <appSettings> already has a file or configSource attribute: leave it as it is. Put the UberallStoreFinder:Pages line and the token's line into the file that attribute names, and leave out uberall.config.

    In UberallStoreFinder:Pages, put the address of your store finder page, as it is in the browser, 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, with its language prefix, comma separated, such as /store-locator, /de/filialfinder, /fr/magasins.
    • c) A site in a folder of its domain: with the folder, such as /shop/store-locator.

    Add the module exactly as above. With preCondition="managedHandler" on it, IIS skips it for a page whose address ends in its file name, such as /store-locator.html, and that page arrives without its stores.

    If your site has other applications under it in IIS Manager, such as /blog, keep the module from them: without this, they fail with "Could not load type 'Uberall.StoreFinder.StoreFinderModule'". Put the <modules> part into a <location> of its own, instead of under <system.webServer>:

    <location path="." inheritInChildApplications="false">
      <system.webServer>
        <modules>
          <add name="UberallStoreFinder" type="Uberall.StoreFinder.StoreFinderModule" />
        </modules>
      </system.webServer>
    </location>

    Saving web.config restarts your site, and the module starts on its next visit. ASP.NET reads uberall.config when the site starts: when you change it later, for example with a new token, restart the site's application pool. In IIS Manager, click Application Pools, select the pool, and click Recycle.

    Check

    Open your store finder in a private browser window. Right click, and choose View page source. Search the source for __ubSfSsr. If you find it, and the div has no data-baseurl, 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.

    On a site with more than one language, check the store finder page in each of them.

    What changes on your store finder pages

    On the store finder's pages, the module replaces part of what your page has in its 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.

    A store's page also leaves out your page's links to the store finder page in your other languages (hreflang): they name the store finder page, not the store. The store finder page itself keeps them.

    A store finder page that is a file of your site is compressed by the module, with gzip, for every browser that takes it, rather than by IIS.

    More than one store finder on the site

    Each store finder has its own locator key and its own render token. Add a line for each of them to uberall.config, and each store finder page, in every language, to UberallStoreFinder:Pages:

    <appSettings>
      <add key="UberallStoreFinder:Token:STORES_LOCATOR_KEY" value="STORES_RENDER_TOKEN" />
      <add key="UberallStoreFinder:Token:SHOWROOMS_LOCATOR_KEY" value="SHOWROOMS_RENDER_TOKEN" />
    </appSettings>

    The module takes each page's token by the data-key of its snippet. Then follow steps 3 and 4 for each page.

    If it does not work

    The error texts in the first rows show in a browser on the server itself. Elsewhere, IIS shows a short error page instead.

    What you see What to do
    Every page of the site shows "HTTP Error 500.19", with "This configuration section cannot be used at this path" at the <modules> line IIS has no ASP.NET 4. Turn it on, as in step 1.
    Every page of the site shows "Could not load type 'Uberall.StoreFinder.StoreFinderModule'" IIS does not find the module. Put UberallStoreFinder.cs where step 2 says for your site. In an application under your site, keep the module from it, as at the end of step 5.
    Every page of the site shows "The directory '/App_Code/' is not allowed because the application is precompiled" Your site is precompiled. Remove the App_Code folder, and add the module as in step 2 b) or c).
    A store's page, such as /store-locator/l/berlin/..., answers with a 404 error Check the application pool, as in step 1, and UberallStoreFinder:Pages, as in step 5: the address must be the page's, as it is in the browser, without the domain. If your site's code serves the page, check its route, as in step 3 b).
    The source has no no-render-reason line and no __ubSfSsr The module does not run for the page. Check the application pool, as in step 1, the page file's name, as in step 3 a), UberallStoreFinder:Pages, and that the module has no preCondition, as in step 5. Then see When changes show.
    The source ends with no-render-reason: no token uberall.config has no token for the snippet's data-key, is not next to web.config, or the <appSettings> of web.config has no file="uberall.config". See step 5, then recycle the application pool.
    The source ends with no-render-reason: declined: unauthorised The token is not the one Uberall gave you for this locator key. Paste it again, and recycle the application pool.
    The source ends with no-render-reason: no data-key on the store finder div Add data-key to the snippet, as in step 4.
    The source ends with no-render-reason: no empty store finder div The page IIS sends has no empty store finder div, or no </head>: the div is missing, or has something inside it. Check it as in step 4.
    The source ends with no-render-reason: page is not UTF-8 Save the page as UTF-8.
    The source ends with no-render-reason: request failed Your server cannot reach Uberall, or Uberall took more than 10 seconds to answer. Ask your host to allow outgoing HTTPS to uberall.com. If your server reaches the internet through a proxy, set it in web.config, under <system.net>, <defaultProxy>.
    The source ends with no-render-reason: paused after a failure A call to Uberall failed in the last 30 seconds, so the module waits before the next one. Load the page again in a minute, and see the line above.
    The source has no store-finder-widget at all The snippet is added by a script. Move it into the page, as in step 4 c).
    The source ends with another no-render-reason, or __ubSfSsr is not there Contact Uberall, with that line.

    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, within about 10 seconds, 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.

    When your site gives a store finder page a longer time in caches than an hour, with IIS's client cache setting or ASP.NET's output cache, the module makes it an hour: for browsers, for caches in front of IIS, such as a CDN, and for ASP.NET's output cache. A store finder page that is a file of your site also no longer carries the file's date (Last-Modified) and ETag: with them, and no cache time from your site, browsers keep the page for a share of the file's age, however old its stores get. Nothing tells your caches when your stores change at Uberall, so a change shows once they store the page again. That goes for a change to your own setup too, such as the token or the snippet: to check one at once, add ?check to the page's address, which caches usually keep apart, or recycle the application pool. When the content does not arrive, the module sends Cache-Control: no-store with the page, so a later visit tries again. A page that is not set up yet, with no token, no data-key or no empty store finder div, is cached like any other.

    A cache that sets its own time for your pages, rather than the one IIS sends, may keep them longer, and keep a page without its stores. If yours does, exclude the store finder's addresses, such as /store-locator/*, from it.

    locator iis upgrade

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • FAQ about Self Serve Locator & Pages
    • What is embedded Locator + Pages (Self Serve)?
    • Customizations of Locator + Pages via CSS
    • Locator and Pages attributes
    • Filters for Locator & Pages
     

    Copyright 2026 – uberall.

    Expand