How to Measure Podcast Traffic to Your Website in GA4 and Search Console

Podcast traffic to your website is tracked in Google Analytics 4 by tagging every show-notes and video-description link with UTM parameters, grouping those visits into a Podcast channel, and marking lead actions as key events. Search Console then shows how your episode pages perform in Google Search. GA4 counts website visits, not downloads, so your podcast host still reports listening.

This article is for hosts: you run the show and want to know what your own listeners do on your website. If you’re the guest on other people’s shows, the setup is different and lives in how to track podcast guest appearances. Getting podcast leads into your CRM is a separate job again. Here we stay inside GA4 and Search Console, using Google’s own help pages for every step.

What can GA4 measure about a podcast, and what can’t it?

GA4 can measure what podcast listeners do once they reach your website: which episode page they landed on, which link they clicked to get there, and whether they filled in a form. GA4 can’t measure plays or downloads, because those happen in the apps and on your podcast host’s servers.

Question	Where the answer lives
How many people downloaded or played episode 40?	Your podcast host’s stats, plus Apple, Spotify and YouTube dashboards
How many people clicked from episode 40’s show notes to my site?	GA4, from UTM-tagged links
Which episode pages get found in Google Search?	Search Console, Performance report
Did podcast visitors ask for a home valuation?	GA4 key events
Are more people searching my name since the show launched?	Search Console queries

Keep that split in mind before you set anything up. A month with fewer downloads and more valuation requests from podcast visitors can still be a good month.

How should a host tag show-notes links with UTMs?

A host should tag every link they control with the same three required values: the platform as the source, one fixed word as the medium, and the episode as the campaign. Google says UTM values are case sensitive and strongly recommends setting all relevant parameters when you set one, because missing ones show up as “(not set)” (GA4 URL builder help).

On your own show, the podcast is always the same, so the useful question is which platform the click came from. That’s the main difference from guest tracking, where each show gets its own source.

Parameter	Value for your own show	Example
utm_source	The platform where the link sits	apple, spotify, youtube, newsletter
utm_medium	Always podcast	podcast
utm_campaign	Episode number and short name	ep040-first-time-buyers
utm_content	Placement on that platform	shownotes, pinned-comment, chapter-link

A finished show-notes link for Apple Podcasts looks like this:

https://yoursite.com/buyer-guide/?utm_source=apple&utm_medium=podcast&utm_campaign=ep040-first-time-buyers&utm_content=shownotes

Send listeners to a real page that matches the episode, such as the guide you talked about or the episode page itself. A page built from the podcast episode page template gives them somewhere useful to land. Keep all values lowercase with hyphens, and write the pattern down so anyone who publishes for you uses it.

What about links people hear but can’t click?

A short address said on-air, such as yoursite.com/listen, catches listeners who never open the show notes. Redirect it to a tagged URL with utm_content=spoken. Without that, Google says GA4 records a session as direct traffic when no referral information is available (campaigns and traffic sources), and typed-in visits arrive exactly that way.

Why does podcast traffic end up as Unassigned in GA4?

Podcast traffic ends up as Unassigned when the medium you chose doesn’t match any of GA4’s default channel rules. GA4 sorts each session into a channel by fixed rules. Its Audio channel matches only when the medium “exactly matches audio”, and Unassigned is the value GA4 uses “when there are no other channel rules that match” (GA4 default channel group). So utm_medium=podcast lands in Unassigned by default, unless the source matches one of GA4’s site lists. A utm_source of youtube, for example, can be sorted into Organic Video, which Google describes as non-ad links on video sites like YouTube. Either way, your podcast clicks end up scattered.

You could switch to utm_medium=audio, but Google describes the Audio channel as visits “via ads on audio platforms (e.g., podcast platforms).” If you also buy ads on other shows, those paid clicks and your own show-notes clicks would share one channel. A cleaner fix is a Podcast channel of your own.

How to build a Podcast channel in a custom channel group

