The Search results section in the Test results module of Spotler Activate Search lets you test a search term, review the returned results, and inspect the technical response behind those results. This section combines a live result view with advanced result details, so you can understand what the search engine returns and identify where relevance, sorting, filters, or data quality can be improved.
What is Search results?
Search results is a testing module in Spotler Activate Search that shows how the software responds to a search query in real time.
The module is designed to help you evaluate both the user-facing result page and the underlying response data. This makes it useful for functional checks, relevance analysis, troubleshooting, and search optimisation.
The exact output depends on the data, configuration, and search settings available in your environment. Because of this, the number of results, available sort options, filters, and products can differ between accounts.
On this page, the following topics are covered:
- What do you see in the Search results screen?
- How do you test a search query?
- What are Advanced Search Result Details?
- How do you read the payload?
- How do you read the results response?
- How do you evaluate the visible search results?
- Who uses this module and why?
- How do you use Search results to improve search quality?
- What is the result of using this module?
- FAQ
What do you see in the Search results screen?
When you open Search results, you see a complete testing view of the search experience.
At the top of the page, you can open the module directly through the Test your Search button that is available from anywhere in the software. This makes it easier to move quickly from another module to the search test view.
Below that, you see a search bar where you can enter a search term and test how the search engine responds.
Next to the search bar, you see a gear icon. This icon opens an additional panel with technical details about the search request and response.
Below the search area, the module shows the result page preview. This preview includes the total number of returned results, the available sorting options, the facet or filter area on the left side, and the products or items returned for the query.
This layout helps you review both the customer-facing output and the technical context in one place.
Minimal design by default
The Search results view intentionally uses a minimal design, with filters collapsed by default. This keeps the focus on the returned results and the query analysis before you refine the result set further.
How do you test a search query?
You can use Search results to simulate how a visitor searches in your environment.
- Enter a search term in the search bar.
- Run the query.
- Review the returned result set.
- Check the number of results that match the query.
- Review the visible sort options.
- Inspect the filters shown in the left-hand menu.
- Evaluate the products or items displayed in the result overview.
This test shows how the current search configuration responds to a specific input. It is useful when you want to understand whether the search engine recognises the query correctly and whether the returned items match the expected intent.
Tip
Test both broad and specific queries. A broad query helps you evaluate ranking, filtering, and sorting behaviour, while a specific query helps you check whether exact products, brands, attributes, or article numbers can be found correctly.
What are Advanced Search Result Details?
The Advanced Search Result Details panel gives you a technical view of the search call behind the visible result page.
You open this panel through the gear icon next to the search bar.
The panel contains two main parts:
- Payload, which shows the request that is sent.
- Results, which shows the response that is returned.
This panel is useful when the visible result page alone does not explain why a query behaves in a certain way. It helps you understand which search term, filters, sorting settings, and response elements are involved.
How do you read the payload?
The payload shows which input is sent to the search engine for the current test.
In the example view, the payload includes fields such as search_term, filters, sort_by, offset, and limit.
These fields help you understand how the request is constructed.
| Field | What it shows | Why it matters |
search_term |
The entered query. | Use this to confirm that you are testing the intended search input. |
filters |
The active filter selection. | Use this to check whether filtering affects the returned result set. |
sort_by |
The selected sorting method. | Use this to verify whether the result order is based on relevance or another sorting rule. |
offset |
The starting point in the result list. | Use this to understand pagination or where the result set begins. |
limit |
The number of items requested. | Use this to confirm how many results are returned in the current response. |
The payload is especially useful when you want to confirm whether the expected query settings were actually sent. If the visible output looks incorrect, the payload is the first place to check whether the request itself already explains the behaviour.
How do you read the results response?
The results response shows what the search engine returns for the submitted payload.
In the example view, the response contains items such as success, code, facets, sort_fields, fullDebug, data, meta, banners, and result_id.
Each part helps you interpret a different aspect of the result.
| Response item | What it tells you | How to use it |
success |
Whether the request completed successfully. | Use this as a first check to confirm that the call returned a valid response. |
code |
The response code of the request. | Use this to support technical troubleshooting when the result is unexpected. |
facets |
The filter groups available for the query. | Use this to verify whether expected filters are returned and whether the result set is grouped correctly. |
sort_fields |
The available sorting options. | Use this to confirm which sort methods are available in the current environment. |
fullDebug |
Additional debug information. | Use this when you need more technical context for result interpretation. |
data |
The returned products or items. | Use this to inspect the actual content shown in the result overview. |
meta |
Metadata about the response. | Use this to understand response context, counts, or additional result information. |
banners |
Additional returned content such as banners, when configured. | Use this to verify whether non-product content is included in the result page. |
result_id |
An identifier for the returned result set. | Use this for reference during analysis or follow-up debugging. |
The results response helps you understand not only what is shown, but also why it is shown in that form.
Important
A correct technical response does not always mean the search experience is optimal. A query can return a successful response while still showing weak ranking, missing expected products, or less useful filters. Always evaluate the visible result page together with the technical details.
How do you evaluate the visible search results?
The result overview helps you assess the functional quality of the search experience.
Start by checking the total number of results. This gives you a quick indication of whether the query is broad, narrow, or unexpectedly empty.
Then review the sorting options. Depending on the settings in your environment, this can include options such as relevance, price, or popularity. These options are environment-specific and can differ between implementations.
Next, review the filter area on the left side. This section shows the categories or facets that users can use to refine the result set further. Check whether these filters are useful, complete, and logically connected to the search term.
Finally, inspect the returned products or items. Review whether the results match the likely search intent, whether important items appear high enough in the list, and whether the content is understandable and relevant for the query.
When you assess the visible output, focus on these questions:
- Does the query return the expected type of result?
- Are the most relevant items shown first?
- Are important products missing?
- Do the available filters help refine the query?
- Do the sort options support the intended search experience?
- Does the result count make sense for the query?
Who uses this module and why?
The Search results module is useful for different roles involved in search quality and product discovery.
Merchandisers and e-commerce teams
Merchandisers and e-commerce teams use this module to check whether important products appear for strategic search terms. They often focus on ranking, visibility, sorting behaviour, and whether result pages support conversion goals.
Search specialists and implementation teams
Search specialists and implementation teams use this module to validate configuration changes, inspect returned facets, review payload values, and understand how the engine responds to specific queries. They often use the advanced details to diagnose why a query behaves differently than expected.
Support and optimisation teams
Support and optimisation teams use this module when users report unclear search behaviour, missing products, irrelevant rankings, or unexpected filter output. The combined functional and technical view helps them reproduce the situation and narrow down the cause.
Content or catalogue owners
Content or catalogue owners use this module to spot possible data quality issues. For example, they may notice that products are difficult to find, grouped incorrectly, or missing from expected result sets because the underlying data does not support the intended search behaviour.
Example use case
A merchandiser wants a high-priority product group to be easier to find for a common search term. In Search results, the merchandiser tests the query, checks whether the expected products appear in the returned data, reviews the visible ranking, and confirms which filters and sort options are available. If the result still looks unclear, the merchandiser or a search specialist can open the advanced details to inspect the payload and response more closely.
How do you use Search results to improve search quality?
You can use this module as a structured optimisation tool.
- Test a realistic search query.
- Review the visible result page and technical details together.
- Check whether the query intent matches the returned results.
- Identify whether the issue is related to ranking, filtering, sorting, or returned data.
- Compare multiple queries to detect recurring patterns.
- Use the outcome to define the next optimisation step.
Common optimisation questions include whether the right products are shown, whether the sort order supports the expected search experience, whether filters help users refine effectively, and whether the underlying response contains the expected structure.
For more technical interpretation, your team can also use the internal Spotler Activate Search Debugger GPT as an additional aid when reading complex search output. Use it as support for interpretation, not as a replacement for validating the behaviour in your own environment.
What is the result of using this module?
By using Search results, you gain a clearer understanding of how the search engine behaves for specific queries and why a result page looks the way it does.
This helps you identify improvement opportunities in relevance, sorting, filtering, and result quality. It also helps teams work more efficiently because the module combines a practical result preview with technical debugging details in one place.
The end result is a more transparent search process and a better basis for improving the search experience in Spotler Activate Search.
FAQ
Does every account show the same results?
No. The output depends on the data, connected sources, and configuration available in the environment.
What is the difference between the visible result page and Advanced Search Result Details?
The visible result page shows what a user would experience, while Advanced Search Result Details shows the technical request and response behind that experience.
Why should I check both the payload and the results?
The payload helps you confirm what was sent, and the results help you confirm what was returned. You need both views to analyse search behaviour correctly.
Can I use this module for optimisation as well as troubleshooting?
Yes. The module is useful for both routine search improvements and for analysing unexpected search behaviour.