1
00:00:00,000 --> 00:00:13,120
How to fix duplicate listings in Apple Podcasts or the other naughty proxy-based podcast apps.

2
00:00:13,120 --> 00:00:17,720
Thank you for joining me for the Audacity to Podcast. I'm Daniel J. Lewis. If your podcast

3
00:00:17,720 --> 00:00:23,920
is listed twice or more in Apple Podcasts or another podcast app or directory, stop.

4
00:00:23,920 --> 00:00:28,880
Don't do anything about it until you listen to this episode. You will want the notes for

5
00:00:28,880 --> 00:00:33,360
this episode. You'll probably want to review them because I know that some of this is unfortunately

6
00:00:33,360 --> 00:00:39,160
more complicated than it needs to be and I'm going to try to explain it as best I can.

7
00:00:39,160 --> 00:00:43,040
Some of it you just might not fully grasp unless you're actually in this situation

8
00:00:43,040 --> 00:00:47,560
and trying to work your way through it. But here's the big key. Even if you're not in

9
00:00:47,560 --> 00:00:52,640
this situation right now, this is what you need to do to avoid this problem from happening.

10
00:00:52,640 --> 00:00:57,800
Do not resubmit your podcast if it's already listed. I'll talk about that a little more

11
00:00:57,800 --> 00:01:02,520
toward the end of this episode, but that's the big important takeaway. It's even bold

12
00:01:02,520 --> 00:01:07,520
in my notes for this episode. Do not resubmit your podcast if it's already listed. So

13
00:01:07,520 --> 00:01:11,020
if you want to follow along with the notes for this episode or review them later when

14
00:01:11,020 --> 00:01:14,660
you need them, or maybe you need them right now, I hope you're not in this situation,

15
00:01:14,660 --> 00:01:22,080
but please go to theaudacitytopodcast.com/fixduplicates or the notes are a simple tap or swipe away

16
00:01:22,080 --> 00:01:24,000
inside of your podcast app.

17
00:01:24,000 --> 00:01:27,640
First, how do duplicate podcast listings happen?

18
00:01:27,640 --> 00:01:31,200
There are two common reasons you might end up with a duplicate listing of your podcast,

19
00:01:31,200 --> 00:01:35,100
either by your own actions or by some kind of automation out there.

20
00:01:35,100 --> 00:01:40,120
Reason number one, a secondary feed was automatically discovered and indexed.

21
00:01:40,120 --> 00:01:44,920
You might have used several different podcast publishing tools like your own website, powerpress,

22
00:01:44,920 --> 00:01:47,320
multiple podcast hosting providers and such.

23
00:01:47,320 --> 00:01:51,240
Or you might have used some automation tools for cross-posting your episodes to multiple

24
00:01:51,240 --> 00:01:58,200
places like Spreaker, AudioBoom, PodPage and such. Or you used a feed proxy to mirror and

25
00:01:58,200 --> 00:02:03,160
re-host your RSS feed for performance or extra features or anything like that, like FeedBurner

26
00:02:03,160 --> 00:02:07,820
or PodcastMirror. And to learn more about what feed proxies are, I did a whole episode

27
00:02:07,820 --> 00:02:13,160
about that previously and talking about the dangers that iOS 14.5 introduced. And I will

28
00:02:13,160 --> 00:02:17,280
talk more about that in this episode too because it's totally relevant. It's what's causing

29
00:02:17,280 --> 00:02:20,640
this problem with Apple Podcasts. But I've got a link to that previous episode with more

30
00:02:20,640 --> 00:02:27,280
information in the notes for this episode at theaudacitytopodcast.com/fixduplicates.

31
00:02:27,280 --> 00:02:32,280
Any of these tools might have created another RSS feed for your podcast and may even be

32
00:02:32,280 --> 00:02:39,320
actively updating it. They could even be serving the exact same feed from the exact same publishing

33
00:02:39,320 --> 00:02:48,880
tool but from multiple URLs, like an HTTP version and an HTTPS version. Same feed, just

34
00:02:48,880 --> 00:02:57,120
different protocols there, HTTP and HTTPS. There might also be a case where there's a www and a

35
00:02:57,120 --> 00:03:05,120
non-www version. Or it might be something like a subdomain like feeds.podcasthostingprovider

36
00:03:05,120 --> 00:03:11,280
and then now it's feeds2.podcasthostingprovider or anything like that. There could be multiple

37
00:03:11,280 --> 00:03:17,120
reasons that you might have the multiple RSS feeds from some of the different tools that you've used.

38
00:03:17,120 --> 00:03:22,560
Podcast Index, Google Podcasts, may it rest in peace. And maybe a couple of other systems

39
00:03:22,560 --> 00:03:28,480
search the web looking for podcast feeds to include and they'll often find those duplicates.

40
00:03:28,480 --> 00:03:34,560
Podcast Index has a fairly smart deduplication process but it still gets some things wrong and

41
00:03:34,560 --> 00:03:40,000
adds some duplicates here and there. But Google Podcasts was a little annoying with how they would

42
00:03:40,000 --> 00:03:45,360
do it. At least they didn't create duplicates. But what they would do is often switch to the

43
00:03:45,360 --> 00:03:50,960
newly discovered feed, even if it was only a redirect, and then require you to verify

44
00:03:50,960 --> 00:03:56,800
ownership of that new feed before you could switch back to your desired feed. This created

45
00:03:56,800 --> 00:04:02,880
the potential for someone else to steal your podcast in Google Podcasts. It was a horrible

46
00:04:02,880 --> 00:04:08,000
way that they did it. I'm glad that aspect of Google Podcasts is going away. I'm not really

47
00:04:08,000 --> 00:04:13,920
a fan of Google Podcasts going away, dying like it is, but at least this aspect we no longer have

48
00:04:13,920 --> 00:04:18,640
have to worry about after it's dead. A couple of my own podcasts have been a victim of this

49
00:04:18,640 --> 00:04:23,960
situation, where one of my podcasts even had I think as many as 8 different RSS feeds discovered

50
00:04:23,960 --> 00:04:29,120
by Google Podcasts. And even though some of them were proper 301 redirects back to the

51
00:04:29,120 --> 00:04:35,440
correct RSS feed, the automated system still wanted to change to them instead of keeping

52
00:04:35,440 --> 00:04:41,780
the feeds that I had intentionally submitted for Google Podcasts to use. But at least that

53
00:04:41,780 --> 00:04:46,700
didn't create duplicates of my podcast and I don't think it interfered with my

