11 tips for sharing URLs in your podcast.
Thank you for joining me for The Audacity to Podcast.
I'm Daniel J. Lewis.
There comes a point in every podcast when it's necessary to say a URL.
If for nothing else, at least your podcast's own home on the internet and you should have
a domain for your podcast.
Beyond your podcast website, you might also want to share affiliate links, resources,
episode notes, past episodes, sponsors, and more.
So here are 11 tips for how to share URLs effectively in your podcast.
If you'd like to follow along with the notes for this episode and get several of the links
that I mention in this episode, then get to the notes a simple tap or swipe away inside
of your podcast app or go to theaudacitytopodcast.com/sharingurls.
Please note that I do mention several products in this episode and in the notes and I link
to them and several of them I have affiliate relationships with and so those are affiliate links.
I earn something if you purchase through those links and only if you purchase through my links.
But nonetheless, I recommend things I truly believe in regardless of earnings.
That disclosure out of the way, let's jump into this.
Number one, speak as few URLs as possible per episode.
Every URL is essentially a call to action. That could be where to follow you on social
networks, the episode's webpage, your support page, where to send feedback, and much more.
And calls to action are most effective when there are very few of them, but they are reinforced
multiple times. This is why you'll hear most ads give the call to action, like visiting
a website, at least three times. It's part of the marketing lie. Think someone gets fired
if they don't mention it three times. They say it again and again and again at least
three times. That's a good practice for your podcast too. But with all of the URLs
you might want to share, you'll start overwhelming your audience and making each URL less memorable.
For this reason, I recommend that you say as few URLs as possible, maybe only one, and
that's what you say and speak in your podcast, not what you actually link to from your site,
what you're saying in your audio or video podcast.
But don't make it the same URL across all your episodes.
For example, if I kept telling you to get the links for this episode at theaudacitytopodcast.com,
that works best only when this is my latest episode.
But the more episodes I publish, the more episodes get shifted down my website's front
page and eventually get pushed off that front page.
So if you're looking for the notes for this episode and all I've done is told you get
the notes at theaudacitytopodcast.com and it's years later, you have no idea where to get
the notes.
Except somewhere on theaudacitytopodcast.com.
That doesn't work.
Thus, I recommend having a unique URL for each episode that will always take your audience
to the correct information, whether they listen immediately or 5 years later.
This is easy to do on WordPress with my favorite plugin, PrettyLynx Pro, or you might have
something else that allows you to create a friendly, speakable URL, a single URL for
that episode and then that episode's webpage can point to everything else that you need
to link to.
That's number one.
Tip number two, defer to your chapters or episode notes.
If you follow tip number one, then your single URL should be your episode webpage, as I started
to touch on.
There, on that webpage, you can include all the things you want your audience to get or
4C, that could be images, videos, links, buttons, and more. Make sure this stuff, at least the
links, appear in your episode notes within the podcast apps too. Because many publishing
tools and podcast apps follow different standards, there's no one right way to do this. Well,
there is actually, but not all the podcasts support that one right way. So the best thing
to do would be to ask the maker of your publishing tool, whether that's your website publishing
system, your podcast hosting provider, whatever is making your RSS feed, ask the people who
make that how to ensure your links in your episode notes show in your top podcast apps.
So if Spotify and Apple are top in your downloads, then you want to make sure that those links
appear in those apps. And then those people can give you the right guidance for your situation
on their publishing tool. But the most universal case is, unfortunately, that a full, ugly
URL will work more often than an HTML hyperlink. The full, ugly URL would be "https://theaudacitytopodcast.com"
instead of the hyperlink, which you probably won't type this code into your notes, but
whatever kind of system you're using if it lets you bold text and make bullet points and hyperlinks,
it will put this HTML code in there that is HTML stuff. It's an ATAG, an href equals quotation
mark, the URL, the quotation mark, some text that's being hyperlinked, and it's HTML code.
If you really want to see what I'm talking about, you can look at the notes for this episode at
theaudacitytopodcast.com/sharingurls or get to that a tap or swipe away inside of your app.
Check out how Knickknack News does this for a great example of actionable episode notes.
It's also, by the way, a really fun podcast I highly recommend.
I've got the link to them in the notes for this episode.
Their notes are actually not effective for SEO on their website or in the podcast apps,
but podcast apps don't really search descriptions anyway.
But their episode notes are excellent for engagement inside the podcast apps.
Not so much on the website, but in the podcast apps.
It's great.
The hosts of that fun show, Alex and Anthony, often share things you will want to see or
read for yourself.
Could be a picture of a bear, or reading about an ice cream flavor, or watching a video,
or anything like that that's interesting along the lines of what stories they're
talking about for that episode.
And they do that in very simple and actionable ways in their notes.
I've copied an example from one of their episodes in the notes for this episode, but
just to give you a brief overview, they have two headlines for this main section that I've copied.
There's "Anthony's Stories This Week" and "Alex's Stories This Week" and under
Anthony's stories, it's a simple list with one or two keywords that describe the story,
like "ketchup" and then there's a link to businesswire.com and then there's "ice
cream" and a link to mensjournal.com.
for Anthony's stories with what links he found. And then for Alex's stories, for
what she is sharing, she has Beard with a link to UPI.com and Zelda with a link to TheVerge.com.
And these links aren't only to those top domains, but they are to the specific pages
for these stories. You can check that out in the notes for this episode. And those are
the ugly URLs they're sharing, but that does work. As ugly as it is to see a full URL,
It works more often than other methods do.
And it's highly actionable.
If you're listening along to their podcast, then these simple notes will make total sense
to you and the notes don't get in the way of what you want.
While you're listening to Anthony talk about ketchup, you can look right there in the notes
and you see there's the link for the ketchup story.
You don't have to see the full headline.
You don't need paragraphs as text.
You just want the link to the story that he's talking about.
Now depending on how you're communicating around the URLs you want to share, you might
also want to consider using chapters.
Both legacy chapters embedded in MP3 files and podcasting 2.0 chapters in a separate
episode metadata file, and that's in JSON format if you're interested in that technical stuff.
Both of these formats support adding a single URL per chapter.
In knickknack news, Alex and Anthony spend several minutes on each story so each story
would be perfect as a single chapter per story.
And then they could add the relevant URL to each chapter.
But this gets complicated when you have multiple URLs within a single context.
For example, if I share a list of my favorite podcast hosting providers, which are currently
Captivate, Buzzsprout, and Blueberry, I can't add multiple URLs to the same chapter.
least not yet. So this is where you would want to defer that list of links to your episode
notes because it wouldn't be reasonable to have a chapter for each of those links when
I just blazed through those and then you'd see those chapters go by so quickly it might
be difficult for you to actually go back to the chapters and get the link that I mentioned.
And it would be a mess for me to manage as well to put those into individual chapters
for each URL that I mention, because you can't put multiple URLs in a single chapter.
However, I'm pushing hard for Podcasting 2.0 to turn our current podcast chapters into
super chapters.
That's a term coined by Dovi Das from RSSBlue.com.
Super chapters would allow you to use a single chapter to display rich content, including
but not limited to things like a gallery of images, a block of text, a numbered or unnumbered
list, videos, or even multiple links for a single chapter. Essentially, you could put
whatever you normally put in your episode notes also in your chapters, but then your
audience is getting that only one chapter at a time, or they're seeing something that's
far more actionable. So instead of paragraphs of text around a single link, they see only
that single link with maybe a brief headline, an explanation, or something like that.
Then I could make a single chapter for my favorite podcast hosting providers and that
one chapter can link to the multiple options and there would be the three different links
for those three different hosting providers.
However, even if this is adopted within the Podcasting 2.0 standard, I urge you to maintain
backwards compatibility.
That's where your episode webpage comes in.
If you're worried about your audience getting lost in a long episode webpage, there's a
cool thing you can do.
You could actually link your chapters to specific sections of your page by adding an anchor
or ID to each heading in your notes.
And then link each chapter to that anchor in the URL.
And that would simply be with a hash or a pound sign at the very end of the URL and
then whenever that anchor is.
So for example, for this episode it's https://theaudacitytopodcast.com/sharingurls#2 and
that links to this actual section that I'm talking about right now in my notes.
And in fact, for this episode, and maybe only this episode, maybe I'll do this again in
the future, we'll see.
For this episode though, every one of these chapters will take you to that specific section
of my notes on my website.
If you click on the chapter link for that section.
That's something that you could do that takes people directly to that relevant section on
your site.
You have to look at whatever publishing tool you're using though to see how easy it is
to add that.
Inside of WordPress, I can simply click on the heading and then there's in the little
block editor section because I like the Gutenberg editor and I think you should too.
But in the block section, there's an advanced drop down and there is a spot where I can
enter text for an HTML anchor.
And it says enter a word or two without spaces to make a unique web address just for this block.
I can do that with headings or images or paragraphs or lists or anything like that.
I'm doing it with just my headings.
it out inside of your app and see what you think about it and see if it actually works
inside of your app.
I think it will.
So try it.
You could do that kind of thing then so each chapter is linking to a section in your notes
where then that section has your multiple URLs that you've mentioned.
So that's number two, really long one, I promise they're not all this long, and that's
defer to your chapters or episode notes.
Number 3. Never say "https://" or "www.". It's not the 90s anymore. It's been literally
decades since anyone needed to type "http://" or "https://" in their browser. Also, most
websites don't actually use "www." at all in their domain anymore. Or if they do, like
YouTube still does, you can usually still get to the correct place without typing the
www dot. Which, by the way, has to be the worst abbreviation ever because saying www
is actually more syllables than what it's an abbreviation for. World Wide Web. Might
as well just say World Wide Web dot whatever the domain is dot com or anything like that.
You don't have to do that, most of the time, but you must test this first.
I have run into a couple of badly configured sites that needed the www dot because they
weren't even forwarding their domain without the www dot.
So if you typed the domain without it, the website wouldn't work.
But that's a very, very rare case.
And I haven't used www for any of my domains in many, many years. Decades.
And if I hear you say www.theaudacitytopodcast.com, well I won't come after you.
But don't be surprised if poetic justice comes after you by making your neighbor mow
his yard right when you want to record your podcast.
Just don't say www.
And please, definitely don't say https://.
Unless you have to be explicitly clear because you talk code in your podcast.
Like when I've mentioned it in here, it's because I am being clear of this is what the
code says.
But if you're telling people to visit a website, you don't have to say https://www.
And that will save you so much more time.
Number four.
Simplify your URLs.
If you do speak a URL in your podcast, make it as simple as possible.
I remember a commercial many years ago, I think maybe from the late 90s or early 2000s
from Epson, you know, one of the biggest printer manufacturers who should know better than this.
The only thing I remember about their commercial was because I, as a teenager, recognized how
bad their call to action was.
I think the URL they spoke was www.ebson.com/what-if-you-could.
And yes, they actually spoke it that way, saying "dash" for every "dash".
What dash, if dash, you dash, could.
I just want to turn it into something that I just keep adding to it.
dash if dash you dash could make dash a dash better dash you are dash l dash.
You can just start inserting dashes all over the place. Don't do that. Please.
Even if you have to combine multiple words in order to speak something in your podcast,
try to avoid having to say dashes. Just don't make it so complicated. Simplify it.
I highly recommend that any URL you speak should reinforce your brand. So make it a slash keyword
URL on your own domain. Consider the speakable URL for this very episode, theaudacitytopodcast.com/sharing-urls.
It's not sharing dash URLs, it's just sharing URLs. Now when you visit that, that's simply
a redirect that takes you to a full URL that does have all of those dashes and a lot more
words in the URL. That's fine. That's for SEO and that's the way that my publishing
system makes those URLs, but I've made a shortened URL that's friendly, it's speakable,
it's more memorable.
This also goes for external resources too.
Instead of sending people to something like Patreon.com/whatever your slug is for your
podcast, send them to a /Patreon 307 or 302 temporary redirect on your own domain.
Or even better, remove that third-party brand name completely.
I've done an episode about not saying brand names in your podcast, and make it a generic
URL, like /support or something meaningful to your audience, like /hero/whatever it is
that's special to your audience.
This not only reinforces your brand, but it also makes your calls to action future-proof
because you can redirect the URL whenever you want, especially if it's a temporary
redirect, and to wherever you want, even to a completely different brand. Like, what if
you wanted to stop using Patreon and switch to a membership on your own website? Then
your audience doesn't need the brand Patreon and it's not accurate anymore. So if you
kept sending them to patreon.com/somethingorother, then that's going to be a broken link. Or
if you send them to your own website/patreon, well you're not using Patreon anymore. Send
them to something that's more generic and that reinforces your brand.
To listen to that previous episode I did about not using brand names in your podcast, get
the link in the episode notes at theaudacitypodcast.com/sharingurls.
Number five, make friendly URLs that make sense.
Whether you're sending your audience to your own episode webpage, an affiliate product,
or somewhere else, ensure the URL makes sense for that thing.
brand names if possible, or wherever practical.
And this is part of why I stopped using episode number URLs for my own podcast a long time ago.
Firstly, I realized that my episode numbers didn't actually matter when I was doing
an episode about whether episode numbers matter.
Listen to that episode, the link is in the notes for this episode.
And secondly, even I, the creator of my own podcast, was having a hard time remembering
which numbers went with which episodes. So it was safer to assume that you and the rest
of my audience would have an even harder time remembering what number went with what episode.
Now I create a redirecting short URL for each episode to match the content of that episode
by making those URLs keyword focused. Like how this episode's URL is theaudacitytopodcast.com/sharing
"sharing URLs". And if you look at the image that goes along with this episode, you'll
see that sharing URLs is part of the big text on that image too. That's the other thing
I do is I try to make those URLs match or be similar to that big text so it's all reinforcing
the same text instead of /391, which is the pointless number of this episode by the way.
This is easy to do, again, with PrettyLinks Pro, a plugin that I love for WordPress. You
You can make as many temporary and permanent redirects as you want, and all using your
own WordPress-powered website.
Even many third-party website providers that work with podcasting, like Podpage or some
of the websites you get through podcast hosting providers like Captivate, will let you create
your own redirects in their system.
But what I really like about PrettyLinks Pro, and specifically the paid version, the Pro
version, is that I can create the PrettyLink right in my post editor or page editor.
So that link goes live when I publish, reducing how many things I need to do away from the
post or page editor.
That's number five.
Number six, say slash, not forward slash or backslash.
And you can call this a pet peeve if you want, but it's simply slash, not forward slash.
Forward slash is actually redundant, like pin number, ATM machine, and please RSVP.
And it's definitely not a backslash.
That's completely wrong.
Just saying forward slash is redundant, backslash is incorrect.
Just say slash.
People are familiar enough with what a slash is.
It's been around for a long time.
Number seven.
Slow down and speak clearly.
Even though URLs don't have spaces, that doesn't mean you should speak like they don't have spaces.
It can be okay for you to say your own URL a little bit faster, not intentionally faster,
but just at a natural pace when it exactly matches your brand that you've already said
several times, and here's the key, within the context of your podcast.
For example, the website for The Audacity to Podcast is, duh, theaudacitytopodcast.com.
Brilliant, right?
And I'm saying that in my own podcast where you've already heard me say that domain several
times and you've heard me say The Audacity to Podcast several times.
You can look at your podcast app right now and probably somewhere on the screen it says
The Audacity to Podcast.
So my branding is really strong there.
The branding is strong with this one.
So I don't have to worry so much about saying that URL slowly.
But what comes after the slash, that's where I might need to be more intentional in this context.
So it's theaudacitytropodcast.com/sharingurls.
So see there I slowed down when I said sharing URLs.
But when speaking any different URL, and especially if you're in a different context, speaking
your own URL in front of a new audience or in a different context, make sure you say
Say it slowly and clearly enough so they can know what you said.
In other places I don't say theaudacitytopodcast.com, I say theaudacitytopodcast.com.
A little bit slower, emphasizing the branding a little bit more.
Also that context helps them know what word I mean when I say "to".
A little more on that in just a moment.
Check your podcast transcripts too.
They can be a good indicator of whether you're clearly speaking the URL and saying it slowly
enough. And also, by the way, check your transcripts for any URLs that you mention so that you
can fix any of them that were transcribed incorrectly. Now, that doesn't always mean
if the transcript is wrong that you set it wrong. It's just a good indicator, potentially.
Number eight. Clarify or avoid ambiguity. There's a chance that you'll run into some
confusion with some URLs you might speak. For example, does the domain have the preposition
4, F-O-R, the spelled number F-O-U-R, the numeral 4, just the digit that is, or something
crazy like the Roman numeral 4, which would be I-V. An interesting corporate example of
this as a failure is Fifth Third Bank. Ironically for a bank, the secure URL, if you actually
typed it this way, "https://" which many browsers now just assume it's "https"
and then type the words "5th3rdbank.com".
That doesn't actually work, at least at the time of this recording.
But if you typed in "http://" without the "s", so the non-secure version, "/5th3rd"
spelled out dot com and if you type in https colon slash slash www dot fifth third spelled
out words there dot com those do work. However the actual website and the redirection destination for
those urls that actually do work is https colon slash slash www dot 53 dot com. Okay yeah I know
it's actually fifth third dot com but you look at it and it's 53. We all know it's 53. What's the
the website for Fifth Third Bank, it's 53.com. But I hope no one types the ordinal versions
of the numbers like 5TH3RD.com because that's a completely different website. And right
there on the front page it says "Online since 2000". I kind of wonder how long has
Fifth Third Bank been online? But I digress.
There are three different ways I think that you could avoid sending people to the wrong URL.
First, consider clarifying any ambiguity, such as by spelling it when the context doesn't
make it obvious.
For example, I hear Clinton say this all the time in his podcast, "ComedyForecast.com,
that's the number 4."
Sometimes the context makes it obvious, though, which way you mean.
But like in the case of Comedy Forecast, is that the number 4?
Is that F-O-R?
Is that F-O-U-R?
Or is it maybe F-O-R-E like forecast a weather forecast. It's comedy the number 4 cast.com.
That's the number 4. Maybe he has the trademark on that by now.
You could also create fallbacks to handle other versions. Like yes, I have the audacity
number 2 podcast.com. Or avoid the ambiguity altogether such as avoiding any single digit
numbers or ambiguously spelled words like g-r-a-y and g-r-e-y for grey. And this might
come down to knowing what some of those other spellings are which might not be completely
obvious because sometimes it's a British English vs. American English kind of thing, or sometimes
it's just a misunderstanding of which way it's spelled. Like "lead" is it l-e-d or
or LED. You need to make sure that you solve that ambiguity problem you might have.
Number 9. Be careful with top level domains that aren't .com. A top level domain or
TLD is the .com part of the domain. You probably also know .org, .net, .edu, and .gov. But
there are hundreds of other TLDs. Some of them are full words, like .photography. While
it can be fun to have one of those modern TLDs, they might be expensive, some of them
really are, and they might be confusing to non-savvy internet users who probably assume
a dot com for everything and also probably enter all their URLs into the Google search
field. Consider your audience in that case. Is your audience tech savvy? Then it's probably
okay to have a really cool top level domain like dot show or dot whatever. Consider the
podcast That Story Show, for example. They have both ThatStoryShow.com, which they've
used for many years, and more recently ThatStory.show. The host, James Kennison, now speaks the .show
domain more often than the original .com domain, but he still has and uses the longer .com
version as that backup. The more creative you get, the more it will cost you in both
the domain itself and likely how many alternatives you might have to grab to ensure anyone who
mishears you still gets to the right website and it doesn't get stolen and used for malicious
purposes which can happen. And you might not have any defense against that unless you actually
trademark your podcast name and that's part of your domain and then you could potentially
go after some of those malicious websites if they're infringing on your trademark.
But if you don't have a registered trademark, and if you don't grab those domains, then
you're at the mercy of some of the trolls on the internet.
Number 10.
Beware case sensitivity.
Case sensitivity is still weird on the internet.
It really depends on the server configuration running the website.
A little flashback here.
When I started my first website, I think around the year 2000, maybe even 1999, I can't
remember exactly.
Actually, I think even before then.
Because I remember having my first webpage was "Angel Fire Geocities" or something
like that.
But when I started my first official website, I specifically wanted a Windows server instead
of a Linux server because I didn't want to mess with capitalization issues that I
knew that Linux servers could have.
Oh my youthful mind and completely oblivious to how some stuff works and should work.
Domains and subdomains are case insensitive.
So you can capitalize TheAudacitytoPodcast.com however you want and it's still handled
the same way.
You can even all caps it.
You can all caps the dot com part.
Anything like that.
It's all handled the same way.
But anything after the domain could be case sensitive in that URL.
For example, capitalization actually matters with bitly links.
Like bit.ly/a is a different link from bit.ly/a.
And it matters on some other website servers and hosting configurations too.
You might just have to check it to see which way does it work.
And actually when I launched podgagement, I didn't realize that some people had saved
slugs like followthepodcast.com/audacity. I didn't realize that some of them had some
interesting capitalizations in there and the system was not configured to handle all the
different capitalizations that could have been in there. I had it set so they couldn't
make weird capitalizations, but if they already had one from the old My Podcast Reviews days,
that wasn't quite handled correctly. I've fixed that since then, but you have to be
aware of that kind of thing. Just assume anything that comes after the domain is case sensitive.
It might not be, but assume it is. So test whatever you do, test it. And if it is case sensitive,
then please don't tell your audience that. Don't tell them specifically to capitalize the URL.
Just send them to a URL that's not case sensitive because you don't want to have to get into those
specific instructions like that. Keep it simple. And then number 11, always test your URLs before
you share them. Make sure it actually works and it works in the way that your audience will hear it
and that they will type it in. Type it with the www dot and without it. Make sure your redirects
are functioning and if your friendly URLs aren't activated until you publish your episode, like all
all of my own slash keyword format URLs work from PrettyLinks Pro for my podcast episodes,
make sure to test that link after you publish your episodes. I don't know if it's a particular
aspect of my publishing workflow or what, but sometimes an episode of the Audacity podcast
goes out and that slash keyword URL does not work initially. So I have to go in after the
episode automatically publishes at its particular time and I go in and quickly make that link
work. I don't quite know what it is that causes that, whether it's a workflow thing, or maybe
I forgot to type something in, or maybe it's something else related to maybe a plugin conflict.
I don't completely know, and it happens rarely enough that I don't really diagnose to fix
the problem completely. I just test every time. And you should test every time too.
Whatever URL, especially URLs that you speak in your podcast, make sure that they work.
And the more important they are, the more you want to periodically go back and check
to make sure that they still work.
So in review, go to theaudacitytopodcast.com/sharingurls to get all the links that I mentioned, plenty
of links, and the notes for this episode and see some of the examples.
And these 11 tips that I've shared are, number one, speak as few URLs as possible per episode.
Number two, defer to your chapters or episode notes.
Number 3, never say https:// or www. Number 4, simplify your URLs.
Number 5, make friendly URLs that make sense.
Number 6, say slash, not forward slash or backslash.
Number 7, slow down and speak clearly.
Number 8, clarify or avoid ambiguity.
Number 9, be careful with top level domains that aren't .com.
Number 10, beware case sensitivity.
And number 11, always test your URLs before you share them.
If you've appreciated this episode, this has helped you or you think it might help someone
else, I would love it if you would share this episode out with someone else.
Go to theaudacitytopodcast.com/sharingurls to share this episode out or maybe it's a simple
tap inside of your app.
Quick visit to the community corner.
Thanks for the 5 star review on the episode that I did previously, 11 Warnings About Using
AI in Content Creation.
That 5 star review is from Rich Bennett using GoodPods and he said thanks for another informative
episode Daniel.
Well thank you for that kind review Rich.
Check out the notes by the way and I've got an image in there of the review.
It's a really neat image.
That is not something that I manually took a screenshot of anything and copied and pasted that.
that I downloaded straight from my own app, Podgagement.com, where now you can make images
of your individual ratings and reviews, well the non-anonymous ratings and reviews.
You can make those easily with Podgagement.
You can also make other cool images to embed on your website that show off your social
proof and much more.
It's the image maker tool that's brand new inside of Podgagement.
I love it.
Really excited about what that opens up for the future.
You can check out an example of that in the notes for this episode.
And try it yourself over at Podgagement.com.
Also thanks for the 1000 sats from Dwev who, as you might remember, I kind of questioned
is it Dweev, is it Dwev, is it something else?
But it is Dwev.
And he said, "Yep, you're pronouncing it perfectly."
Thanks Daniel.
And also thank you for the streaming satoshis from Brian Insmeiner, Dave Jackson, Dwev,
and newcomer Gardas for past episodes streaming those satoshis to me.
If you value The Audacity to Podcast, would you consider ascribing a number to that value
and sending that back to the podcast?
Either through fiat currency, there's a PayPal link, there is the option to send value
back through streaming satoshis or a boostergram if you're in a modern podcasting 2.0 app,
or just purchase my products if you want to support what I do.
It's all at theaudacitytopodcast.com/sharingurls.
Now that I've given you some of the guts
and taught you some of the tools,
it's time for you to go start and grow your own podcast
for passion and profit.
I'm Daniel J. Lewis from theaudacityyoutubepodcast.com.
Thanks for listening.
[Music]