World is now on Opti ID! Learn more

Praful Jangid
Apr 12, 2019
  64
(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
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |