Håkon Nordli
Apr 8, 2016
visibility 3468
star star star star star
(7 votes)

Episerver full-text search module

Episerver full-text search module aka Standard Search Inspector

The last years I've set up and worked with several sites using Episerver full-text search. Episerver Search is like you might already know, a search engine delivered together with Episerver CMS without any extra costs. It is based on Lucene which gives it a powerful foundation.

Several of times I've had issues when customers wanted something extra like facets or want an explanation on how the relevance work.

For me it has been difficult to find good examples, good practices and/or blog posts about the search API. To solve this I've started to develop a module. I hope this can be a module that more people contribute to.

The goal is not to compete with Find. Find is still a better search engine with more functionality, and the search engine I recommend customers. But for different reasons some customers don't want Find.

At the moment the module only have two functions:

  1. A search inspector which shows indexed items as JSON objects. This gives us as developers a lot more control on which data that are indexed.

    blogg image1

  2. A reindexing page. As several of us know, the reindex page is a hidden feature in Episerver which is a bit annoying. To be honest I visit my colleague Svein Aandahls blog post everytime I need the URL to the reindex-page. Sorry Svein, your visit numbers might go down.

    blogg image2

The module is available through Episervers nuget feed, http://nuget.episerver.com/en/OtherPages/Package/?packageId=Knowit.EPiModules.StandardSearchInspector

It is also added to Github, https://github.com/knowit/Knowit.EPiModules.StandardSearchInspector, where anyone may add pull requests. Please be brave and add features, that would be awesome!

Apr 08, 2016

Comments

Apr 8, 2016 03:38 PM

Nice!

K Khan
K Khan Apr 8, 2016 04:08 PM

+1

"Find is still a better search engine with more functionality" will relief the Find Marketing guys :)

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026