A blank search page says very little. Did nothing match, did the network fail, or did the app forget to load? These states need different messages because they need different actions.
Only show “No results” after a successful response that contains no matching items. A timeout or server error is not evidence that the catalog has nothing relevant.
Offer one helpful next step
Keep the query visible. Suggest shortening a long phrase, checking a name, or removing a restrictive filter. If the app supports both show and episode search, explain that switching the result type may help.
Do not automatically replace the query with a popular term. A listener may be looking for a small show, a name in another language, or a specific older interview. Their input remains useful even when the first attempt fails.
A broad query such as “gardening” and a narrow phrase such as “winter container composting interview” need different expectations. Help the listener move between them without suggesting that a result is guaranteed.
Make state changes accessible
Announce the result count or empty message through an appropriate status region. Avoid moving keyboard focus away from the input every time a person types. Give any “clear filters” control a clear label and keep it reachable with the keyboard.
Test three fixtures: a successful empty response, a failed request, and a response that arrives after the query was cleared. They should produce three intentional states rather than the same empty illustration.
An empty page is still part of discovery. Its job is to help the listener make a better next request, not to hide uncertainty behind cheerful but vague copy.