A list displaying all the search results found after a user has made a search.
About this pattern
This pattern includes the search results page, the ability to display multiple pages of search results and to navigate between pages.
Within the pattern:
- users can choose the page they want by picking a page number at the bottom of a search result page, starting at page 1
- each individual page number contains 10 search results
- the page number the user is on is always highlighted
A maximum number of 7 page numbers are shown at the bottom of a page of search results, but the user can select pages outwith these 7 by choosing the “…” (ellipsis) symbol.
An option to select ‘previous’ page appears to the left of the 7 numbers and an option to select ‘next’ page on the right. The current page number always appears in the URL, for example
On a mobile, a ‘Load more’ button is shown instead of a list of page numbers.
When there are no results found
If a user has searched for something and there are no results to display, give the user some hints for how to improve their search.
Components related to this
Why we use this pattern
The design of the pattern helps the user to browse their search results, or to refine their search term if the search results do not meet their needs.
Many analytics tools offer out of the box tracking for site search. The setup below covers more complex tracking to understand which search result was interacted with from a search results page, and how additional interactive elements are being used.
Search results should be tracked in order to understand if internal search engines are providing useful results to users. Tracking works through the query being available from the page URL, the click text, click URL and a data attribute showing the result’s position.
Clicks to the suggested terms in the “did you mean…” component are tracked through the page URL (which contains the original search query), the click text, the click URL and a data attribute.
Pagination is tracked using the data attribute with the number of the results page clicked.
The data attributes are added automatically by the Design System’s “tracking” script.
Search suggestions use WAI-ARIA attributes to give more context for screen reader users. They include:
- link text for each suggestion being overwritten with a more descriptive aria-label
- text “Did you mean?” being hidden to avoid duplication in the links
- suggestions being wrapped in a nav element with a descriptive aria-label Supporting evidence: mygov.scot accessibility review, March 2019.
Feedback, help or support
If you need any help or want to give any feedback you can e-mail us at: firstname.lastname@example.org