1. In GA4, open Admin, then under Data display click Channel groups.
2. Click Create new channel group. GA4 starts you with a copy of the default group.
3. Name it something like “Channels with Podcast.”
4. Click Add new channel, name it Podcast, and add a condition: Medium exactly matches podcast.
5. Click Reorder and drag Podcast to the top of the list, so YouTube clicks don’t fall into Organic Video first. Google says traffic goes into the first channel whose definition it matches.
6. Click Save group.

Google’s custom channel groups help page says standard properties can have two custom groups in addition to the default one, and that custom channel groups can be applied to reports retroactively. Your past tagged visits show up under Podcast as soon as you pick the new group in a report.

Which key events should a podcast website track?

A podcast website should track the few actions that mean a listener became a lead or moved closer to one. Marking them as key events lets every traffic report show leads by channel, including your new Podcast channel.

Good candidates for an agent’s site:

• Contact form submitted
• Home valuation or seller guide requested
• Buyer consultation booked
• Newsletter or market report signup
• Click on your phone number or email link

Google’s key events help page explains the steps: in Admin, under Data display, click Events and select the star next to an event GA4 already receives. You can also create a new event and toggle Mark as key event. Standard properties can mark up to 30 events as key events. The event itself has to exist first, so if your form doesn’t send one, ask whoever runs your site to add it.

How do you measure episode pages in Search Console?

You measure episode pages in Search Console by filtering the Performance report to the folder your episodes live in. If every episode sits under /podcast/, one filter separates podcast search traffic from the rest of your site.

Google’s advanced filtering help page gives the steps: click + Add filter, choose Pages, choose URLs containing, and enter /podcast/. Google says the match isn’t case sensitive but is otherwise exact. For episode pages spread across folders, use Custom (regex) with a pattern such as (podcast|episode). The same page explains how to compare two date ranges, such as this quarter against last quarter.

Then switch to the Queries tab with the filter still on. That list shows the searches your episodes appear for. It’s the best source of topics for future episodes and of titles worth rewriting.

Should you link Search Console to GA4?

Linking Search Console to GA4 is worth the five minutes because it puts search data next to your key events. Google says the link adds two reports, Google Organic Search Queries and Google Organic Search Traffic, and that the Search Console collection is unpublished by default, so you publish it from the Library (connect Search Console to Google Analytics). The landing-page report then shows which episode pages bring searchers who go on to contact you. Google also says a web data stream can link to only one Search Console property, and that the data arrives about 48 hours after collection.

For tracking searches for your own name as the show grows, use the method in measuring branded search from podcasting. It works the same for hosts.

What should a monthly podcast traffic report include?

A monthly podcast traffic report should fit on one page and answer three questions: did listeners visit, did they act, and did search find the episodes. Pull these numbers on the same day each month.

Metric	Where to find it	What it tells you
Sessions in the Podcast channel	GA4 Traffic acquisition, with your custom channel group	How many listeners clicked through
Sessions by utm_source	Same report, secondary dimension	Which platform sends visitors
Top podcast campaigns	Session campaign dimension	Which episodes drove visits
Key events from the Podcast channel	Same report, key events column	Whether visits turn into leads
Clicks and impressions to /podcast/ pages	Search Console, URLs containing filter	Whether Google sends people to episodes
Top queries for episode pages	Search Console Queries tab	Topics and titles that work
Downloads per episode	Your podcast host	Listening, for context

Add a notes line for anything else running that month, such as a listing launch or a mailer, so you don’t credit the podcast with someone else’s result.

What should you do with the numbers?

You should use the numbers to change one thing a month: a title, a call to action, a destination page or a topic. Measurement only pays off when it changes what you publish. Episode pages that earn impressions but few clicks need better titles and descriptions, which show notes written for search help with. Platforms that send visits but no key events need a better destination page. The podcast SEO guide for real estate agents covers what to fix on the page itself, and how a real estate podcast earns backlinks covers getting other sites to send you visitors.

If the measurement is easy but the weekly publishing isn’t, Icons production that publishes each episode with an SEO-optimized website article handles guest booking, editing, publishing, promo clips and website articles. Ardor SEO is the parent company of Icons of Real Estate. Give its team your UTM pattern so the reports stay consistent.