YouTube search: history, suggestions, sponsored results and filters
This captured iOS journey starts on the YouTube home feed, then opens search history, voice input and query suggestions before showing a sponsored result, format shortcuts, an overflow menu and detailed filters. Search is available from the home header, recent queries can be reused, voice input has a visible listening state, suggestions extend typed text and the filter page groups sort order, content type and upload date.
The screenshots show the organisation and presentation of search tools; they do not demonstrate reduced friction, trust, momentum, recall or preference. Recent history is not a Recency Effect, a prominent microphone is not a default, bold query completions do not measure cognitive load and different result formats do not prove Choice-Supportive Bias. The most material review questions are whether people can understand history controls, distinguish paid from organic results, know why suggestions appear and recognise which filters are active.
- Captured
- Capture date not recorded
- 8
- Screens
- 3
- Ingredients
- 3
- Applications
Common contexts
Business goals
What works
What the captured flow does well.
- Search is available in the home header and remains visible through results.
- The search landing page shows recent query text, a history symbol, thumbnails and a control for reusing each query.
- Voice search says “Speak now”, presents a distinct listening state and provides a close control.
- Query suggestions preserve the entered words and visually distinguish proposed additions.
- The paid result includes a visible “Sponsored” label and advertiser domain.
- Results provide quick format choices and a separate filter page with grouped, visibly selected options.
What could improve
What deserves closer review.
- The arrow beside each recent query is not explained in the screenshot, and no delete or clear-history control is visible.
- The voice screen does not show what audio is processed, how to stop recording, or the recovery state for silence, permission denial or a recognition error.
- Suggestions do not say whether they come from the typed text, personal history, general popularity or another ranking input.
- The sponsored result occupies the first visible result area and resembles the surrounding content stream; the screen does not explain why that advertisement was shown.
- Detailed filters are available only through the overflow menu while the visible chips focus mainly on format and watch state.
- The filter page shows Relevance, All and Any time as selected defaults, but the capture does not show an Apply or Reset action or explain whether changes take effect immediately.
Screen-by-screen breakdown
Follow the journey.
Each annotation distinguishes what is visible from our interpretation or hypothesis, then identifies a practical opportunity to investigate.
Screen 01
YouTube home
Keep search in a predictable header position with an accessible name and adequate target size. Only add a tutorial or temporary emphasis if task research shows that the intended audience cannot find it.
Screen 02
Search landing screen
Give the reuse arrow an accessible label, make individual deletion and clear-history controls easy to find and explain whether thumbnails represent the previous result. Keep a generic placeholder unless examples would materially help the current audience.
Screen 03
Voice search interface
The voice-search overlay says “Speak now”, presents a listening state and provides a close control. This communicates system status while input is expected; the static screenshot cannot verify animation, recognition accuracy or error recovery.
Announce when listening starts and stops, explain microphone use at the permission point and provide clear states for silence, no match, permission denial and retry. Do not add a countdown that pressures speech unless there is a real time limit.
Screen 04
Search suggestions
Distinguish typed text from the proposed completion and make insertion controls understandable to screen readers. Explain suggestion inputs in accessible help and provide ways to remove history-derived suggestions where relevant.
Screen 05
Search results with sponsored result
Keep the Sponsored label visually and programmatically attached to the advertisement, identify the advertiser and provide a “Why this ad?” route. Paid placement should remain distinguishable from organic relevance at a glance.
Screen 06
Search results with format shortcuts
Keep the selected format chip clear, preserve access to the full filter set and make horizontally hidden choices discoverable. Explain whether selecting Shorts, Videos or another chip replaces or further filters the result set.
Screen 07
Search options menu
The overflow menu reveals Search filters and Help and feedback without keeping those secondary routes in the results header. This is an observable use of progressive disclosure; the screenshot does not show whether people discover the menu.
Use descriptive option labels, move keyboard or screen-reader focus into the menu, keep a reliable close route and return focus to the trigger. “Search filters” is clearer than adding a generic “Refine by” heading.
Screen 08
Search filters
Relevance, All and Any time are visibly preselected and will define the result set unless changed. These are interface defaults; the screenshot does not show whether people keep them or whether they produce the best result for a task.
Show whether changes apply immediately, provide Reset all, summarise active filters on return to results and announce result updates. Keep preselected defaults visible and avoid implying that Relevance is an objective quality ranking.
Keep exploring