54
00:04:46,700 --> 00:04:50,660
audience in Google Podcasts. Also I didn't really have much of an audience

55
00:04:50,660 --> 00:04:54,120
inside of Google Podcasts which is part of the reason why Google Podcasts is

56
00:04:54,120 --> 00:04:57,980
going away. If you're looking for a replacement to Google Podcasts as a

57
00:04:57,980 --> 00:05:02,980
listener then I recommend you check out newpodcastapps.com or even just

58
00:05:02,980 --> 00:05:08,220
podcastapps.com. That's a great list of podcasting 2.0 apps that you can check

59
00:05:08,220 --> 00:05:14,260
out to really stay on the cutting edge of podcasting, podcast consumption, and podcast engagement.

60
00:05:14,260 --> 00:05:15,900
That's podcastapps.com.

61
00:05:15,900 --> 00:05:19,200
Or you might have heard of newpodcastapps.com.

62
00:05:19,200 --> 00:05:20,340
It goes to the same place.

63
00:05:20,340 --> 00:05:26,540
But back to this, other discovery systems might add the extra feeds as new podcasts

64
00:05:26,540 --> 00:05:28,700
resulting in duplicates.

65
00:05:28,700 --> 00:05:34,260
And at least at this time, none of the most popular podcast apps use automatic discovery

66
00:05:34,260 --> 00:05:35,900
to build their catalogs.

67
00:05:35,900 --> 00:05:42,160
Apple podcasts, not Spotify, not Amazon. Podcast index is really now the next

68
00:05:42,160 --> 00:05:47,060
number one that is auto discovering RSS feeds for podcasts. But they are trying

69
00:05:47,060 --> 00:05:52,420
to crack down on the duplication problem and avoid duplications. They kind of have

70
00:05:52,420 --> 00:05:58,040
a proxy system where podcast apps can get the podcast index version of your

71
00:05:58,040 --> 00:06:03,060
podcast from podcast index instead of from your RSS feed. But my understanding

72
00:06:03,060 --> 00:06:08,380
is that although that situation exists, they understand the nature of this whole

73
00:06:08,380 --> 00:06:12,220
problem this episode is about with the duplicates and the consequences of

74
00:06:12,220 --> 00:06:16,860
deleting a duplicate. So I think most of those apps that work with the podcast

75
00:06:16,860 --> 00:06:22,980
index version still look to your RSS feed as the authority on what's in your

76
00:06:22,980 --> 00:06:27,900
podcast in some way or they're redirect or they don't worry about what's in the

77
00:06:27,900 --> 00:06:32,620
index but get it from your RSS feed. Because these are smart podcast app

78
00:06:32,620 --> 00:06:37,060
developers that understand the industry better so they've designed a better system.

79
00:06:37,060 --> 00:06:38,820
That's the first reason you may have duplicates.

80
00:06:38,820 --> 00:06:44,060
The second reason you may get duplicates of your podcast is the podcast was resubmitted.

81
00:06:44,060 --> 00:06:45,500
I said this in the beginning.

82
00:06:45,500 --> 00:06:46,720
I'll say it again now.

83
00:06:46,720 --> 00:06:48,220
I'll say it again later.

84
00:06:48,220 --> 00:06:52,580
Do not resubmit your podcast if it's already listed.

85
00:06:52,580 --> 00:06:57,620
I see this happen far more frequently lately and definitely more than it should happen.

86
00:06:57,620 --> 00:07:01,860
When podcasters switch podcast hosting providers like from Spotify for podcasters formerly

87
00:07:01,860 --> 00:07:06,780
known as Anchor, to a provider such as Captivate or Blueberry, both great providers that I

88
00:07:06,780 --> 00:07:08,140
do highly recommend.

89
00:07:08,140 --> 00:07:14,300
The podcasters sometimes submit their new RSS feeds from those new podcast hosting providers

90
00:07:14,300 --> 00:07:20,780
as new podcasts in the podcast apps instead of simply redirecting the old feeds, which

91
00:07:20,780 --> 00:07:23,020
you can't do in almost all the places.

92
00:07:23,020 --> 00:07:29,340
So they're doing an unnecessary step, creating an unnecessary duplicate, and not completely

93
00:07:29,340 --> 00:07:33,060
recognizing the problem that they're creating and that they're not bringing any of their

94
00:07:33,060 --> 00:07:38,180
audience over with them. This sometimes comes from bad advice or from an attempt, albeit

95
00:07:38,180 --> 00:07:43,220
the wrong method, to reclaim ownership of a podcast in Apple Podcasts or another directory,

96
00:07:43,220 --> 00:07:48,060
or it might even be from thinking you had to resubmit after changing the title or cover

97
00:07:48,060 --> 00:07:52,780
art or podcast hosting provider or changing anything about the feed. Whatever the reason,

98
00:07:52,780 --> 00:07:58,940
this usually results in listing the same podcast twice or more, even if you later properly

99
00:07:58,940 --> 00:08:05,600
redirect the old RSS feed. Apple Podcasts used to prevent the same RSS feed from being

100
00:08:05,600 --> 00:08:12,300
submitted twice, but I'm seeing indications that system either isn't working or isn't

101
00:08:12,300 --> 00:08:16,800
used anymore. Because I know of one case that happened only a couple weeks ago as of the

102
00:08:16,800 --> 00:08:23,420
time of this recording where someone managed to resubmit the exact same RSS feed a second

103
00:08:23,420 --> 00:08:29,020
time and got it listed a second time in Apple Podcasts. The only difference was that that

104
00:08:29,020 --> 00:08:35,380
second submission had the new title and cover art of the podcast, which Apple simply hadn't

105
00:08:35,380 --> 00:08:41,020
updated yet in the old listing. But everything else about the podcast was exactly the same.

106
00:08:41,020 --> 00:08:45,780
So I don't know why Apple let that through. Maybe the first version was submitted through

107
00:08:45,780 --> 00:08:51,340
some kind of API and therefore wasn't listed in their kind of index that prevents duplicates.

108
00:08:51,340 --> 00:08:56,820
I don't know, whatever it is, something wasn't working or isn't being used like it should be.

109
00:08:56,820 --> 00:09:02,940
But the big takeaway is, again, do not resubmit your podcast if it's already listed.

110
00:09:02,940 --> 00:09:06,700
And don't tell your long-time audience to follow your new listing either.

111
00:09:06,700 --> 00:09:11,060
If you switch tools or anything like that, you need to put in a redirect.

112
00:09:11,060 --> 00:09:16,500
Don't submit your new feed to the apps because that creates this problem.

113
00:09:16,500 --> 00:09:20,420
But it's even worse in Apple Podcasts since iOS 14.5.

114
00:09:20,420 --> 00:09:25,140
And this is a problem that a lot of podcasters don't know exists.

115
00:09:25,140 --> 00:09:31,000
And I see even some podcasting consultants and podcast hosting providers not remember

116
00:09:31,000 --> 00:09:33,500
or recognize that this problem now exists.

117
00:09:33,500 --> 00:09:39,640
I did a whole episode about feed proxies and the big change that iOS 14.5 made.

118
00:09:39,640 --> 00:09:48,000
But in short, before iOS 14.5, your audience was connected directly to your podcast RSS feed.

119
00:09:48,000 --> 00:09:52,840
So regardless of what happened in the Apple Podcast Catalog, even if for whatever reason

120
00:09:52,840 --> 00:09:58,000
cancel culture, copyrights, trademarks, anything like that, even technical problems, if your

121
00:09:58,000 --> 00:10:03,880
podcast was kicked out of the Apple Podcast Catalog, your audience would still get whatever

122
00:10:03,880 --> 00:10:08,960
you put in your feed and would follow whatever that feed URL would redirect.

123
00:10:08,960 --> 00:10:13,640
So back then, you could simply redirect the duplicate listing and then delete it and you

124
00:10:13,640 --> 00:10:15,540
wouldn't lose any of your audience.

125
00:10:15,540 --> 00:10:20,040
Even if you were kicked out, removed by your own choice or by someone else's choice from

126
00:10:20,040 --> 00:10:24,740
the Apple Podcast Catalog, your feed still existed and therefore your audience was still

127
00:10:24,740 --> 00:10:26,960
connected to your RSS feed.

128
00:10:26,960 --> 00:10:28,380
Those were the good old days.

129
00:10:28,380 --> 00:10:29,960
But it's not like that anymore.

130
00:10:29,960 --> 00:10:32,660
They changed this with iOS 14.5.

131
00:10:32,660 --> 00:10:35,840
Go back to my previous episode about feed proxies and iOS 14.5.

132
00:10:35,840 --> 00:10:41,500
I link to it in the notes for this episode at theaudacitytopodcast.com/fixduplicates.

133
00:10:41,500 --> 00:10:45,080
It is another technical heavy episode but it's very important to understand what Apple

134
00:10:45,080 --> 00:10:50,240
changed and it does give them some censorship control that I don't think they'll admit

135
00:10:50,240 --> 00:10:53,540
to but I think it's one of the reasons why they changed this.

136
00:10:53,540 --> 00:10:55,440
It also has great performance benefits.

137
00:10:55,440 --> 00:10:57,480
But here's what's so different now.

138
00:10:57,480 --> 00:11:03,140
Now even if your duplicate listing gets switched to your correct RSS feed, so you have two

139
00:11:03,140 --> 00:11:06,340
Two listings, both with the correct RSS feed.

140
00:11:06,340 --> 00:11:09,500
One of them was redirected maybe to the correct feed.

141
00:11:09,500 --> 00:11:15,100
Everyone who followed your podcast through that duplicate is connected to Apple's proxy

142
00:11:15,100 --> 00:11:19,700
of your podcast feed and not connected directly to your feed.

143
00:11:19,700 --> 00:11:24,120
In other words, people in Apple Podcasts, Spotify, and maybe a couple of other naughty

144
00:11:24,120 --> 00:11:31,020
proxy based podcast apps are subscribed to the catalog listing of your podcast in that

145
00:11:31,020 --> 00:11:37,100
not directly to your RSS feed. So if you delete that duplicate catalog listing, or

146
00:11:37,100 --> 00:11:42,740
delete any of your catalog listings, you will lose the followers for that listing.

147
00:11:42,740 --> 00:11:48,100
You will lose audience members. Even if you're okay with losing any ratings,

148
00:11:48,100 --> 00:11:52,780
reviews, and rankings that duplicate listing might have accumulated, I suggest

149
00:11:52,780 --> 00:11:57,540
that you should not accept losing your audience. It's a big problem that Apple

150
00:11:57,540 --> 00:12:04,220
created and unfortunately they don't really have a good solution and there's some bad

151
00:12:04,220 --> 00:12:09,260
advice out there and some people that don't understand that this problem exists and so

152
00:12:09,260 --> 00:12:14,500
they're either giving bad advice or just not recognizing what kind of situation this is.

153
00:12:14,500 --> 00:12:19,220
With that understanding in place, and I hope it was clear enough at this point, here's

154
00:12:19,220 --> 00:12:25,000
how to fix your duplicate podcast listing in these proxy-based services like Apple Podcasts

155
00:12:25,000 --> 00:12:28,120
and Spotify and maybe a couple others now or in the future.

156
00:12:28,120 --> 00:12:32,240
If the podcast app in question behaves like Apple Podcasts and Spotify where your audience

157
00:12:32,240 --> 00:12:38,080
is connected to the platforms proxy of your podcast or the catalog listing of your podcast

158
00:12:38,080 --> 00:12:45,600
instead of directly to your RSS feed, then the solution is a little complicated or maybe

159
00:12:45,600 --> 00:12:47,560
I should say a lot complicated.

160
00:12:47,560 --> 00:12:53,440
And it's unfortunately incomplete and not fully effective, but these steps should help

161
00:12:53,440 --> 00:12:58,480
and should get you most of the way there. But you're going to have to accept that it's not

162
00:12:58,480 --> 00:13:05,200
going to be 100% safe and effective. In all the following steps, when I refer to the correct

163
00:13:05,200 --> 00:13:10,080
listing, that will be the oldest listing that you have. The one that has the majority of your

164
00:13:10,080 --> 00:13:15,040
followers, the majority of your ratings and reviews and rankings. That's the one you want to

165
00:13:15,040 --> 00:13:21,360
keep. You want to keep that older one with its reputation. Even if it still has the wrong RSS

166
00:13:21,360 --> 00:13:25,620
feed because that should be fixable with a simple redirect. So even if it's the

167
00:13:25,620 --> 00:13:29,180
wrong feed, that's the one you want because that's where most of the people

168
00:13:29,180 --> 00:13:34,380
have followed your podcast and it probably has the reputation and maturity

169
00:13:34,380 --> 00:13:39,060
to it inside of the podcast apps. So maybe it has the ratings and reviews and

170
00:13:39,060 --> 00:13:43,340
rankings and all of that. You want to keep that original one as much as

