How to forward your Audioboom podcast feed - 301 Redirect

301 redirect from Audioboom

After importing your Audioboom RSS feed into Transistor, you’ll then need to redirect your old Audioboom feed so that it points to your new Transistor feed.

Important: If you haven't imported your show yet, you should follow our Import Guide first.

Export your Analytics

It’s a good idea to export your analytics from Audioboom at this point. Analytics do not transfer between hosts so it’s good to take a copy now for your own records.

How to redirect your feed from Audioboom to Transistor?

In your Transistor account, go to the Overview tab and copy your new RSS feed, you'll need that as part of the redirect process.

Each podcast host has their own instructions on redirecting a feed. For Audioboom you can refer to their guide here: https://support.audioboom.com/hc/en-us/articles/360021937714-Redirecting-your-podcast-RSS-to-another-provider

Here are the steps:

Go to Audioboom and login to your account.
Go to the Audioboom Settings page
Submit a redirect request

Audioboom says they aim to set that up within 1 working day.

What if I no longer have my Audioboom account?

If you no longer have an account with Audioboom you can still contact their support directly and ask for them to enable a 301 redirect for you.

Audioboom Support Email: support@audioboom.com

You can use the following email template and enter your podcast details and feeds:

“I have moved my podcast to Transistor.fm. Please redirect my podcast called (insert podcast name) using (insert old Audioboom rss feed) to my new host Transistor (insert new Transistor RSS feed). Please let me know once the redirect is active.”

Audioboom Support Details

Audioboom Support email: support@audioboom.com
Audioboom Contact page: https://support.audioboom.com/hc/en-us/requests/new
Audioboom Support docs: https://support.audioboom.com/hc/en-us
Audioboom Redirect article: https://support.audioboom.com/hc/en-us/articles/360021937714-Redirecting-your-podcast-RSS-to-another-provider

What does a 301 redirect do?

A 301 redirect for your podcast RSS feed is very useful when you move to a new podcast host. It ensures that any subscriber or podcast platform still using your Audioboom feed won’t be faced with a broken link. Enabling a redirect means that your existing subscribers will stay subscribed and podcast directories can continue to pick up your new episodes.

A redirect is like leaving a forwarding address. It lets anyone using your old feed know where you have moved to.

How long does a 301 redirect last?

Most podcast platforms provide a permanent redirect for free, even after you have closed your account with them.

How long does it take to enable a 301 redirect?

A redirect should be active within a couple of minutes of it being applied to your Audioboom feed. Podcast directories will then be able to pick up your new episodes from Transistor the next time they check your feed. That’s usually within 24 hours of your redirect being active.

How to test if a 301 redirect is working?

If you visit your Audioboom feed link in a browser, it should automatically redirect to your Transistor RSS feed.

What happens if I don’t forward my old feed from Audioboom?

If you choose not to redirect your podcast, you may need to complete a few extra steps.

Without a redirect existing subscribers won’t know where you have moved to. They will need to manually re-subscribe to your new Transistor podcast feed. So be prepared to share your new feed out manually to regain your subscribers back.

Without a redirect podcast directories like Apple and Spotify will still be using your old Audioboom feed. To fix that without a redirect you’ll need to manually go to those platforms and update the feed they are using for your podcast.

Here’s how update your RSS feed on Spotify:
https://support.transistor.fm/en/article/how-can-i-change-my-rss-feed-on-spotify-1ttzvm4/

Here’s how to update your RSS feed on Apple Podcasts:
https://support.transistor.fm/en/article/how-can-i-update-my-rss-feed-on-apple-podcasts-1sql0ga

Updated on: 21/11/2022