HomeEngagementContentDiscoveryOther resources
Release notes
Back to All

🚀 Release 2025-11

January 29th, 2025

Release date: January 30, 2025

TL;DR: New enhancements in Ranking diagnostics. Fixed bugs to enhance performance.

⚡Improvements

View impact of ranking rules in Ranking diagnostics

We are excited to share that the Ranking diagnostics tool now shows how different ranking rules affect each search result.

What’s new?

  1. The refreshed UI for the Ranking diagnostics dashboard offers a consistent experience with the Visual editor.

  2. A new “Rules” tab displays the impact of various PID-based or attribute-based ranking rules.

  3. All the global and local rules that apply to the current search are shown, along with the number of products each operation affects.

    Image of the Ranking diagnostics page in the Bloomreach dashboard. It highlights the Rules tab in the report, and different ranking rules affecting the search.

    The Rules tab in the diagnostics report

Why is this valuable?

  • Reviewing the exact impact of multiple ranking rules will aid in debugging searches and rules.
  • More transparency on the factors affecting search results can help identify the causes behind unexpected results.

View the documentation article to learn more.

What’s coming next?

In the upcoming releases, we plan to enable you to turn individual ranking rules on/off to view their impact in the Ranking diagnostics tool. This will be followed by more updates to improve the overall debugging experience!

🐛 Bug fixes

We have fixed the following issues:

  1. Site-level synonyms in staging couldn't be cloned to the production environment.
  2. Disabled synonyms were incorrectly displayed in Ranking diagnostics.
  3. The category ranking rules homepage showed an error instead of loading the page data.
  4. Some category ranking rules displayed a “Failed to load” error.
  5. The visual editor did not display the complete product titles.
  6. Product collections analytics displayed identical data for three separate site groups.
  7. The top keywords report did not load as expected when switching between the account and site-level contexts.