Every PR campaign, sponsorship plan, guest booking and partnership search begins with the same question: which podcasts talk to the people we want to reach? Most teams answer it with a directory search for a few keywords and a scroll through the top results. That finds the obvious shows and misses most of the good ones, because the best-fit podcasts often do not have your keyword in their name.
This guide is a practical manual for finding podcasts by topic and audience with full-text search. It covers how podcast search works, the query techniques that matter (phrases, fields, boolean logic, wildcards), filters, how to infer audience from content, how to use charts and categories, and how to build a reusable library of queries for your clients. Examples use podsearch.org, which searches episodes from about 3.2 million active feeds in the open Podcast Index catalog.
Why directory searches miss good shows
Most podcast apps and directories search primarily on show titles and a short show description. That works when you know the show's name. It fails for topic research for three reasons:
- Show titles are brand names. A great show for HR leaders might be called "The Coffee Break" with nothing about HR in the title.
- Show descriptions are written once. They describe the show at launch, not what it covers today.
- Episodes carry the specifics. The episode titled "How we cut employee turnover by 40%" tells you more about audience fit than any show description.
Full-text search over episode titles and descriptions, and where available episode content and transcripts, finds shows by what they actually discuss.
The basics: words, phrases and ranking
A plain query like employee retention matches episodes containing both words, with matches in the show title ranked highest, then the episode title, then descriptions. Results are ranked by relevance unless you sort by date.
Quote a phrase to require the words together and in order:
"employee retention"
Phrases are the single most useful tool for topic research. "Supply chain" means something precise; supply chain without quotes also matches episodes that mention a chain restaurant's supply of tomatoes.
Field prefixes: say where to match
podsearch.org supports field prefixes that restrict a term to one part of the data:
| Prefix | Matches | Use it for |
|---|---|---|
title: or podcast: | Show title | Shows branded around a topic |
episode: | Episode title | Episodes about a topic, guest names |
desc: or description: | Show and episode descriptions | Broader coverage, sponsors, show notes |
content: or transcript: | Episode content and transcripts, where available | Spoken mentions |
Examples:
episode:"employee retention"
title:hr AND episode:retention
desc:"brought to you by" AND episode:payroll
content:"four-day week"
A rule of thumb: start with episode: for precision, widen to desc: for recall, and use content: when you need spoken mentions and can tolerate more noise.
Boolean logic: AND, OR, NOT and parentheses
Typing AND, OR, NOT or parentheses switches the search into boolean mode automatically. The operators must be uppercase.
- OR expands vocabulary. People say the same thing in different ways:
(episode:layoffs OR episode:"reduction in force" OR episode:downsizing). - AND combines dimensions. Topic and audience:
episode:retention AND desc:"small business". - NOT removes false positives.
"apple" NOT (desc:fruit OR desc:orchard OR desc:recipe). - Parentheses group. Always group your OR lists before combining them with AND.
A well-built query for "HR leaders at mid-sized companies" might look like this:
(episode:"employee retention" OR episode:onboarding OR episode:"people ops" OR episode:"hr leader")
AND (desc:hr OR desc:"human resources" OR desc:"people leaders")
NOT episode:trailer
Wildcards for word families
A trailing asterisk matches word endings:
invest* # invest, investing, investor, investment
nutrition* # nutrition, nutritionist, nutritional
Use wildcards on distinctive stems only. car* matches car, care, career and cardiology.
Filters: language, genre, length and date
The search page offers language and publish-date filters, and the API adds genre, episode length and more:
- Language. Essential for international campaigns. In the API, pass a language code such as
en,esorde. - Publish date. "Episodes in the last 30 days" separates active shows from archives and is the best quick check of whether a show is still publishing.
- Genre (API). Restrict to categories when a topic spans many (for example, "AI" in Business versus Education versus Comedy), using
genre_idsfrom/genres. - Episode length (API). Long interviews and short daily briefs reach different listening moments; use
len_minandlen_maxin minutes.
Through the API (ListenNotes-compatible at https://podsearch.org/api/v2), the same query with filters looks like this:
curl -s -G "https://podsearch.org/api/v2/search" \
--data-urlencode 'q=(episode:"employee retention" OR episode:onboarding) AND desc:"human resources"' \
--data-urlencode "syntax=dql" --data-urlencode "type=episode" \
--data-urlencode "language=en" --data-urlencode "len_min=20" \
--data-urlencode "published_after=1758000000000" --data-urlencode "unique_podcasts=1" \
-H "X-ListenAPI-Key: $PODSEARCH_API_KEY"
unique_podcasts=1 returns at most one episode per show, so the results read as a list of shows, each with an example episode.
Inferring audience from content
Feeds do not publish listener demographics. You can, however, infer a lot about who listens from what a show talks about and how.
Who the host addresses. Descriptions like "for first-time managers", "for nurses", "for indie game developers" are explicit audience statements. Search for them:
desc:"for first-time managers" OR desc:"for new managers"
Who the guests are. A show that interviews CFOs reaches finance leaders. Search episode titles for role words: episode:cfo OR episode:"chief financial officer".
What the sponsors sell. Sponsors pay to reach specific audiences. Descriptions listing B2B software sponsors suggest a professional audience; mattress and meal-kit sponsors suggest a broad consumer one.
Format and length. Short daily news briefings reach commuters and professionals keeping up; long technical deep dives reach practitioners.
Language and region signals. Local place names, currency and regulations mentioned in episodes point to a geography.
Combining these gives you an audience profile that is often more reliable than self-reported categories.
Using charts, categories and new shows
Search is the precise tool; browsing helps you understand a landscape. On podsearch.org:
- Browse covers 19 categories.
- Charts show Apple Podcasts rankings per country, which is useful for finding the biggest shows in a category and market.
- New shows surface recent launches, which are often open to guests and inexpensive to sponsor.
A good workflow is to browse a category's chart to understand the head of the market, then use search to find the mid-sized and long-tail shows that the chart does not show.
Searching for people, companies and products
Topic research often starts from a name rather than a subject: a competitor, a client's peer, a product category leader. Names are easy to search and hard to search well.
Quote full names. "Jane Doe" as a phrase avoids matching every Jane and every Doe. For very common names, require the name in the episode title (episode:"Jane Doe"), where guest names usually appear.
Add context for ambiguous names. A person who shares a name with a celebrity needs a disambiguating term: episode:"Chris Evans" AND (desc:marketing OR desc:saas).
Search company names with and without suffixes. "Acme Analytics" OR "Acme Inc" catches the variants people use in show notes.
Look for product mentions in descriptions. Sponsors, tools and books are often linked in show notes. desc:"Product Name" finds shows whose hosts or sponsors mention it, which tells you about audience interest in the category.
Track names over time. Sort by date to see who is talking about a person or company now, rather than years ago.
People search pays off twice: it finds shows directly, and the shows that interview your competitors' executives are exactly the shows that might interview your client.
A worked example: one brief, five queries
Brief: a climate-tech startup wants to reach facilities managers and sustainability leads at mid-sized companies in the US and UK.
- Audience statements.
desc:"facilities managers" OR desc:"facility management" OR desc:"sustainability professionals"finds shows that say who they are for. - Topic episodes.
(episode:"energy efficiency" OR episode:"net zero" OR episode:decarboni*) AND (desc:buildings OR desc:facilities)finds episodes on the problem the product solves. - Guest roles.
episode:"sustainability director" OR episode:"head of sustainability" OR episode:"chief sustainability officer"finds shows that interview the buyer persona. - Competitor mentions. Descriptions mentioning two or three competitors' names find shows already covering the category.
- Recency and language. Each query filtered to English and the last 90 days, with one result per show.
Merging the five result sets by show and counting how many queries each show matched gives a natural ranking: a show that appears in four of the five is almost certainly a fit. In practice, the shows that rank highest this way are rarely the ones a directory search for "sustainability podcast" would have returned.
Building a query library
Agencies run the same kinds of searches for many clients. A shared query library saves hours and improves quality over time.
For each audience or topic you work on often, store:
- The query, with vocabulary lists in OR groups.
- Filters used (language, genre, length, date window).
- Precision notes: false positives you found and the NOT clauses that removed them.
- Date last validated.
Example library entries:
| Audience | Query |
|---|---|
| Small-business owners | (desc:"small business" OR desc:smb OR desc:"business owners") AND (episode:hiring OR episode:cash* OR episode:marketing) |
| Clinicians | (desc:physicians OR desc:nurses OR desc:clinicians) AND (episode:burnout OR episode:"patient care") |
| Indie developers | (desc:"indie dev*" OR desc:"solo founder" OR desc:"bootstrapped") AND episode:launch* |
| Personal finance, Spanish | (desc:"finanzas personales" OR desc:ahorro OR desc:inversión) with language es |
Validate each entry every few months by reading 20 random results. Vocabularies drift.
Exporting and sharing results
For client deliverables, export shows rather than screenshots. Two routes:
- API scripts that run your library queries and write a CSV with show title, publisher, RSS URL, an example episode and its date.
- Catalog exports from the datasets page, filtered by category, language, activity and episode count, which include websites, published contact emails, episode counts and latest publish dates.
Combining both is powerful: use search to find the right shows by topic, then join to a catalog export for contact and activity fields.
Avoiding common mistakes
Too narrow too early. Start broad, look at results, then narrow. Over-specified first queries return nothing and teach you nothing.
Trusting titles. Always check recent episodes. A show called "Startup Stories" may have pivoted to crypto.
Ignoring language and geography. An English query returns shows from every English-speaking market. Filter or check.
Mistaking volume for fit. A daily show matches many queries simply because it has thousands of episodes. Use unique_podcasts=1 and judge each show by consistency, not match count.
Forgetting AI-generated shows. Some feeds generate large numbers of episodes on trending topics. podsearch.org labels shows "likely AI" only at 0.9 classifier confidence or higher, with partial, on-demand coverage. Check unfamiliar high-volume shows by listening.
Saving time with repeat searches
Most research repeats. Save the search URLs of your best queries on podsearch.org (the query is in the address bar, so a bookmark or a shared document works), and re-run them whenever a client brief comes up again. Sorting by date on a saved query shows only what is new since you last looked, which turns a half-day research task into a ten-minute refresh.
When to stop searching
Research has diminishing returns. When new queries mostly return shows you have already found, your candidate pool is complete enough for the brief. Spend the remaining time qualifying and researching the best shows, which is where placements are actually won.
Frequently asked questions
What is the best way to find podcasts about a niche topic?
Search episode titles and descriptions with a quoted phrase and a few synonyms in an OR group, filter by language and recent dates, and use unique_podcasts=1 in the API to get one result per show.
How do I find podcasts for a specific audience?
Search descriptions for explicit audience statements ("for nurses", "for founders"), episode titles for guest roles, and descriptions for sponsors that target that audience.
Do boolean operators work on podsearch.org?
Yes. AND, OR, NOT, parentheses, quoted phrases and trailing wildcards are supported, along with field prefixes such as title:, episode:, desc: and content:. Operators must be uppercase.
Can I search inside episodes?
Where feeds provide transcripts or content, yes: use the content: prefix, or deep_search=1 in the API.
How do I find the biggest podcasts in a category?
Browse the category and the Apple Podcasts charts per country on podsearch.org, then use search for the mid-sized shows the charts do not show.
Can I export my search results?
Use the API to script searches into a CSV, or buy a filtered catalog export from the datasets page and join it to your search results.
Summary
Finding the right podcasts is a search skill. Search episodes, not just show titles; use phrases, field prefixes and boolean logic; filter by language, length and recency; infer audience from guests, sponsors and descriptions; browse charts for the head of the market and search for the rest; and keep a validated query library. The shows that fit your campaign are there; the right query finds them.