2026 Search & Navigation release notes

  • Updated

Follow this article to receive email notifications when new Search & Navigation packages are available for 2026. Product packages are found on the Optimizely NuGet server

Are you looking for release notes before January 2024? See the Optimizely Release Notes on the Optimizely World site.

You can find prior versions of user guides and when functionality was released or deprecated at the following locations:

May 26

EPiServer.Find 16.8.0

Enhancements

  • Added management of statistical autocomplete phrases in the Search & Navigation UI. Statistical phrases are suggestions that Search & Navigation generates automatically from site visitors' previous successful searches. This lets you edit or delete those phrases from the Autocomplete tab to remove inappropriate or unwanted terms from the suggestions shown to site visitors.
  • Added pagination to the Explore view in the Search & Navigation UI. The Explore view loads indexed content one page at a time instead of retrieving every indexed item at once. This reduces load on the search service and the UI and removes the repeated background search requests that the previous behavior generated.
  • Updated the default maximum indexing depth for content areas to three levels. Search & Navigation limits the depth of nested ContentArea mappings to three levels by default, which protects search performance and cluster stability for sites that have deeply nested content structures. Override the default with the MaxDepthContentAreaConverter convention if your site requires a different depth.

Bug fix

  • FIND-15111 – Fixed an issue where the Search & Navigation menu did not display, and Search & Navigation features stopped working when a site used a custom relative path instead of the default EPiServer path. Search & Navigation no longer overrides the configured user interface and protected module paths during initialization.

March 3

EPiServer.Find 16.7.1

Enhancement

  • Added support for Search and Navigation for Content Management System 12 sites with Opti ID enabled. See Configure Opti ID for CMS 12 for more information.

Bug fixes

  • FIND-14387 – Fixed a performance issue that caused excessive CPU and memory consumption during content indexing. The system now uses a pre-compiled static Regex instance to reduce processing overhead.
  • FIND-14641 – Fixed an issue where items in the event indexing queue were not automatically removed after reaching the maximum retry count (default 10). 
  • FIND-14642 – Fixed an HTTP 500 error that occurred when filtering on a $$string field with a null value. The proxy now substitutes null string values with empty strings, and the .NET client ignores filters with null values.
  • FIND-14951 – Fixed a PdfDocumentFormatException error that occurred during PDF attachment text extraction due to an outdated PdfPig library version.