“Find a podcast about gardening” and “find the interview with this gardener” are different tasks. The first needs a show worth following. The second may need one episode from a show the listener does not know.
A single flat result list makes those tasks hard to read. A show and an episode can share similar titles while leading to very different next screens.
Start with the expected next action
A show card should help someone decide whether to open a catalog or follow it. Useful context includes the show title, publisher, artwork, language, and a short description where available.
An episode card should explain what can be played. Show the episode title together with its parent show, date, and duration when those fields exist. A title alone often loses its meaning outside the show page.
Podnivo's search documentation distinguishes podcast and episode discovery. Use the current documented type filter instead of guessing a response field from a visual label.
If you offer both types, separate them with clear headings or tabs. Keep a selected type in the URL when a listener shares the search. Changing the type should restart pagination rather than reuse a cursor from a different result set.
Test ambiguous queries
Choose a phrase that appears in both a show name and several episode titles. Check that each card's label explains its type without relying only on color. Keyboard users should be able to hear a useful accessible link name.
Measure whether people reach the screen they intended. A higher click count can simply mean they are opening the wrong kind of result and going back. Good search design reduces that uncertainty before the click.