Podcast guesting is still one of the highest-ROI B2B marketing channels in 2026. A 2025 survey by Demand Sage found that 82% of B2B marketers who appeared on podcasts said it directly influenced pipeline. The problem isn't whether it works. The problem is finding the right email address for the host so your pitch actually lands.
I run ApifyForge, where we've built and maintained 300+ web scraping actors on Apify. One of them -- the Podcast Directory Scraper -- exists specifically because I watched PR agencies burn hours manually hunting for podcast host contact info. There are exactly three reliable data sources for podcast host emails, and most people only know about one of them. Here's all three, plus the workflow that gets you from keyword to verified email in under 10 minutes.
What are the 3 data sources for podcast host emails?
The three primary sources for finding podcast host email addresses are: (1) the itunes:owner tag inside RSS feeds, which contains the email the host registered with their podcast hosting platform; (2) Apple Podcasts and Spotify metadata accessible through their public APIs; and (3) the podcast's own website, which often has a contact page, booking form, or team page with direct email addresses.
Most guides only mention the first one. That's a mistake, because RSS feeds only contain the owner email about 50-80% of the time, according to data from Podcast Index, the open-source podcast directory. If you stop at RSS, you're missing a huge chunk of your target list.
Let me break down each source and what you actually get from it.
Source 1: RSS feed itunes:owner tag
Every podcast submitted to Apple Podcasts has an RSS feed. Inside that feed, there's an XML block that looks like this:
<itunes:owner>
<itunes:name>Sarah Chen</itunes:name>
<itunes:email>booking@verdantmedia.com</itunes:email>
</itunes:owner>
This is the email the host gave to their podcast hosting platform (Buzzsprout, Libsyn, Podbean, Anchor, etc.) when they set up the show. It's the single best source for host emails because it's self-declared -- the host put it there intentionally. For professionally produced shows, this email is almost always monitored. It's where Apple sends communication about the show, so hosts don't let it go to a dead inbox.
The catch: you can't see this on the Apple Podcasts website or app. The itunes:owner block is only in the raw RSS XML. You have to fetch the feed URL, parse the XML, and extract it. Doing that manually for 200 podcasts is... not how you want to spend your Tuesday.
Source 2: Apple Podcasts and Spotify API metadata
The iTunes Search API returns structured data for every podcast in the Apple catalog -- title, author name, genre categories, episode count, artwork, and the RSS feed URL itself. Spotify's Web API gives you similar metadata plus the Spotify-specific show URL. Neither API gives you the host email directly. But they give you the RSS feed URL (which leads to source 1) and the author/artist name, which you need for source 3.
The iTunes API indexes over 4.2 million podcasts across 175+ country storefronts, per Listen Notes' 2025 statistics. That's the universe you're working with.
Source 3: The podcast website
This is the source most people skip entirely, and it's often the best one. About 65% of podcasts in the Apple catalog include a website URL in their RSS feed's <channel><link> tag. That website usually has:
- A "Contact" or "Book a Guest" page with a direct email or form
- A team/about page with host names and titles
- Footer links with social profiles (LinkedIn is gold for warm outreach)
- Sometimes a media kit with explicit booking instructions
For podcast guest outreach specifically, the website is where hosts tell you exactly how to pitch them. Some have a dedicated /guest or /apply page. Some have a Calendly link. Some say "email me at..." in plain text. You just have to actually visit the site and look.
How do you find podcast host emails at scale?
To find podcast host emails at scale, use a three-step process: search Apple Podcasts by keyword to discover shows in your niche, parse each show's RSS feed to extract the owner email, then scrape the podcast website for additional contact data. This workflow replaces 6-8 hours of manual research with a 5-10 minute automated run.
Here's the exact setup I recommend, with real input and output examples.
Step 1: Search and extract with Podcast Directory Scraper
ApifyForge's Podcast Directory Scraper searches Apple Podcasts (and optionally Spotify) by keyword, fetches every matching show's RSS feed, and pulls out the ownerEmail, ownerName, websiteUrl, episode frequency, active status, categories, and more. All in one run.
Here's what a typical input looks like for a PR agency doing guest outreach for a SaaS client:
{
"searchTerms": ["B2B SaaS marketing", "revenue operations", "demand generation"],
"maxResults": 100,
"country": "us",
"activeOnly": true,
"includeEpisodes": false
}
Setting activeOnly: true is important. According to Podnews, only about 440,000 of the 4.2 million total podcasts published an episode in the last week. Dead shows waste your outreach time and hurt your sender reputation. Filter them out.
Setting includeEpisodes: false speeds up the run and shrinks the output when you only need host contact data. You don't need episode listings for a pitch email.
Here's a trimmed example of what comes back per podcast:
{
"podcastId": 1482738706,
"title": "The Revenue Engine",
"author": "Pinnacle Growth Media",
"categories": ["Business", "Entrepreneurship", "Marketing"],
"episodeCount": 183,
"lastEpisodeDate": "2026-03-18",
"episodeFrequency": "weekly",
"isActive": true,
"websiteUrl": "https://www.revenueenginepodcast.com",
"ownerName": "Pinnacle Growth Media LLC",
"ownerEmail": "booking@pinnaclegrowth.com",
"feedUrl": "https://feeds.pinnaclegrowth.com/the-revenue-engine.xml",
"applePodcastsUrl": "https://podcasts.apple.com/us/podcast/the-revenue-engine/id1482738706",
"scrapedAt": "2026-03-25T09:14:37.000Z"
}
That ownerEmail field is the one you want. You also get the websiteUrl for step 3, the episodeFrequency so you know the show is actively publishing, and the author name so you can personalize your pitch.
Three keywords at 100 results each, with deduplication, typically returns 150-250 unique active podcasts. Cost is $0.05 per podcast on pay-per-event pricing -- so around $7.50-$12.50 per campaign. Compare that to Podchaser Pro at $599/month.
Step 2: Verify the emails you found
Not every ownerEmail is still valid. People change hosting platforms, let domains expire, or set up new booking addresses. Before you send a single pitch, verify.
ApifyForge's Email Pattern Finder does more than find patterns -- it includes built-in email verification with MX record checks and catch-all domain detection. Feed it the domains from your podcast list, and it tells you whether each email is valid, invalid, or risky. The catch-all flag is especially useful: some podcast hosting platforms accept mail to any address at their domain, which means an email can "verify" even if nobody reads it.
Alternatively, for bulk verification without pattern detection, use Bulk Email Verifier directly on the ownerEmail values.
This step takes about 30-60 seconds per domain. On a list of 200 podcasts, expect to cut 15-25% of emails as undeliverable. Better to learn that now than after you've sent 200 pitches and 50 bounced.
Step 3: Fill gaps with Website Contact Scraper
Here's where most podcast outreach workflows fall short. After the RSS extraction in step 1, you'll have maybe 50-80% email coverage. The remaining 20-50% of shows had blank itunes:owner tags or feeds that couldn't be fetched. Those aren't lost -- they just need a different approach.
Take the websiteUrl values from shows where ownerEmail came back null and feed them into ApifyForge's Website Contact Scraper. It crawls each domain, discovers contact pages and team pages automatically, and extracts:
- Personal and generic email addresses (separated and classified)
- Phone numbers
- Contact names with job titles
- LinkedIn, Twitter/X, Facebook, Instagram, and YouTube profiles
Enable deep scan mode and it'll probe 14 hidden page paths including /imprint, /contact, /about, /team, and /booking. European podcast websites are legally required to show contact info on their imprint page, so deep scan catches those reliably.
The Website Contact Scraper also has built-in email verification, same as the Email Pattern Finder. So the emails you get back are already checked. No extra step needed.
For the 200-podcast example, if 40 shows had no owner email, running 40 website URLs through the contact scraper costs about $6 (at $0.15 per domain) and typically recovers contact data for 30-35 of those 40 sites. That pushes your total coverage from 80% to 95%+.
What's the best format for a podcast guest pitch email?
The best podcast guest pitch email is 4-6 sentences: a specific reference to a recent episode, one sentence on what you'd discuss, your credibility in one line, and a direct ask. Podcast hosts receive 50-200 pitches per week according to PodMatch's 2024 booking data, so brevity wins.
I'm not a PR specialist, but I've talked to enough podcast booking agencies using ApifyForge to know what works and what gets deleted. Here are the patterns that get replies:
Reference a specific episode. Not "I love your show." Literally: "Your episode with Marcus Webb about ditching outbound at Series B made me rethink our PLG motion." The Podcast Directory Scraper returns episode titles and descriptions if you set
includeEpisodes: true-- use them.Pitch a topic, not yourself. Hosts don't care about your bio. They care about what their audience wants to hear. Lead with "I'd love to talk about [topic that fits their show format]" not "I'm the CEO of..."
One credential, one sentence. "I've built 170+ public actors on Apify's marketplace that process 50,000+ runs per month" is specific and verifiable. "I'm a thought leader in data automation" is not.
Make it easy to say yes. Include your availability, your headshot link, and a 2-sentence bio they can use for show notes. The less work for the host, the more likely you get booked.
How is finding podcast host emails different from LinkedIn outreach?
Finding podcast host emails targets people who have published their contact information inside RSS feeds and on public websites specifically for listener and media communication. LinkedIn outreach operates against platform Terms of Service and reaches people who may not want cold messages. Podcast hosts expect to be contacted.
That's the real difference, and it's worth repeating: podcast hosts want to hear from potential guests. They published that itunes:owner email precisely so people could reach them. That's a fundamentally different dynamic than cold-messaging someone on LinkedIn who hasn't opted into anything.
Some numbers to illustrate. Lavender's 2024 Cold Email Benchmark Report found that average LinkedIn InMail response rates dropped to 1.6% in 2024. Podcast booking agencies I've spoken with consistently report 8-15% reply rates on well-crafted guest pitches sent to verified host emails. That's a 5-9x difference.
The tradeoff is volume. LinkedIn has a billion profiles. Apple Podcasts has 4.2 million shows. But if your goal is getting on 10-20 podcasts that your target audience listens to, you don't need a billion contacts. You need 200 good ones with verified emails.
For teams running account-based marketing alongside podcast guest outreach, ApifyForge's B2B Lead Qualifier can score podcast hosts against your ICP criteria -- company size, industry, geography, tech stack -- so you're pitching shows where the audience actually matches your buyer.
Can you extract podcast host emails without coding?
Yes. ApifyForge's Podcast Directory Scraper runs entirely in the browser through Apify's Console. Type your keywords, click Start, and download the results as CSV or Excel. No code, no API, no RSS parsing. The actor handles the iTunes API calls, RSS feed fetching, XML parsing, and email extraction behind the scenes.
For teams that do want API access, here's a quick Python example that searches, extracts, and prints host emails:
from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("ryanclinton/podcast-directory-scraper").call(run_input={
"searchTerms": ["fintech founders", "banking innovation"],
"maxResults": 100,
"activeOnly": True,
"includeEpisodes": False,
})
for podcast in client.dataset(run["defaultDatasetId"]).iterate_items():
if podcast.get("ownerEmail"):
print(f'{podcast["title"]} | {podcast["ownerEmail"]} | {podcast.get("websiteUrl", "")}')
That's it. 12 lines. The API approach is what most PR agencies integrate into their CRM -- they schedule weekly runs on new keywords and pipe the results into HubSpot or their outreach sequencer via Zapier or Make.
Why do some podcasts not have an owner email in their RSS feed?
Approximately 20-50% of podcasts omit the itunes:owner > itunes:email tag from their RSS feed. This happens because some hosting platforms don't require it, some hosts intentionally remove it for privacy, and older feeds created before Apple enforced the field may never have included it. The percentage varies by niche -- business and technology podcasts average 70-80% coverage, while hobbyist and fiction podcasts average closer to 50%.
When ownerEmail comes back null, you have three fallback options:
Scrape the podcast website. Use Website Contact Scraper on the
websiteUrlfrom the scraper output. This is your highest-yield fallback -- most podcast websites have some form of contact information.Find the email pattern for the host's company. If you can identify the company behind the podcast from the
authororownerNamefield, run that domain through Email Pattern Finder. It detects the company's naming convention (first.last@, flast@, etc.) and generates a verified email for any name you provide. At $0.10 per domain, it's cheap insurance.Check the show notes on recent episodes. Some hosts include booking info in their episode descriptions. If you ran the Podcast Directory Scraper with
includeEpisodes: true, the episode descriptions are already in your dataset. Search them for "email", "book", "pitch", or "guest" to find hosts who publish their booking process there.
How much does it cost to find podcast host emails?
The full pipeline for finding and verifying podcast host emails for a typical outreach campaign of 200 targeted shows costs between $15-25 on ApifyForge, using pay-per-event pricing where you only pay for results.
Here's the breakdown:
| Step | Actor | Volume | Cost per unit | Total |
|---|---|---|---|---|
| Search + extract | Podcast Directory Scraper | 200 podcasts | $0.05 | $10.00 |
| Verify emails | Bulk Email Verifier | ~160 emails | $0.02 | $3.20 |
| Fill gaps (websites) | Website Contact Scraper | ~40 domains | $0.15 | $6.00 |
| Total | $19.20 |
That gets you 190+ verified host contacts for under $20. No monthly subscription. No per-lookup fees. Use ApifyForge's cost calculator to estimate your specific campaign before running.
Compare that to the alternatives. Podchaser Pro charges $599/month. Rephonic starts at $99/month. A virtual assistant doing this manually bills 8-10 hours at $25-50/hour for $200-500. And the manual approach doesn't include email verification.
What about using podcast booking platforms like PodMatch?
Podcast booking platforms like PodMatch, Podmatch, and Matchmaker.fm charge $49-199/month and limit you to their curated database, which is typically 10,000-50,000 shows. Direct outreach via email to hosts found through directory scraping covers the full 4.2 million show Apple Podcasts catalog with no monthly fee.
These platforms aren't bad. They're just limited. If you're doing 2-3 guest spots per year, a booking platform is fine. If you're a PR agency booking clients onto 10-20 shows per month, you need to work outside the platform's walled garden. The hosts who are easiest to book are already getting pitched by every other PodMatch user. The best opportunities are shows that aren't on any booking platform -- and those shows still have emails in their RSS feeds.
Direct outreach also lets you control the pitch entirely. No platform template, no character limits, no hoping the host logs into their PodMatch inbox. You send a real email to their real address and reference their actual content. That's how you stand out.
The complete workflow, start to finish
For PR agencies and B2B marketing teams doing podcast guest outreach at scale, here's the full pipeline I've built on ApifyForge:
Identify target keywords -- 3-5 terms that match the topics your guest expert can speak about. Be specific: "healthcare SaaS growth" beats "business."
Run Podcast Directory Scraper with those keywords,
activeOnly: true, andmaxResults: 100. Takes 2-4 minutes.Filter the results -- sort by
episodeFrequency(weekly and biweekly shows are most active), checkepisodeCount(shows with 50+ episodes are established), and verifyisActive: true.Verify the
ownerEmailaddresses -- run them through Bulk Email Verifier to catch dead addresses before you send.Fill gaps on shows where
ownerEmailis null -- feed theirwebsiteUrlinto Website Contact Scraper with deep scan enabled.For remaining gaps, run the host's company domain through Email Pattern Finder to detect their naming convention and generate a verified email.
Personalize and send -- reference a specific recent episode, pitch a topic (not yourself), and keep it under 6 sentences.
Schedule the Podcast Directory Scraper weekly on the same keywords and you'll catch new shows as they launch. Some of the best guest spots come from shows in their first 20 episodes -- the host is hungry for guests and the audience is growing fast.
One thing I'll say honestly: this pipeline works best for targeted outreach, not spray-and-pray volume. If you're trying to blast 5,000 podcast hosts with the same template, don't. You'll get blacklisted and burn the channel for everyone else. 200-500 highly targeted hosts per quarter, with personalized pitches, is the sweet spot.
ApifyForge catalogs 300+ web scraping actors and 93 MCP intelligence servers. The podcast outreach pipeline above uses four of them. You can compare all the contact scraping options on our comparison page to see which combination fits your specific workflow.
Last updated: March 2026
Top comments (0)