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 Nergård (MVP)
May 20, 2014
  2356
(3 votes)

EPiServer Search indexing bug

Last week I got a question from a customer why they didn’t get the expected search results. A couple of issues was caused by the search index being corrupt, but they still had a a few pages that wouldn’t show up.

After looking at the actual HTML in the editor and fiddling around a bit I found out that it’s a problem with using bold ,italics and hard line breaks inside a paragraph.

Some examples:

<p><strong>some text</strong></p> here “some text” won’t get indexed.

<p><strong>some text <br /> more</strong> here neither “some text” or “more” get’s indexed.

I’ve reported it as a bug to EPiServer and it’s in the bug list 114609.

May 20, 2014

Comments

Please login to comment.
Latest blogs
ScheduledJob for getting overview of site content usage

In one of my current project which we are going to upgrade from Optimizely 11 I needed to get an overview of the content and which content types we...

Per Nergård (MVP) | Jan 27, 2026

A day in the life of an Optimizely OMVP: Migrating an Optimizely CMS Extension from CMS 12 to CMS 13: A Developer's Guide

With Optimizely CMS 13 now available in preview, extension developers need to understand what changes are required to make their packages compatibl...

Graham Carr | Jan 26, 2026

An “empty” Optimizely CMS 13 (preview) site on .NET 10

Optimizely CMS 13 is currently available as a preview. If you want a clean sandbox on .NET 10, the fastest path today is to scaffold a CMS 12 “empt...

Pär Wissmark | Jan 26, 2026 |

Building AI-Powered Tools with Optimizely Opal - A Step-by-Step Guide

Learn how to build and integrate custom tools with Optimizely Opal using the Opal Tools SDK. This tutorial walks through creating tools, handling...

Michał Mitas | Jan 26, 2026 |