171
00:13:43,340 --> 00:13:48,340
possible. You can fix the RSS feed, you can't fix losing your audience. But I

172
00:13:48,340 --> 00:13:53,080
want to help you avoid that. So here's how to do that. Step one, ask the platform to

173
00:13:53,080 --> 00:13:58,580
merge your listings. While this is most likely not possible, at least at this time, these

174
00:13:58,580 --> 00:14:03,280
platforms need to know how frequent these problems are. So here's what I suggest you

175
00:14:03,280 --> 00:14:08,480
send to them. And feel free to copy and update this version, which is in the notes for this

176
00:14:08,480 --> 00:14:14,500
episode at theaudacitytopodcast.com/fixduplicates. Just update it, fill in some of the fields

177
00:14:14,500 --> 00:14:18,040
with your own information, and you can put it in your own voice if you want or even run

178
00:14:18,040 --> 00:14:22,320
it through chat GPT if you feel like it, but this is basically what you need to communicate.

179
00:14:22,320 --> 00:14:27,120
And it goes like this, quote "Dear Apple Podcasts, Spotify, or whatever other platform

180
00:14:27,120 --> 00:14:32,780
it is, my podcast, your podcast title here, is listed multiple times in your catalog and

181
00:14:32,780 --> 00:14:36,040
that's negatively affecting me and my audience.

182
00:14:36,040 --> 00:14:41,600
If possible, would you please merge these listings so I don't lose any of my audience

183
00:14:41,600 --> 00:14:44,160
or earned engagement or rankings?

184
00:14:44,160 --> 00:14:48,760
listing and then list your URL of the correct listing. Maybe it's an ID number like your

185
00:14:48,760 --> 00:14:53,840
Apple Podcast ID or the Spotify ID for that listing. And then the correct feed, that's

186
00:14:53,840 --> 00:14:58,760
their feed URL which may actually be different from the current listing. And you might want

187
00:14:58,760 --> 00:15:03,960
to point that out to them if it is different. Then also list the incorrect listings, the

188
00:15:03,960 --> 00:15:10,040
URLs or the IDs. And then you can continue. It's crucial for my audience's experience

189
00:15:10,040 --> 00:15:15,080
ensure none of them are disconnected from my podcast through this merge process.

190
00:15:15,080 --> 00:15:20,640
Even if I have to lose some other earned engagement or ranking, I need a promise that I won't

191
00:15:20,640 --> 00:15:22,740
lose any of my audience.

192
00:15:22,740 --> 00:15:23,740
Thanks in advance."

193
00:15:23,740 --> 00:15:27,780
And then you can send that off to them with your name and contact information.

194
00:15:27,780 --> 00:15:32,680
If they actually can merge your listings, because right now I don't think they can,

195
00:15:32,680 --> 00:15:36,500
and they can promise you won't lose your audience, then great.

196
00:15:36,500 --> 00:15:40,660
Most likely they'll come back saying either they can't merge the listings or they might

197
00:15:40,660 --> 00:15:48,900
even give bad advice, as I've seen come from Apple sometimes, suggesting to delete the duplicates.

198
00:15:48,900 --> 00:15:50,780
Do not do that!

199
00:15:50,780 --> 00:15:51,780
At least not yet.

200
00:15:51,780 --> 00:15:56,940
Now, in your interaction with them, please, please, please be kind so that you are giving

201
00:15:56,940 --> 00:16:01,500
respect to them, so that they'll be happy to work with you as much as possible.

202
00:16:01,500 --> 00:16:04,980
It's easier to work with people who are being kind, so please be kind to them even though

203
00:16:04,980 --> 00:16:09,660
Though they probably can't fix this problem, but they still need to hear you ask.

204
00:16:09,660 --> 00:16:15,620
They need to know how often this problem happens and how important it is to you that the problem

205
00:16:15,620 --> 00:16:16,740
be fixed.

206
00:16:16,740 --> 00:16:21,300
But you should probably assume that they won't be able to give you the correct help.

207
00:16:21,300 --> 00:16:24,220
But I do still recommend asking anyway.

208
00:16:24,220 --> 00:16:28,300
Since these naughty proxy-based platforms like Apple Podcasts and Spotify and maybe

209
00:16:28,300 --> 00:16:32,780
a couple of others most likely can't provide the correct solution, deleting the duplicate

210
00:16:32,780 --> 00:16:35,500
listing will harm your audience.

211
00:16:35,500 --> 00:16:40,420
Your only other option is to ask your audience to re-follow the correct listing, but there's

212
00:16:40,420 --> 00:16:41,820
a clever way to do that.

213
00:16:41,820 --> 00:16:47,120
So you don't need to ask your whole audience or confuse your whole audience, only giving

214
00:16:47,120 --> 00:16:50,780
the instructions, most likely, to the people who are affected.

215
00:16:50,780 --> 00:16:52,820
So that leads into Step 2.

216
00:16:52,820 --> 00:16:58,100
After you've asked the platform to merge your listings, Step 2, redirect properly.

217
00:16:58,100 --> 00:17:04,180
Unfortunately, it seems most of these duplicates happen where the old but correct listing is

218
00:17:04,180 --> 00:17:12,560
using the wrong RSS feed and your duplicate incorrect listing might be using the new correct feeds.

219
00:17:12,560 --> 00:17:15,440
So you got the correct and incorrect separated.

220
00:17:15,440 --> 00:17:17,680
You need the correct and the correct together.

221
00:17:17,680 --> 00:17:22,580
So I know this will seem a little confusing and I highly recommend looking at the notes

222
00:17:22,580 --> 00:17:25,540
along with this, especially if you're in this situation.

223
00:17:25,540 --> 00:17:29,100
And maybe I'll be able to help you if you need some help or I can refer you to someone

224
00:17:29,100 --> 00:17:30,900
else you can hire to help you.

225
00:17:30,900 --> 00:17:37,220
Look at the notes, theaudacitytopodcast.com/fixduplicates to review some of this and to re-read any

226
00:17:37,220 --> 00:17:41,300
of the parts that you need to try to better understand if it's necessary for you.

227
00:17:41,300 --> 00:17:44,980
The old listing most likely has more followers and reputation.

228
00:17:44,980 --> 00:17:49,900
So it's the listing you want to keep, especially if it's been around longer.

229
00:17:49,900 --> 00:17:56,820
that old feed URL to redirect to the new feed using a 301 permanent redirect. None of this

230
00:17:56,820 --> 00:18:03,060
302, 307, or anything like that. It needs to be a 301 redirect. And that is a permanent

231
00:18:03,060 --> 00:18:08,260
redirect. So saying 301 redirect is the same as a permanent redirect. But I try to avoid

232
00:18:08,260 --> 00:18:14,860
only saying permanent redirect because really that redirect needs to remain as a 301 for

233
00:18:14,860 --> 00:18:20,980
forever. It needs to be permanently in place, permanently redirecting. Ideally. If you can't

234
00:18:20,980 --> 00:18:25,900
have that then at least have it redirect for a few months. But typically, redirect for

235
00:18:25,900 --> 00:18:30,140
forever. That's what it should be doing. A redirect happens before the contents of

236
00:18:30,140 --> 00:18:35,300
the feed are loaded. So it really doesn't matter what's in that feed you're redirecting.

237
00:18:35,300 --> 00:18:40,340
Or if it's even a feed anymore. It's the URL that's important. I could send you to

238
00:18:40,340 --> 00:18:46,220
myawesomepodcast.com/feed/blahblahblah and have nothing there at all.

239
00:18:46,220 --> 00:18:50,180
But I could set up the redirect on my server on the domain level.

240
00:18:50,180 --> 00:18:53,280
It's just like forwarding mail from your old address to your new home.

241
00:18:53,280 --> 00:18:57,760
It really doesn't matter who lives in the old home because your mail will be forwarded

242
00:18:57,760 --> 00:18:59,760
before it even gets delivered.

243
00:18:59,760 --> 00:19:01,800
That's what a redirect does.

244
00:19:01,800 --> 00:19:08,660
It redirects people before ever loading whatever was at that destination URL.

245
00:19:08,660 --> 00:19:13,940
So don't worry about keeping your old feed contents online at that URL or having a page

246
00:19:13,940 --> 00:19:15,480
there or anything like that.

247
00:19:15,480 --> 00:19:19,800
You need the URL itself and that needs to redirect.

248
00:19:19,800 --> 00:19:24,820
Any half-decent podcast hosting provider should be able to permanently redirect your old RSS

249
00:19:24,820 --> 00:19:26,800
feed to the new one.

250
00:19:26,800 --> 00:19:30,000
Even the bottom of the barrel SoundCloud can do it.

251
00:19:30,000 --> 00:19:33,920
And yes, I still think SoundCloud is the absolute worst podcast hosting provider.

252
00:19:33,920 --> 00:19:37,560
Spotify for podcasters is close to the bottom, but they're not the absolute worst.

253
00:19:37,560 --> 00:19:43,960
But they can also put in a 301 redirect permanently, or as far as I know it's permanent, for forever.

254
00:19:43,960 --> 00:19:48,760
If you control the URL of your old feed, you might be able to use tools from your website,

255
00:19:48,760 --> 00:19:54,720
your web hosting provider, or your domain registrar to redirect the old URL to your

256
00:19:54,720 --> 00:19:55,720
new feed.

257
00:19:55,720 --> 00:20:00,240
You could even use a third party tool like Cloudflare to put a redirect on the domain's

258
00:20:00,240 --> 00:20:06,560
exact path and you wouldn't need web hosting at all because again, the contents of the

259
00:20:06,560 --> 00:20:14,800
URL don't matter. It's the URL itself that matters. And that URL needs a 301 redirect

260
00:20:14,800 --> 00:20:21,960
to the new feed URL. So you don't need your hosting for your old site. You just need that

261
00:20:21,960 --> 00:20:28,280
URL. And domains these days are $15 to $20 for a .com domain or .net, .org and some of

262
00:20:28,280 --> 00:20:33,520
those more popular ones. So it's really not that much of an expense to keep it. And you

263
00:20:33,520 --> 00:20:37,740
You can use some free tools like Cloudflare or maybe something built in with your registrar

264
00:20:37,740 --> 00:20:41,900
so you are redirecting the old URL to the new one.

265
00:20:41,900 --> 00:20:46,900
Or your old podcast hosting provider should have the option for you to have a 301 redirect

266
00:20:46,900 --> 00:20:48,880
from your old feed to the new one.

267
00:20:48,880 --> 00:20:51,760
If they don't, you should be leaving them anyway.

268
00:20:51,760 --> 00:20:56,400
Because they're making the world a horrible place if they don't do 301 redirects.

269
00:20:56,400 --> 00:21:02,840
Step 3 then, make a new RSS feed with a single announcement episode.

270
00:21:02,840 --> 00:21:07,760
by creating a new RSS feed with most of the same podcast information, like the same title,

271
00:21:07,760 --> 00:21:11,280
cover art, same artist information, and some of the other stuff.

272
00:21:11,280 --> 00:21:16,960
The easiest way to get this would be a separate category feed from your publishing tool if available.

273
00:21:16,960 --> 00:21:20,320
But you need to be able to control what is in that feed.

274
00:21:20,320 --> 00:21:26,000
And if that won't work, you could even open your RSS feed in a browser or download it,

275
00:21:26,000 --> 00:21:31,320
save it to your computer, and manually edit it, which is kind of difficult for some and

276
00:21:31,320 --> 00:21:33,520
Kind of dangerous, potentially.

277
00:21:33,520 --> 00:21:38,840
But when you edit it, make sure you remove all the episodes and even change the title.

278
00:21:38,840 --> 00:21:44,280
Maybe simply add "DUPLICATE" very prominently, maybe in all caps in the title or something similar.

279
00:21:44,280 --> 00:21:47,840
And you may even want to add a banner across the cover art that says "DUPLICATE" "PLEASE

280
00:21:47,840 --> 00:21:54,400
REFOLLOW" or something like that so that it is very obvious that anyone who sees this

281
00:21:54,400 --> 00:22:00,520
duplicate listing can see that it is a duplicate and not the actual podcast you want them to follow.

282
00:22:00,520 --> 00:22:05,960
since you've deleted all the episodes that were in it, then put in a single episode explaining

283
00:22:05,960 --> 00:22:12,960
what you need your audience to do and link to your correct listings in all the affected apps.

284
00:22:12,960 --> 00:22:16,880
Maybe even also including your RSS feed in plain text, so if they want that, they can

285
00:22:16,880 --> 00:22:17,880
use that.

286
00:22:17,880 --> 00:22:24,100
Now this announcement episode will be seen and heard most likely only by those who actually

287
00:22:24,100 --> 00:22:29,480
need to do something as long as you are putting it in this separate announcement feed, not

288
00:22:29,480 --> 00:22:34,200
in your main podcast feed that's going out to your main audience. I've got an example

289
00:22:34,200 --> 00:22:37,840
script you can use, feel free to use that, put it in your own voice, run it through chat

290
00:22:37,840 --> 00:22:42,960
GPT if you want, but these are the main points that you need to hit in this episode in a

291
00:22:42,960 --> 00:22:49,280
way that I suggest that you could word it. It's in the notes at theaudacitytopodcast.com/fixduplicates

292
00:22:49,280 --> 00:22:53,560
or a simple tap or swipe away. You could start off saying, "Hi, we're changing some back-end

293
00:22:53,560 --> 00:22:58,460
stuff with our podcast and that unfortunately breaks part of our podcast. We would love

294
00:22:58,460 --> 00:23:03,240
to keep you in our community, so we need you to do a couple of things to continue receiving

295
00:23:03,240 --> 00:23:08,520
our podcast. First, re-follow our podcast in your podcast app, but it needs to be the

296
00:23:08,520 --> 00:23:13,720
one without duplicate in the title and cover art. You can probably get there from the link

297
00:23:13,720 --> 00:23:18,800
in this episode's notes or by searching for the same title. And make sure you include

298
00:23:18,800 --> 00:23:24,540
those links in the text. Make sure it shows up as much as you can in the podcast apps.

299
00:23:24,540 --> 00:23:28,820
And then you can continue saying, "Then, when you see that you're following the correct

300
00:23:28,820 --> 00:23:33,640
podcast with all the episodes again, please unfollow this duplicate podcast and remove

301
00:23:33,640 --> 00:23:34,640
it from your library."

302
00:23:34,640 --> 00:23:37,020
That's all you need to say in that episode.

303
00:23:37,020 --> 00:23:43,120
Make this new RSS feed then available online, even if you merely upload that XML file to

304
00:23:43,120 --> 00:23:46,420
your web hosting or Amazon S3 or anything like that.

305
00:23:46,420 --> 00:23:48,080
It needs to be online somewhere.

306
00:23:48,080 --> 00:23:52,120
But you will not be using any regular redirects to it or from it.

307
00:23:52,120 --> 00:23:53,460
At least not yet.

308
00:23:53,460 --> 00:23:59,700
Step 4. Change the feed URL in the platform's portal. Apple Podcasts, Spotify, and other

309
00:23:59,700 --> 00:24:04,920
proxy-based platforms usually offer portals for you to manage your podcast listings on

310
00:24:04,920 --> 00:24:10,380
their platform. These portals sometimes allow you to change the source RSS feed for your

311
00:24:10,380 --> 00:24:14,740
podcast listing without having to do the redirect for your feed. This is the thing that in the

312
00:24:14,740 --> 00:24:20,380
past I've urged podcasters NOT to change in Apple Podcasts Connect because it would

313
00:24:20,380 --> 00:24:26,360
only affect Apple Podcast followers, but now you do need it because you want it to affect

314
00:24:26,360 --> 00:24:30,660
only Apple Podcast followers because they're the ones affected by this problem.

315
00:24:30,660 --> 00:24:34,780
And the same thing in other platforms that might be affected by this duplication problem.

316
00:24:34,780 --> 00:24:38,940
Log into each platform portal that has your duplicate listings and change that source

317
00:24:38,940 --> 00:24:43,180
RSS feed to the announcement feed you created in step 3.

318
00:24:43,180 --> 00:24:47,820
This is only for the duplicate listing or multiple listings, not for the one that you

319
00:24:47,820 --> 00:24:48,860
want to keep.

320
00:24:48,860 --> 00:24:54,180
change anything about it yet. You've already redirected its old URL to the new one. This

321
00:24:54,180 --> 00:25:01,740
will change the feed then for only your followers on that platform, not everywhere else. If

322
00:25:01,740 --> 00:25:06,220
you change this in the Apple Podcast catalogs, it will change that source RSS feed for any

323
00:25:06,220 --> 00:25:12,580
apps that use Apple's catalog in their apps, but that would only be for new followers in

324
00:25:12,580 --> 00:25:18,140
those apps. And there is an option inside of Apple Podcasts to stop your podcast feed

325
00:25:18,140 --> 00:25:21,340
from being included in the open API that other apps use.

326
00:25:21,340 --> 00:25:27,420
So you can certainly disable or whatever it is to prevent your podcast from being redistributed

327
00:25:27,420 --> 00:25:29,320
through the Apple API.

328
00:25:29,320 --> 00:25:32,140
So that way the other apps won't pick up the duplicate listing.

329
00:25:32,140 --> 00:25:38,980
But changing this option won't change the feed for anyone already following your podcast

330
00:25:38,980 --> 00:25:45,200
in those other apps, even if they got that feed originally from Apple's API.

331
00:25:45,200 --> 00:25:48,480
It's not like Apple has control over those other apps.

332
00:25:48,480 --> 00:25:50,380
Apple has control over their own app.

333
00:25:50,380 --> 00:25:55,920
And since iOS 14.5, they gave themselves a whole lot more control over what is on your

334
00:25:55,920 --> 00:25:58,320
device in their app.

335
00:25:58,320 --> 00:26:02,120
That's part of the reason why I keep saying this is like communist level control that

336
00:26:02,120 --> 00:26:08,160
Apple has now because they can control what podcasts you're able to download through their app.

337
00:26:08,160 --> 00:26:10,560
And it seems like they want that control.

338
00:26:10,560 --> 00:26:13,880
But they probably won't say exactly why they want it.

339
00:26:13,880 --> 00:26:18,520
But it's okay if the other apps don't completely update the same way because those

340
00:26:18,520 --> 00:26:22,320
other apps aren't really suffering from this duplication problem.

341
00:26:22,320 --> 00:26:26,820
Nearly all the other apps connect your audience directly to your RSS feed.

342
00:26:26,820 --> 00:26:31,200
So your audience would go wherever that feed points in those other apps.

343
00:26:31,200 --> 00:26:36,280
And even if there was a duplicate listing in those other apps, it wouldn't matter because

344
00:26:36,280 --> 00:26:39,480
it's the RSS feed that matters in the other apps.

345
00:26:39,480 --> 00:26:44,080
But in a proxy based app like Apple Podcasts and Spotify and a couple of others maybe,

346
00:26:44,080 --> 00:26:46,240
it's the listing that matters.

347
00:26:46,240 --> 00:26:52,120
And if that duplicate listing is using your correct RSS feed in the other apps, then your

348
00:26:52,120 --> 00:26:57,200
audience would continue to get your podcast from that feed instead of from the app proxy

349
00:26:57,200 --> 00:27:03,000
even if that duplicate listing no longer exists in the API.

350
00:27:03,000 --> 00:27:08,600
Because the other apps connect your audience with your RSS feed, not with Apple's proxy.

351
00:27:08,600 --> 00:27:14,840
Creating your source feed in these few proxy based apps should then add the duplicate information,

352
00:27:14,840 --> 00:27:18,120
and that would be in the title, and in the cover art, and anywhere else you put the word

353
00:27:18,120 --> 00:27:22,280
duplicate or make it obvious that this is a duplicate, it would put that information

354
00:27:22,280 --> 00:27:27,960
and push that announcement episode out to only those who are affected because of the

355
00:27:27,960 --> 00:27:31,040
way the Apple Podcast works with its listings.

356
00:27:31,040 --> 00:27:36,000
So you change the source feed in Apple Podcasts and everyone who's following that listing

357
00:27:36,000 --> 00:27:41,400
from the catalog will get the episode from the new source feed and they'll get only

358
00:27:41,400 --> 00:27:43,160
that one episode.

359
00:27:43,160 --> 00:27:45,860
Where you would then say, "This is a duplicate.

360
00:27:45,860 --> 00:27:50,840
You need to unfollow this, follow the podcast from the correct feed."

361
00:27:50,840 --> 00:27:53,120
That whole thing that I talked about in step three.

362
00:27:53,120 --> 00:27:59,880
Then step five, after a few months, redirect and delete that announcement feed.

363
00:27:59,880 --> 00:28:03,420
Leave that announcement feed online for at least three months.

364
00:28:03,420 --> 00:28:05,480
You can start shutting it down after that.

365
00:28:05,480 --> 00:28:08,120
Or you could leave it online for longer if you want to.

366
00:28:08,120 --> 00:28:13,460
But it doesn't have to stay on there for forever because it's not something that people

367
00:28:13,460 --> 00:28:16,420
would need to be redirected from necessarily.

368
00:28:16,420 --> 00:28:20,240
You're doing the redirection as just a fail safe sort of.

369
00:28:20,240 --> 00:28:23,160
And that's one of the two things you need to do with that announcement feed.

370
00:28:23,160 --> 00:28:27,980
Number one, redirect the announcement feed URL to your correct podcast feed just in case

371
00:28:27,980 --> 00:28:33,320
there are any stragglers somehow following that RSS feed and not the catalog listing.

372
00:28:33,320 --> 00:28:38,680
By redirecting the feed you would ensure they get your new feed correctly, but probably

373
00:28:38,680 --> 00:28:40,160
won't be so much of a problem.

374
00:28:40,160 --> 00:28:42,280
This is just being super thorough at this point.

375
00:28:42,280 --> 00:28:48,000
And then number two with it is delete the duplicate listing through the podcast portals.

376
00:28:48,000 --> 00:28:50,560
That's in Apple Podcasts, Spotify and such.

377
00:28:50,560 --> 00:28:56,320
Once it is redirecting you don't need to keep that announcement feed or episode online anymore,

378
00:28:56,320 --> 00:29:02,240
but you do want to keep that redirect online for at least another few months or so or if

379
00:29:02,240 --> 00:29:05,800
if possible, permanently, but you don't have to worry about it all that much because it

380
00:29:05,800 --> 00:29:12,320
was primarily linked to a catalog listing and the catalog listing is gone, so the feed,

381
00:29:12,320 --> 00:29:17,000
ideally, if the system is working correctly, no one is actually following that feed.

382
00:29:17,000 --> 00:29:20,120
But redirect it just in case and you can delete the contents.

383
00:29:20,120 --> 00:29:21,660
I know.

384
00:29:21,660 --> 00:29:27,800
This is frustrating, it's technical, it's... the unfortunate conclusion for this is it's

385
00:29:27,800 --> 00:29:32,320
It's messy and you might still lose some numbers.

386
00:29:32,320 --> 00:29:38,080
I believe these steps are the current best way to do things if the platforms use their

387
00:29:38,080 --> 00:29:42,860
own proxies and you can't merge the listings or they can't merge them for you.

388
00:29:42,860 --> 00:29:48,160
It's still possible and even likely you'll lose some numbers through the cracks, so to

389
00:29:48,160 --> 00:29:50,040
speak, inherent with this process.

390
00:29:50,040 --> 00:29:55,080
You might see your download stats drop, but it will most likely be disengaged audience

391
00:29:55,080 --> 00:29:56,080
members.

392
00:29:56,080 --> 00:30:02,320
That's why I say you might lose some numbers. I didn't say people. Because, after all, if

393
00:30:02,320 --> 00:30:08,960
those people don't follow you to the correct podcast listing, after months, were they really

394
00:30:08,960 --> 00:30:13,760
that engaged with your podcast anyway? I know there are exceptions to this, so that's why

395
00:30:13,760 --> 00:30:19,560
it's possible that some might fall through the cracks a little bit. And that is unfortunate.

396
00:30:19,560 --> 00:30:25,280
It's messy and it might still decrease your stats a little bit. I really wish this whole

397
00:30:25,280 --> 00:30:29,800
thing was not an issue at all. I wish that Apple wasn't using a proxy or

398
00:30:29,800 --> 00:30:35,440
Spotify using a proxy. I wish that Apple, Spotify, and similar platforms had a way

399
00:30:35,440 --> 00:30:39,760
of merging your listings, merging your ratings and reviews, and your ranking

400
00:30:39,760 --> 00:30:43,320
authority, and all of that stuff. That would be wonderful if they could.

401
00:30:43,320 --> 00:30:47,960
Unfortunately it seems like right now they don't and it seems like they won't

402
00:30:47,960 --> 00:30:52,720
build that unless they see that this is a big enough problem basically

403
00:30:52,720 --> 00:30:57,520
necessitating they're building something like that. And the bad instructions and platform

404
00:30:57,520 --> 00:31:03,520
limitations make this complicated process necessary if you hope to keep most of your

405
00:31:03,520 --> 00:31:10,800
audience. So back again to that important reminder, do not resubmit your feed. As much

406
00:31:10,800 --> 00:31:15,840
as I'd like to bring in Smokey the Podcast Bear to tell you that only you can prevent

407
00:31:15,840 --> 00:31:21,200
duplicate podcast listings, and it is majority on your responsibility, the unfortunate reality

408
00:31:21,200 --> 00:31:26,240
is that it's still possible for some hosting providers, most likely the unknowledgeable

409
00:31:26,240 --> 00:31:31,840
ones, to make this mistake and either tell you to resubmit your podcast with the new

410
00:31:31,840 --> 00:31:38,840
RSS feed that they're providing or, even worse, they submit it for you. Do not let

411
00:31:38,840 --> 00:31:45,500
this happen. Do not resubmit your feed if your podcast already exists. Probably the

412
00:31:45,500 --> 00:31:52,920
only exception is if you've completely lost control of your old RSS feed and it's absolutely

413
00:31:52,920 --> 00:31:58,560
impossible to get it back. But it usually is possible. Even in this case, it's still

414
00:31:58,560 --> 00:32:03,980
better to change the source feed of your podcast and all the podcast apps you can instead of

415
00:32:03,980 --> 00:32:10,040
resubmitting your podcast with the new feed. Because of that whole thing of people in Apple

416
00:32:10,040 --> 00:32:17,860
podcasts and Spotify are following the catalog of your podcast, not actually following your podcast.

417
00:32:17,860 --> 00:32:18,860
It's the proxies.

418
00:32:18,860 --> 00:32:25,120
Listen to that previous episode where I talked about feed proxies and the changes with iOS 14.5.

419
00:32:25,120 --> 00:32:26,120
This is messy.

420
00:32:26,120 --> 00:32:27,120
I know.

421
00:32:27,120 --> 00:32:28,120
It's complicated.

422
00:32:28,120 --> 00:32:29,120
I know.

423
00:32:29,120 --> 00:32:30,120
It's frustrating.

424
00:32:30,120 --> 00:32:33,140
I would not want to be in your position if you're running into this.

425
00:32:33,140 --> 00:32:38,000
One person that I worked with recently, at least they caught it quickly that their new

426
00:32:38,000 --> 00:32:42,500
podcast had just been approved in Apple Podcasts and I was there with them

427
00:32:42,500 --> 00:32:46,760
helping them through it. It was a customer of Podgagement and I saw that

428
00:32:46,760 --> 00:32:50,240
they added the same podcast twice so I reached out to them and we started

429
00:32:50,240 --> 00:32:54,720
talking through it and the podcast had just been approved by Apple. I urged them

430
00:32:54,720 --> 00:32:58,440
you got to remove this quickly before you start getting subscribers on that

431
00:32:58,440 --> 00:33:02,800
new one. You got to delete this listing. You can still reclaim the ownership of

432
00:33:02,800 --> 00:33:06,520
the old listing through Apple's processes or Spotify might have some

433
00:33:06,520 --> 00:33:10,720
processes. Spotify is a little weird with reclaiming ownership of a listing. They

434
00:33:10,720 --> 00:33:16,380
might actually need you to resubmit the feed, but in that process you need to

435
00:33:16,380 --> 00:33:21,620
make sure that if they require you to do that, that they can assure you that you

436
00:33:21,620 --> 00:33:26,380
won't lose any of your existing audience to that old listing. That everyone needs

437
00:33:26,380 --> 00:33:31,300
to follow over to the correct listing. So because this is complicated and messy, if

438
00:33:31,300 --> 00:33:34,940
you need help for this I might be available for hire to help you with this

439
00:33:34,940 --> 00:33:38,780
or I might be able to refer you to someone who can help you with this, but I really hope

440
00:33:38,780 --> 00:33:40,900
you don't end up in this situation.

441
00:33:40,900 --> 00:33:45,020
And this is the episode that I've wanted to put out there because my podcasting heart

442
00:33:45,020 --> 00:33:49,980
breaks for some of the podcasters I see in this situation where their audience is split

443
00:33:49,980 --> 00:33:54,300
and it seems like the only solution is going to cost some of their audience, especially

444
00:33:54,300 --> 00:33:58,660
some of their ratings and reviews, that maybe they really like some of their ratings and reviews.

445
00:33:58,660 --> 00:34:01,960
Now if you are a customer of Podgagement and you're in this situation where you've got

446
00:34:01,960 --> 00:34:07,120
multiple listings and the multiple listings for the same podcast have their

447
00:34:07,120 --> 00:34:11,400
own ratings and reviews and you don't want to lose those, please reach out to

448
00:34:11,400 --> 00:34:15,660
me. Because there's something I can do in my back-end system where even though it

449
00:34:15,660 --> 00:34:19,560
won't change what's in Apple Podcasts or the other systems, at least when you log

450
00:34:19,560 --> 00:34:24,080
into your Podgagement account you would be able to see all the same reviews that

451
00:34:24,080 --> 00:34:27,680
you had on the other podcast. So if you're in that situation, you've got

452
00:34:27,680 --> 00:34:31,840
ratings and reviews on both listings and you want those merged together in

453
00:34:31,840 --> 00:34:36,320
podgagement, so you still have a record of all those ratings and reviews, please reach

454
00:34:36,320 --> 00:34:41,060
out to me before you delete your duplicate listings so we can work on that, duplicate

455
00:34:41,060 --> 00:34:45,940
those over on our system, merge them together for you so you still have that record of those.

456
00:34:45,940 --> 00:34:48,140
But I really hope you're not in this situation.

457
00:34:48,140 --> 00:34:52,300
The big thing is do not resubmit your feed.

458
00:34:52,300 --> 00:34:56,820
If you see that anyone else is in this situation, they've got duplicate listings, please send

459
00:34:56,820 --> 00:34:58,160
them to this episode.

460
00:34:58,160 --> 00:35:02,840
even send this episode alone with your correspondence with Apple and Spotify or any of those other

461
00:35:02,840 --> 00:35:08,140
naughty proxy-based podcast apps. Let them know that this is a problem and the details

462
00:35:08,140 --> 00:35:13,560
and the complicated process involved with this because this needs to stop. And I really

463
00:35:13,560 --> 00:35:18,440
hope that you don't end up in this situation and that if you are in this situation, I hope

464
00:35:18,440 --> 00:35:23,160
this helps you. You can share this episode out from theaudacitytopodcast.com/fixduplicates.

465
00:35:23,160 --> 00:35:29,840
I know this was a heavy episode, so maybe it didn't give you all that much for the

466
00:35:29,840 --> 00:35:34,000
guts, but at least it taught you some of the tools that you need to fix this problem.

467
00:35:34,000 --> 00:35:39,840
So now it's time for you to go start and grow your own podcast for passion and profit.

468
00:35:39,840 --> 00:35:43,120
I'm Daniel J. Lewis from the Audacity to Podcast.

469
00:35:43,120 --> 00:35:43,760
Thanks for listening.

470
00:35:43,760 --> 00:36:09,620
[MUSIC PLAYING]