Feature Requests

We need the ability to flag clusters as "checked but not relevant" (in underperforming queries etc.). There are terms that refer to products we will never carry in our portfolio. We would like to mark these terms in order to exclude them from further review (e.g., via a filter). As of today, the terms remain permanently in the evaluation. And their number keeps increasing.

Objective: Enable the ability to tag specific query clusters or individual queries with a flag that indicates they have an informational or content-driven intent. This will allow a clearer separation from transactional keywords and prevent them from distorting key performance metrics. Background: Some user queries are not aimed at finding products or completing a purchase, but instead seek educational content, guides, or blog articles. Currently, these queries are grouped together with transactional ones, negatively impacting KPIs such as CTR and conversion rate. Requirements: Ability to manually or rule-based tag clusters/queries as “informational” Optional: Filter option in the analysis view to separate KPIs for transactional vs. informational searches Tags should be persistent and usable in reports and dashboards Benefits: Clearer segmentation of search intent More accurate evaluation of KPIs for transactional queries Improved basis for search optimization and content strategy decisions

We request the implementation of a filter option in Searchhub that allows users to generate a list of the most visited clusters while excluding those with an active redirect. This functionality would significantly reduce manual effort, as the current process involves reviewing high-traffic clusters individually to determine whether a redirect is already in place. Automating this step would optimize workflow efficiency and help focus optimization efforts on unresolved clusters only.

As a search manager I would like to edit or delete deployment before go live. Like that I don't need to wait for the deployment to edit mistakes. With multiple people working in searchhub, that can save a lot of time and adds convenience

As a Search manager I w.ant to be able to see who did which changes. This would make it a lot easier for me to know who to contact. We do quality assurance every day and control the deployment before we push the changes live. Sometimes there is an error in the changes which were made. And because there often are multiple people working on the same categories, it is difficult to know who to contact. In order to be able to save time, it would be really helpful to see the Name/Nickname/.. of the one who made the change inside the deployment.

To activate AI redirects, it is currently necessary to do so by enabling the switch one by one. It would be very helpful if you had the option to activate multiple redirects with a single click.

This was a discussion point with Markus K. today. In order to optimize not only spelling or various similar wordings inside a cluster is there a possibility to get suggestions beyond the obvious missspelling etc. Goal for us would be to integrate ALL possible search queries into the existing cluster. example: Montageprofil -> Clustered already in various spelling types. In addition we need to add: bauprofil, 4kant profil, 6kant profil, profilschiene etc. (infos I do get when I e.g. look at other DIY shops or ask the google keyword planner...

Often the displayed cluster name is based on a variant of the cluster which is not popular or even useless. Example @hede: A cluster is called "vausschnitt Pullover" and the MQ is "pullover v ausschnitt". "vausschnitt" has 0 popularity within this cluster but is the main title of the cluster. 2 optimizations would be helpful: rename the cluster after the master query (no matter if set manually or data based) option to rename a cluster (overwriting the existing clustername)

If a user manually sets a redirect for a query cluster, the query testing should be ignored.

To enable users: 1) to see the entire list of words (including total number of words available) 2) allow for filtering of the words by the different categories that it is mapped to in the popular categories categories 3) include some KPIs of the words so users know which ones to focus on first if there is limited resources working on it