Sitecore Module 1.6.1

SearchStax provides a special module that connects Sitecore directly to SearchStax Studio and lets you publish a custom search page immediately.


“Sitecore Plugin” vs. “Sitecore Module”

The Sitecore Plugin connects your Sitecore CMS to SearchStax Solr Cloud for indexing. See, for instance, Sitecore Plugin.

The Sitecore Module (this page) connects your Sitecore CMS to the SearchStax Studio for a customized search experience.


What is the Sitecore Module?

This package is a Sitecore module that Sitecore developers can install to leverage all the search capabilities offered by SearchStax Studio for your client-facing search pages. It contains a Sitecore index connector which can index your Sitecore items using the out-of-the-box Indexing Manager provided by Sitecore. Not only that, but it comes with a functional search page that can be built in minutes instead of weeks of work. With this package your client can focus immediately on improving the real search experience, since that is where the business value is.

First, create a SearchStax Studio App!

You cannot install the Sitecore Module until you have created a SearchStax Studio App.

The App must have suggestions enabled on the Auto-Suggest Tab.

One Sitecore Server per SearchStax Studio App!

To prevent data corruption and/or bad website results, do not connect two different Sitecore Content Management servers to the same SearchStax Studio App.

Install the Sitecore Module

The first step is to contact SearchStax team and ensure you already have a SearchStax Studio account and App created with Solr core configured to deal with your Sitecore. Once you have this you are ready to go.

This is almost a plug-and-play module, thus installing it is as easy as possible.

Below are the supported Sitecore versions, with the links for downloading the Sitecore package:

Sitecore VersionPackageWDP Package
Sitecore 9.0SearchStax package for 9.0WDP Package for 9.0
WDP Package for 9.0 CD
Sitecore 9.0 Update 2SearchStax package for 9.0.2WDP package for 9.0.2
WDP package for 9.0.2 CD
Sitecore 9.1
Sitecore 9.2
SearchStax package for 9.1 and 9.2WDP package for 9.1 and 9.2
WDP package for 9.1 and 9.2 CD
Sitecore 9.3
Sitecore 10.0
Sitecore 10.1
Sitecore 10.2
SearchStax package for 9.3, 10.0, 10.1, 10.2WDP package for 9.3, 10.0, 10,1, 10.2
WDP package for 9.3, 10.0, 10,1, 10.2 CD
Sitecore SXA (All versions)SearchStax package for SXAWDP package for SXA
WDP package for SXA CD

Once you download the package, open the Sitecore Installation Manager:

Use the Choose File option to select the downloaded file and upload it to your Sitecore.

Once the package is uploaded it’s time to properly install it. You can do this by clicking on Next and then on Install.

The installation should take no more than a few minutes. You will know the installation is completed when you see the below pop-up. Go ahead and click on the Configure SearchStax for Sitecore Package button:

Configure the Sitecore Module

The above button will open the list of SearchStax Studio Indexes (SearchStax Studio Apps) associated with your Sitecore project. (You can reach this page whenever you want to change these values from either the Sitecore Control Panel or the Launchpad.)

Begin the process by entering your SearchStax Studio credentials. This makes the Sitecore Module aware of your accounts and the SearchStax Studio Apps that are linked to them.

Choose an Account and an App for Sitecore to use.

Click the Create an Index button. This opens the Sitecore Module Index configuration page. This is where you can configure the search module.

  • Search App Name: The SearchStax Studio App selected in the previous screen.
  • Root Items: From the Content Editor, enter the root nodes of the items you want to add to this index. You may use the (+) button to have more than one root. By default, the module will index every page under /sitecore/content/home/.
  • Read Only Solr Password and Admin Solr Password: These are the “Read-Only API Credentials” and the “Read-Write Search API Credentials” from the Search API tab of the Studio > Navigation Menu > Search App > Settings > Apps Settings screen. You’ll have to scroll down to the bottom of the screen to find them. The User ID is set by the system, but you can set the password (both Read only and Read Write need to be set).
  • Hosted Search Page Password: If you secured the App’s Hosted Search Page with a password, enter it here.

Clicking Save pops up a confirmation dialog box. Sitecore has to be restarted.

This returns you to the list of indexes where you can see the index you just created:

Populate Schema and Rebuild

Once you have installed and configured the Sitecore module, you must run a Populate Schema operation on this new Solr collection to update its schema with the one used by Sitecore. You can find more details about this at This is a common operation that must be executed on every Solr index used in Sitecore and is very easy to perform. Open your Sitecore admin page and click on Control Panel -> Populate Solr Managed Schema.

Select your previously configured core name and then click on Populate.

Once this operation is completed, you should see a success message like this:

Now go back to the Control Panel and click on Indexing Manager. When it opens, select your previously configure core name and click on Rebuild.

Usually, it should only take a few minutes but keep in mind that the time this operation will take is proportional to the number of items you have in your Sitecore. 

Once this operation is completed you should see a success message like this:

This means that your schema is updated and your SearchStax index is ready to receive new indexed items and search queries.

Once the schema is populated and the data is rebuilt, you can start configuring SearchStax Studio, selecting what data you would like to see in Results, and creating a default model. Before creating your Search Page in Sitecore, the following three Steps should be performed in SearchStax Studio:

(You can search SearchStax Studio directly by going to or click on Search Management from within Sitecore as shown below.)

  • Reload schema changes in SearchStax Studio
    • Go to Studio > Navigation Menu > Search App > Settings > Apps Settings > Search API tab.
    • Scroll to the bottom of the screen and click on the Reload Schema button. This syncs schema changes to SearchStax Studio.

  • Configure Result Fields in SearchStax Studio
    • Go to Studio > Navigation Menu > Search App > Search > Results Configuration
    • Select all fields that you would like to be displayed in Result Items. You can map some of the fields to the Result Cards to show them in a special way. Make sure you have at least one field set up.
    • Click on Publish to publish the Results Configuration.
  • Configure Relevance Model for SearchStax Studio
    • Go to Studio > Navigation Menu > Search App > Search > Relevance Modeling
    • Click on “Create a Model” and create a new model named “Default”. If one already exists, you can click on it to edit it.
    • Check “Set as Default” for this model
    • From the Search Fields, select one or more fields that you would like to search on. At least one field should be selected.
    • Click on Publish to publish the Relevance Model.

Create a Search Page

The Sitecore Module comes with a plug-and-play search page template that you can use to create your search page in a few minutes. Use the /sitecore/templates/Feature/SearchStax/SearchPage/SearchStaxPage template to create it.

You just need to publish it to start testing your new search experience:

Computed Fields

The Sitecore Module uses a few computed fields out-of-the-box. These fields improve the search experience of your initial search page, but they can be replaced or removed as your project matures. The module’s computed fields are described in the following sections.

For general information on Sitecore’s computed fields, see


This field contains the title of the result item, based on the Sitecore item DisplayName property. If that is empty, the returned string is its Name property value.

This field is not required by the module to make it work properly. However, it is the field that the module uses as the result template title. If you decide to remove or change, do not forget to change the studio config connector.fields.title property on the /Views/SearchStaxPage/Index.cshtml.


This field contains the result URL. It leverages the native Sitecore MediaManager.GetMediaUrl method for media items to get the item URL. When the item is not a media item, this fields starts by defining the current website context. It uses the indexed item Paths.FullPath property and tries to find a website definition which has the same Database property value and has a RootPath which is a parent item from the current one. Once it finds the current website context, it then leverages the native Sitecore LinkManager.GetItemUrl method to get the item URL.

This field is not required by the module to make it work properly. However, it is the field that is used as the result template clickable URL. If you decide to remove it or change, do not forget to change the studio config connector.fields.url property on the /Views/SearchStaxPage/Index.cshtml.


This field contains a string value that improves the search relevance of the website. It indexes not only the current item text fields, but also the text fields from every data source present on the <indexedRenderings> configuration list.

In order to add new template ids to this list and make them indexable by this computed field, please edit the <indexedRenderings> node children’s values on the App_Config/Modules/SearchStax/SearchStax.Connector.Provider.config file.

This field is not required by the module to make it work properly. You can remove it from your index if you wish.

Adding a Custom Computed Field

What if you would like to add a custom computed field to the configuration? After the SearchStax index has been created, find the index within [site]/App_Config/Modules/SearchStax/SearchStax.Connector.Provider.config, where [site] is the folder of your inetpub/wwwroot/site. In the <fields hint=”raw:AddComputedIndexField”> section, add an entry for the CustomComputedIndexField:

<field fieldName="CustomComputedIndexFieldName" returnType="string">

Bear in mind that computed index fields are expensive and place a load on the CPU. One should minimize their use.

Was this article helpful?