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
  2318
(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
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025