A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Per Magne Skuseth
Feb 27, 2015
  12069
(15 votes)

Inspect In Index for EPiServer Find

Have you ever found yourself in the situation where you’ve been wondering if your index content is correct, updated or there at all? I have. Often. So, to save me from having to go to the Find Explore view and search for the content, I created another content view to inspect the index for the currently selected content. So simple, but SO useful!

iii 

The view shows the current content’s raw form in the EPiServer Find index. From the view you may also index, re-index or delete the content from the index. It will show the content for the currently selected language. Works for pages, blocks, media and custom IContent.

Note: Since non-developers are most likely not interested in the view, it will by default only be visible for users that are members of the “CmsAdmins” or  the “SearchAdmins” role.

Want to try it? It’s in the EPiServer NuGet Feed: Install-Package EPiCode.InspectInIndex

Source code and documentation: github.com/BVNetwork/InspectInIndex/

Feb 27, 2015

Comments

Henrik Fransas
Henrik Fransas Feb 27, 2015 12:14 PM

Nice work as always!

Petri Isola
Petri Isola Feb 27, 2015 01:07 PM

Awesome! I am spreading the word here in Finland.

Feb 27, 2015 01:11 PM

Awesome stuff! Straight into my toolbox!

Janne Kuusela Kuusela
Janne Kuusela Kuusela Feb 27, 2015 02:49 PM

Cool and really useful!

K Khan
K Khan Feb 27, 2015 03:17 PM

very helpful indeed, Bundle of Thanks!

Feb 27, 2015 10:21 PM

I must join in on the comment love train. This is sweet! :)

Malik
Malik Dec 23, 2021 10:55 AM

Hi Team,

I tried the solution in Alloy sample site, for few languages it works and for few it gives below error. Any clue to resolve this?

Error:

An unexpected error occurred: RequestError: Unable to load /EPiServer/Find/proxy/MalikAlloy_Models_Pages_StandardPage/_579871c7-6ec0-4a2b-b7b7-bd3c24af776c_da?language_routing=da status: 400

Thanks in Advance!

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Unlock the Power of Unified Search: Introducing Custom Data Management for Optimizely Graph

Bring all your data together in one searchable experience The Challenge: Siloed Data, Fragmented Search Every organisation has data spread across...

Graham Carr | Jan 16, 2026

Alt text is retrieved for images imported from CMP-DAM in Optimizely CMS 12.

Introduction Although image alt text is stored as metadata in CMP/DAM, it is not automatically rendered in browser HTML. This document outlines the...

Deepmala S | Jan 16, 2026

Announcing Stott Security Version 4.0

January 2026 marks the release of Stott Security v4, a significant update to the popular web security add-on for Optimizely CMS 12, with more than...

Mark Stott | Jan 16, 2026

Optimizely Graph Best Practices - Content Modelling and Querying

Introduction With the Mando Group team having worked extensively with Optimizely Graph over the last 12+ months, we have uncovered a number of best...

Jon Williams | Jan 16, 2026