Take the community feedback survey now.

Praful Jangid
Apr 12, 2019
  107
(0 votes)

Indexing Block's Content to make it searchable

By default, the content of a block (that is added to ContentArea on a page) is not indexed and therefore you can’t search for the content of that block instance in your site.

So, the content of a page (including block's content) is indexed as normal text under "SearchText$$string". To check if the content from Block is being indexed or not. Go to Episerver CMS, Find -> Overview -> Explore, look for the page you want to confirm. Expand to see all its indexed properties. You can see here that, by default the content of the block is not being indexed.

Let's talk about how to enable it. Here we go....

There are several ways to do that, use any of them as per your requirement.

  1. To allow content of all the instances of a block type to be indexed. Just add an attribute [IndexInContentArea] on your block.
    [IndexInContentAreas]
    public class CopyBlock : SectionBlock

    Tip: If you still not see the content is being indexed. Perform some changes to your page and you will see it worked. It's only to reindex the page.

  2. To exclude content of certain instances of the block, add a bool type property with exact name IndexInContentAreas on your block type.

    public virtual bool IndexInContentAreas { get; set; }

    And set its value to True, so that content of all instances will be indexed by default. To exclude content of any instance, uncheck the checkbox for property IndexInContentAreas (for that instance only).

  3. Using search convention, changing the default behaviour of IContentIndexerConventions.ShouldIndexInContentAreaConvention.

    To index a particular block type, create a class and inherit it with interface IShouldIndexInContentAreaConvention

    public class ShouldIndexInContentAreaConvention : IShouldIndexInContentAreaConvention
    {
           public bool? ShouldIndexInContentArea(IContent content)
           {
           	return content is CopyBlock;
           }
    }
    

     Now create an Initializable module

    [InitializableModule]
    [ModuleDependency(typeof(EPiServer.Find.Cms.Module.IndexingModule))]
    public class SearchConventionInitializationModule : IInitializableModule
    {
            public void Initialize(InitializationEngine context)
            {
                ContentIndexer.Instance.Conventions.ShouldIndexInContentAreaConvention = new ShouldIndexInContentAreaConvention();
            }
    
            public void Uninitialize(InitializationEngine context)
            {
            }
    }
    

    In addition, to control the depth of ContentArea to be indexed, can be controlled by MaxDepthContentAreaConverter (by default all nested ContentArea are indexed)

    public class SearchConventionInitializationModule : IInitializableModule
    {
            private const int MaxDepth = 4;
    
            public void Initialize(InitializationEngine context)
            {
                ContentIndexer.Instance.Conventions.ShouldIndexInContentAreaConvention = new ShouldIndexInContentAreaConvention();
                SearchClient.Instance.Conventions.ForInstancesOf<ContentArea>().ModifyContract(x => x.Converter = new MaxDepthContentAreaConverter(MaxDepth));
            }
    
            public void Uninitialize(InitializationEngine context)
            {
            }
    }

Document reference: https://world.episerver.com/documentation/developer-guides/find/Integration/episerver-cms-7-5-with-updates/Indexing-content-in-a-content-area/

Happy Coding :)

Apr 12, 2019

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025