Per Nergård (MVP)
+2
May 20, 2014
visibility 2723
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |