# Search results 🔍 * [ ] Search box The element a user types in to make a search ⭐️ A search box should be at the top of the page, styled consistently with other search boxes across your website or product ⭐️ Include a button to click to process search ⭐️ Placeholder text can nudge the user to make a relevant search * [ ] Visualization of results Showing the items relevant to the search * [ ] Search progress A search may not be instant, so consider a loading indicator as the product makes the enquiry * [ ] Suggested search items Offer a search query to save the user from typing e.g. currently trending, most popular, recently search, autocorrection * [ ] Categories and/or filters Constraints to help users narrow down their search area * [ ] Ordering of search results How a user can sort results e.g. best price, most relevant, newest first * [ ] Highlighting keywords Highlight the words in the search enquiry within the results displayed --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/search-results.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.