Multi-site Management - Bloomreach Experience - Open Source CMS

Multi-site Management

What is multi-site?

A multi-site is also called a multiple-version site. You have a multiple-version site if your site has different versions that have the same structure and similar product catalog for different regions, languages, or brands. For example, if you have a site that has a version for English and another version for French, then you have a multi-site.

As a merchandiser, you can manage multiple versions of your site in the Bloomreach Dashboard. You accomplish your tasks in the same way as for single-version sites, but with a few choices that single sites don't have. These choices let you propagate your merchandising changes across all site versions or a set of versions. You keep the flexibility of overwriting changes at the site-specific level. Before we go any further, let's define some basic terms that will help you understand multi-site management in the Bloomreach dashboard.

Account: used to define the master account. All individual sites and site groups roll under this account.

Site group: used to define a group of sites under the global account. For example, let's say Homeoasis has 3 site groups: Canada, US and Switzerland. Under Canada, they have homeoasis_ca_fr (Homeoasis's Canadian site in French)  and homeoasis_ca_en (Homeoasis's Canadian site in English). In this example, Canada would be considered a site group.

Individual site: used to define an individual site under a site group. In the above example, homeoasis_ca_fr and homeoasis_ca_en are considered individual sites.

Multi-site dropdown

Who may have multi-site support in the Bloomreach dashboard?

  • Large brands who may have multiple sites or domains for each sub-brand. Merchandisers want to be able to view data for each site individually, or view data across all sites globally.  Therefore, they support individual and global views of different domains or subdomains (e.g. homeoasis.com, shop.homeoasis.com, homesbyhomeoasis.com)

  • A regional retailer with a core UK site and several smaller country or language sites (eg: French, German, etc...). Merchandisers want to have a global and individual view of the country sites, but may want to keep the UK site data separate. Merchandisers need the ability to:

    • Support individual site-only views with a combination of global and individual site views (eg: I want to see homeoasis.co.uk separately, but have a global+individual view of homeoasis.fr and homeoasis.de)

    • Support individual and global views of URLs with the same domain but different folders or paths (eg: .com/france or .com/language=german)

    • Support individual and global views of URLs with the same domain but different TLDs (eg: homeoasis.co.uk vs homeoasis.fr)

  • Large brands with several micro-sites across different regions in Europe, who want to group these sites together and view data accordingly (eg: Group A (Site 1, Site 2 Site 3), Group B (Site 4, Site 5)).

  • Brands that have multiple product catalogs 

What are some examples of how Bloomreach supports multi-site management?

Let's take a look at some example scenarios. You can use these scenarios to make merchandising changes that go beyond these scenarios.

Multi-site: Blacklisting a product across a set or all versions of your site

If your site has different versions that have the same structure and similar product catalog for different regions, languages, or brands, we call this "Multi-site". For example, if you have a site that has a version for English and another version for French, then you have a multi-site.

As a merchandiser, you can manage multiple versions of your site in the Bloomreach Dashboard. You accomplish your tasks in the same way as for single-version sites, but with a few choices that single sites don't have. These choices let you propagate your merchandising changes across all site versions or a set of versions. You keep the flexibility of overwriting changes at the site-specific level.

Let's take a look at some example scenarios. You can use these scenarios to make merchandising changes that go beyond these scenarios.

Blacklist rules

Some sites offer merchandise that they don't necessarily want to show for particular search queries. Merchandisers can create blacklist rules to exclude these products from search results for specific queries.

Blacklist rules come in two forms: a search term rule and a global rule. A search term rule affects only search results for specific queries. An alternative to a search term rule is a global rule, which affects all search results on the entire site, regardless of the search query.

Create a global blacklist rule

Molly is a merchandiser at Shoe-In, a retail site that sells shoes through many versions of the Shoe-In site. The site has different versions for languages as well as for major product lines. Molly wants to globally blacklist a shoe called Purple Spots from all search results. She wants this blacklist rule to apply to all versions of the Shoe-In site.

She starts by selecting the global Shoe-In site from the dropdown list in the upper right corner of the Bloomreach Dashboard. The global site is at the top of the list.

Select multi-site

She opens the Ranking Configuration page.

Add Rule dropdown

She clicks the Add Rule button and selects Global Search Ranking Rule, then continues creating her blacklist rule the same way as for a single-version site. When she's done, her new global search blacklist rule applies to all versions of the Shoe-In site. 

Boost a product on a set of sites

Ezra is a digital merchandiser at Benjamin Office, a retail site for office supplies. He wants to boost the product, Very Shiny All-Purpose Surface Cleaner, on two versions of the Benjamin Office site. These two versions are in a group called group-1.

He starts by selecting group-1 from the from the dropdown list in the upper right corner of the Bloomreach Dashboard.

Ezra opens the Ranking page, which is the same starting point that single-version sites use: Configurations → Settings  Ranking Configurations. He clicks the Add Rule button and proceeds the same way as for a single version site with a few exceptions:

  • He can check the Influence marker in the Product Grid view to confirm that he's making changing to the site or group that he wants.
  • He can select a site from the Site Context dropdown list when he previews how his rule affects a specific site within the group of versions (group-1).

Influence Option

Search box

If you have a long list of site versions or groups of site version, then you might find it easier to find the site or group with the search box rather than scrolling through the list.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?