Yes. searchHub’s data-driven approach allows relevance to be calculated based on how well a search term positively influences the overall shop performance. The information is then accessed by using the searchHub searchDataService.
searchHub is not a site search engine. We cluster all keyword variations, and deliver only the best performing query to your site search. The result is fewer queries being sent to your search engine, which in turn increases the cache-hit-ratio and the so-called “call back” performance.
searchHub is equipped with an AI Trainer. Search managers use this tool to manually edit the keyword relationships within our AI. Additionally, searchHub's knowledge base is prefilled with common synonyms on a per-client basis. Lastly, importing synonyms and antonyms via .csv file is also available.
searchHub’s AI clusters all keyword variations around a so-called “MasterQuery”. This ensures more traffic (also known as, “The Longtail”) is redirected to your curated pages without any optimization necessary.
searchHub can use your product export to more precisely determine customer intent. Ingesting brand and product names, for example, allow us to more precisely map misspellings to the highest performing outcome and to learn your custom product language.
Yes. Not only does searchHub provide a function within our UI to manage your redirects, our clustering technology means you create a redirect for MasterQueries only. These then apply to all query variations within the respective cluster.
Auto-complete suggestions delivered by searchHub can be adjusted within the searchHub UI. Choose between overall popularity or most trending suggestions, or add your own custom KPIs. searchHub will make sure to only deliver precise suggestions without embarrassing typos.
Yes. Queries which have previously been mapped or clustered together under a common MasterQuery can be monitored in the searchHub UI. This makes it easy to see how important an automated approach is.
Yes. searchHub has developed a proprietary algorithm to identify potential bot traffic and weed this out to ensure these queries do not skew cluster performance.
