A critical vulnerability was discovered in React Server Components (Next.js). Our Systems Remain Fully Protected. Learn More

Per Nergård (MVP)
May 20, 2014
  2310
(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
Jhoose Security Modules v2.6.0 — Added support for Permissions Policy and .NET 10

Version 2.6.0 adds Permissions Policy header support, updates to .NET 10, improved policy management, configurable security settings, and enhanced...

Andrew Markham | Dec 6, 2025 |

Building a 360° Customer Profile With AI: How Opal + Optimizely Unlock Predictive Personalization

Creating truly relevant customer experiences requires more than collecting data—it requires understanding it. Most organizations already have rich...

Sujit Senapati | Dec 4, 2025

Building a Lightweight Optimizely SaaS CMS Solution with 11ty

Modern web development often requires striking a difficult balance between site performance and the flexibility needed by content editors. To addre...

Minesh Shah (Netcel) | Dec 3, 2025

Creating Opal Tools Using The C# SDK

Over the last few months, my colleagues at Netcel and I have partaken in two different challenge events organised by Optimizely and centered around...

Mark Stott | Dec 3, 2025