Per Nergård (MVP)
+1
May 20, 2014
visibility 2643
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
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |