Håkon Nordli
Apr 8, 2016
visibility 3367
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
Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026

Optimizely DXP: Every Supported Culture, One Searchable Page

Quick one for anyone building multi-language sites on Optimizely DXP. I put together a reference tool listing all 806 supported cultures. More...

Adnan Zameer | Jul 10, 2026 |

A day in the life of an Optimizely OMVP: London Meetup 2026

On 2nd July 2026 the Optimizely London Developer Meetup returned to The Lightwell, and the running theme across the evening was less about individu...

Graham Carr | Jul 10, 2026

Optimizely’s Summer ’26 Roadmap: The CMS Is Starting to Look Less Like a Publishing Tool and More Like Marketing Infrastructure

Optimizely’s Summer ’26 Product Roadmap event was not just a list of product updates. At least, that is not the part I found most interesting. The...

Augusto Davalos | Jul 9, 2026

Optimizely Content JS SDK v2.1.0 — What's New and Why It Matters

  v2.1.0 of the Optimizely Content JS SDK and CLI landed on July 7, 2026. This is a substantial release bringing a wave of capabilities for...

Vipin Banka | Jul 8, 2026