| UI or UX | UI + UX - Search activity management surface with deletion and capture controls | UI + UX - Passive history of submitted search queries that can be rerun | UI + UX - Persisted named search criteria for rerunning a dynamic result set | UI + UX - Automatic list of items the current user opened recently |
| UI guidance | Render search history as a management page or panel with query text, product or source, account/device/workspace scope, timestamp, and clear controls for filtering and deletion. | Render recently searched as a labelled list of query strings the current user actually submitted, ordered newest first, with query text, scope or source, timestamp, and a clear affordance to rerun each query. | Render Save search near the active query and result summary, and show exactly which query text, filters, scope, and sort will be stored. | Render a labelled list or rail of items the current user actually opened, ordered most recent first, with enough identity to recognize each item such as name, type, thumbnail or icon, location, status, and last-viewed time. |
| UX guidance | Use search history when users need to review and control stored search activity across time, products, devices, accounts, or workspaces. | Use recently searched to help users recall and repeat prior search paths without recreating exact wording, especially in large search surfaces where the same query may be useful later. | Use saved search when users repeatedly need the same dynamic result set and must rerun it without rebuilding query, filters, sort, and scope. | Use recently viewed to reduce re-finding effort when users compare items, pause work, resume documents, or return to records they inspected during the current or recent sessions. |
| Good UI | An account activity page lists Gmail, Drive, and web searches with query text, source, device, time, delete-one controls, product filters, date range, and a pause switch. | A knowledge search box opens to Recently searched with benefit appeal deadline, housing evidence upload, and debt advice appointment, each showing scope, time, result count, and a remove control. | A search results page shows Save search beside the result count, opens a naming dialog, and previews query, filters, scope, and sort before saving. | A procurement dashboard shows Recently viewed records with title, record type, status, project, last-viewed time, and a remove control for each row. |
| Bad UI | A button labelled Clear history deletes saved searches, viewed records, and recommendations without naming the affected data. | A list called Recent includes promoted queries, saved searches, recently viewed suppliers, and another user's sensitive query. | A star icon saves an unnamed search with no confirmation or criteria summary. | A homepage shows a Recently viewed carousel filled with promoted products the user never opened. |
| Good UX | A user filters search history to Drive searches from last week and deletes two entries without deleting saved searches. | A user reruns benefit appeal deadline from recent searches and returns to the current result set without creating or modifying a saved search. | A user saves a search for Open renewal risks, returns next week, reruns it, and sees newly matching cases included. | A user opens several supplier records, returns to the dashboard, and reopens the most recent record without reconstructing the search. |
| Bad UX | Users think pausing search history deletes past entries because the interface does not distinguish future capture from stored history. | A shared kiosk shows a prior user's health search because the list has no account or device boundary. | Saving search stores only the current three results, so future matching records are missing. | Users trust a Recently viewed rail as a recommendation and choose an irrelevant item because sponsored content was mixed into history. |
| Best fit | Search activity persists beyond the current session and users need to inspect or control it. | Users revisit a search surface and benefit from rerunning recent query wording. | Users repeat the same search criteria across sessions or operational cycles. | Users inspect multiple objects and often need to return to one they recently opened. |
| Avoid when | The product only needs a short inline list of recent queries for quick rerun. | The search surface is public, shared, signed out, or privacy-sensitive and cannot provide clear controls. | The query is a one-off lookup that users will not need again. | The content set is tiny, linear, or easy to scan without history. |
| Required state | Empty history state with storage scope and next steps. | Empty or hidden state before any qualifying query has been submitted. | Unsaved current search with Save search available only when criteria are meaningful. | Empty or hidden state before any qualifying item has been viewed. |
| Accessibility burden | Use headings and table or list semantics that expose query, source, date, and scope for each entry. | Use a heading or labelled region that identifies the list as recent search history. | Use labelled form fields for saved-search name, description, visibility, and subscription settings. | Use a heading or labelled region that describes the scope of the list. |
| Common misuse | Using search history as a generic label for a short recently searched dropdown. | Recording unsubmitted keystrokes as search history. | Saving static result IDs instead of reusable criteria. | Filling recently viewed with recommendations, ads, popular items, or related content. |