Product
Podcast links: spoken codes, show notes and the app that eats them
Podcast listeners cannot click. They hear a URL, remember part of it and type it later. What that means for code length, sponsor reads and per-episode attribution.
By Wasim Idrishi · Updated · 4 min read
Podcasting is the last channel where a URL has to survive being said out loud, remembered, and typed by someone whose hands are busy. Every other constraint on this site is about screens. This one is about memory.
It changes the answer. On a web page, a four-character code versus a seven-character code is a design preference. Spoken into headphones on a commute, it is the difference between a visit and a vague intention.
Design the code for the ear
Say it out loud before you register it. Three tests, all of which take five seconds.
Can it be misheard? Our alphabet drops 0, O, I and l precisely because "oh" and "zero" sound the same
and I and l look the same afterwards. A random code from a shortener that keeps them will be typed wrong by a
measurable fraction of your listeners.
Can it be held? Four characters, or better, a word. gc.mw/mail beats gc.mw/k7Rq for the same reason a phone
number with a pattern beats one without.
Does it need spelling? If you have to say "that is g-c dot m-w slash…", you have already lost the listener who was parking. Custom aliases on Pro exist for this: pick a word people can spell on the first hearing.
Say it twice, and put it in the same place every time
Listeners learn the shape of a show. If the newsletter link comes at the same point in every episode, regulars stop needing to hear it at all, they already know it.
Say it once early, once late. Retention curves mean a link mentioned only in the outro reaches a fraction of the people who heard the opening.
Show notes are less reliable than you think
Every podcast app renders show notes differently. Some strip links, some truncate after a few lines, some show only the first paragraph without a tap that many listeners never make. Whether a given listener sees your links depends entirely on an app you did not choose.
Treat show notes as a secondary surface. Put everything in them, certainly, but give the show-note version of a link its own code so you can see what fraction of your audience is actually reaching them. On the shows we have looked at, that fraction is lower than the hosts assume and varies enormously by app mix.
A worked example: making a sponsor read invoiceable
An interview show with three rotating sponsors gave each sponsor its own code per episode.
gc.mw/s1e42, gc.mw/s2e42, gc.mw/s3e42, spoken in the read, each pointing at that sponsor's landing page with
utm_source=podcast, utm_medium=host-read and utm_content=ep42 stored on the link.
Three months in, the host had a table: reads per sponsor, clicks per read, and clicks per thousand downloads. One sponsor's mid-roll consistently out-performed the same sponsor's pre-roll by a factor of two on identical copy. That became a pricing conversation, and the pricing conversation went the host's way because it was backed by numbers the sponsor could verify on their own side.
Download counts could never have produced that. Downloads measure the show; the code measures the read.
The permanent links stayed separate: gc.mw/news for the newsletter and gc.mw/join for the membership, unchanged
across 200 episodes. When the membership platform changed, one edit fixed every episode ever published, including the
ones from three years earlier that still get listened to weekly.
Dynamic ad insertion, and where this stops working
If your host inserts ads dynamically, the read a listener hears may not be the read in the show notes, and the code spoken in an episode from 2024 may be a sponsor you no longer work with.
Two habits help. Point retired sponsor codes at a short page explaining the read has ended rather than letting them 404, the traffic is small but the impression is bad. And keep a spreadsheet mapping codes to episodes and dates, because the export from your link dashboard will tell you what was clicked and not what was said.
Create the codes before you record
URL Shortener
Open the full toolMake the link, say it out loud, check it survives the three tests, then record. Fixing a spoken URL after publication means re-editing audio, which is the one thing on this page a short link cannot save you from.
The branded links page covers aliases and stored UTM fields, and link-in-bio covers the single page a show's permanent code should probably point at.
Questions people ask
How long should a spoken podcast URL be?
Four characters after the slash, and words rather than random codes. A listener hears it while driving, holds it for minutes and types it from memory. Every character past four costs you people, and every ambiguous character costs you more.
Why do show note links not get clicked?
Because show notes are rendered differently by every podcast app, and several truncate or strip them. Assume a meaningful share of your audience never sees them. The spoken link is the one that reaches everybody, which is why it deserves the good code.
How do I measure a sponsor read?
One code per sponsor per episode, spoken aloud, pointing at the sponsor's landing page with UTM tags stored on the link. That gives you a number you can put in an invoice, which vanity download counts never do.
Do I need a different link for each episode?
For sponsor reads and calls to action, yes. For the permanent things, the newsletter, the Patreon, the merch shop, use one code across every episode, so the back catalogue keeps working when the destination moves.
Sources
- Apple Podcasts: episode and show notes formatting · checked 5 September 2026
