Many of today’s Sitecore implementations contain lots and lots of items. In many cases the items are stored in buckets and the editors are therefore totally dependent on finding what they are looking for by using the search functionality in Sitecore. When entering the search in Experience Editor the editors may become a bit overwhelmed with information since the default is to search for everything. Normally the editor could start filtering and then search for whatever is needed. Continue reading Customize default search in Sitecore experience editor
Sitecore’s media library does a good job of keeping the media that you want to use on your site, but the amount of media in a large site may become hard to navigate. The editors will then rely on search to find what they are looking for. Wouldn’t it be nice to be able to search for the contents of the images instead of the metadata? Continue reading Integrate Microsoft AI in Sitecore media library
In the official documentation you can read that Sitecore will choose index based on the RootPath in the crawler and based on the placing in the web.config.
Basically if you create an index that indexes everything under /sitecore/content/home/products you will need to get that index defined before for example the master index in the web.config otherwise your new index will not be considered at all. But what does actually happen here? Continue reading How does Sitecore ContentSearch determine which index to use