Prepare the main Sitecore content manager for a scaled environment

Once you correctly built the whole Sitecore infrastructure, you may proceed to configure Coveo for Sitecore on your main content management instance (CM1).

Step 1: Configure an additional database search index

Sitecore suggests adding a pub database, as illustrated in Sitecore infrastructure setup. Whether this additional database is called pub or something else (for example, web2), you must add a new index definition for it.

  1. On CM1, open the <SITECORE_INSTANCE_ROOT>\Website\App_Config\Include\Coveo\Coveo.SearchProvider.Custom.config file in a text editor.


    You shouldn’t modify the Coveo.SearchProvider.config file directly, as it may cause unexpected upgrade issues and loss of configuration.

  2. Inside the contentSearch/configuration/indexes element, add another <index> element as the last child by copy-pasting the code block for your Sitecore version.


    You must disable indexing of the pub database on all your additional CMs and CDs. Patch delete the database parameter from your coveoOnPublishEndAsyncPub index update strategy. For Sitecore 9.2 instances and later, configuration patching to disable indexing on CD and non-indexing CM servers is included directly in the SITECORE 9.2+ code block below. This patch relies on the enabling of the indexing sub-role on your main content manager and only on the main content manager. For Sitecore 9.1, you can patch delete the database parameter using a rule-based configuration (see Step 3: Disable indexing on additional CMs and CDs).

    Copy and paste the following content to create the new child of the <indexes> element:

    <index id="Coveo_pub_index" type="Coveo.SearchProvider.ProviderIndex, Coveo.SearchProvider" patch:before = "*[3]">
      <param desc="p_Name">$(id)</param>
      <configuration ref="coveo/defaultIndexConfiguration" />
      <locations hint="list:AddCrawler">
        <crawler name="ContentCrawler" type="Sitecore.ContentSearch.SitecoreItemCrawler, Sitecore.ContentSearch">
        <crawler name="MediaLibraryCrawler" type="Sitecore.ContentSearch.SitecoreItemCrawler, Sitecore.ContentSearch">
          <root>/sitecore/media library/Files</root>
      <strategies hint="list:AddStrategy">
        <strategy ref="contentSearch/indexConfigurations/indexUpdateStrategies/coveoOnPublishEndAsyncPub"/>
        <strategy role:require="ContentDelivery or !Indexing" name="coveoOnPublishEndAsyncPub" type="Sitecore.ContentSearch.Maintenance.Strategies.ManualStrategy, Sitecore.ContentSearch">
          <param desc="database">
            <patch:delete />
            <patch:delete />
      <propertyStore ref="coveo/databasePropertyStore" param1="$(id)"/>
  3. Apply the following changes to the <index> element that you just added.

    1. The id attribute is set to Coveo_pub_index in the copied block. If your additional database isn’t named pub, change the id attribute value to reflect the name of your database (for example, Coveo_web2_index).

    2. The text value of the <database> elements in the copied block is pub. If your additional database isn’t named pub, change the text value to reflect the name of your database (for example, <database>web2</database>).

  4. Add the following <indexConfigurations> element as an immediate child of the <contentSearch> element:

        <coveoOnPublishEndAsyncPub name="coveoOnPublishEndAsyncPub" type="Sitecore.ContentSearch.Maintenance.Strategies.OnPublishEndAsynchronousStrategy, Sitecore.ContentSearch">
          <param desc="database">pub</param>
  5. The text value of the <param> element in the block you just copied is pub. If your additional database isn’t named pub, change the text value to reflect the name of your database (for example, <param desc="database">web2</param>).


    If you make changes to the <coveoOnPublishEndAsyncPub> element (that is, to the element name or its name attribute value), ensure you match these changes in the child <strategy> element(s) of the <index> element you added earlier.

  6. Save your changes.

Step 2: Rebuild the search index for the additional database

Your additional database is now properly configured and can be indexed by Coveo for Sitecore. Use the Coveo Command Center Indexing Manager to rebuild the newly created index.


Your Sitecore items are indexed with clickable URI values matching a hostName value assigned to your content management instance. However, the clickable URI is automatically recomputed whenever a Coveo-powered search interface receives search results from the index to ensure that the intended content delivery instance is hit whenever a website visitor clicks a search result.

Step 3: Configure the UseHostHeaderForRequestURL setting

Under the hood, Coveo for Sitecore performs HTTP requests on its own. To ensure that these internal HTTP requests are targeting the expected endpoint, the aspnet:UseHostHeaderForRequestUrl setting must be set properly (see ASP.NET appSettings Element for details).


The aspnet:UseHostHeaderForRequestUrl setting must be set to true when the Sitecore instance is deployed behind a network load balancer (NLB). Omitting this setting may cause URL-resolving issues.

Follow these steps to configure the setting on the CM1 instance:

  1. Open your web.config file.

  2. Inside configuration/appSettings, add the following element:

    <add key="aspnet:UseHostHeaderForRequestUrl" value="true" />
  3. Save your changes.

Step 4: Configure the farm name on the instance to be scaled

When scaling Sitecore instances, you need to set a Farm name to ensure all the Sitecore instances share the same resources. Setting a Farm name affects the names of the sources, field sets, security provider, and user identities. Instead of assigning them an individual name, you give them the same label. Follow the Assign a farm name to resources guide to configure the CM1 instance.


When choosing a Farm name different from the CM1 host name, you must rebuild your Coveo indexes (see Coveo for Sitecore indexing guide). Some resources, like the sources, need to be rebuilt to apply the name change. Skipping the rebuild would cause naming inconsistencies that would prevent queries and components from reaching the right resources.

What’s next?

Now that you installed Coveo for Sitecore on your first content management instance, you may proceed either to: