---
title: "Feeds"
description: "Follow a blog in a feed reader, a podcast in Apple Podcasts, Spotify and other apps, or an event in a calendar app, from its public feed or a private one, and what happens when a private feed is shared."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sherpo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Feeds

Every [blog and podcast](/overview/categories) has an RSS feed, the format feed readers and podcast apps read. A blog's feed works in feed readers such as Feedly, Inoreader or NetNewsWire, and a podcast's in podcast apps such as Apple Podcasts, Spotify, Overcast and Pocket Casts.

Each one has two kinds of feed:

- A **public feed**, for anyone: it puts a podcast in directories and lets anyone follow a blog's new posts.
- A **private feed** for each customer who holds the blog or the podcast, at an address of their own, carrying what they paid for.

This page covers both for sellers and customers. To read feeds from your own front end, see [Feeds](/customer-api/feeds) in the customer API.

## Public feeds

A blog's public feed lists its 50 newest posts with their abstracts, the teaser you write for each post, and never a post in full, so a paid post shows only its teaser. A podcast's public feed lists the 50 newest episodes anyone may listen to, each with its audio, length, artwork and notes, and its transcript (its published subtitles) and chapters when it has them. Locked episodes are left out, so a paid podcast's public feed carries its free episodes alone.

A product has a public feed once it's published and listed. An unlisted blog or podcast has none, but its customers still get private feeds. On your store, a blog's or a podcast's pages link its public feed as **RSS feed**, and feed readers find it from any of its pages on their own.

## List a podcast in Apple Podcasts and Spotify

A podcast's public feed is what you submit to directories, once. They read it again on their own, so a new episode reaches them without you doing anything.

1. Publish the podcast and keep it listed. Give it a square JPEG or PNG thumbnail of the size directories ask for, which they show as the show's artwork (see [Feeds](/merchant-app/products#feeds-blog-podcast-event)).
2. In the merchant app, open the podcast's **Settings**, then **Feeds**. Pick a **Category** from Apple's list, set **Explicit** if it applies, and add an **Owner email**, the address directories write to so you can prove the show is yours. See [Feeds](/merchant-app/products#feeds-blog-podcast-event).
3. Copy the **Public feed** address from the same section.
4. Submit it to each directory:
   - **Apple Podcasts:** add a show with an RSS feed in Apple Podcasts Connect. Apple lists a podcast only once it has a category.
   - **Spotify:** add your podcast in Spotify for Creators with its RSS feed. Spotify verifies it through the owner email.
   - **Other apps:** many, such as Overcast, list the shows in Apple's directory, and others take a submission on their own site.

An episode joins the feeds once its audio is an MP3, M4A or AAC file that plays on its page rather than as a download, and isn't protected; see [Feeds](/merchant-app/products#feeds-blog-podcast-event) for what else directories read. Spotify and other directories play only what the public feed carries. Listeners who pay follow the rest from a private feed.

## Private feeds

A customer who holds a blog or a podcast can get a private feed of their own, unless the seller turned private feeds off for it. It carries what they may open, decided again every time their app reads it:

- A blog's private feed lists its 50 newest posts: the 20 newest they may read come in full, the others with their abstract.
- A podcast's private feed lists the 50 newest episodes they may listen to. Older ones play on the store.

When their access ends, the feed stops working, and it works again if they hold the product once more.

### Add a private feed to your app

On the store, sign in and open the blog or the podcast:

- On a blog, choose **Your private feed** beside its RSS feed, or **Private feed** on its card in your library.
- On a podcast, choose **Listen in your app** on the podcast's page, under any episode's player or on its card in your library.

Choose **Get my private feed** the first time, then **Copy**, and add the address to your app:

- **Apple Podcasts** on iPhone and iPad: in **Library**, open the menu at the top and choose **Follow a Show by URL**. On a Mac, choose **File**, then **Follow a Show by URL**.
- **Overcast:** tap **+**, then **Add URL**.
- **Pocket Casts:** paste the address into **Search**.
- **YouTube Music:** add it as a podcast by its RSS feed, from your library.
- **A feed reader:** add a feed or a subscription by its address.

Spotify plays shows from its own directory only, so a private feed doesn't work there; use another app, or listen on the store.

The address is yours alone: anyone who has it gets what you paid for. From the same place you can get a **New address**, which stops the old one at once, or **Turn off** the feed and get a new one later.

## Event calendars

Every [event](/overview/categories#event) has a calendar file of its sessions that calendar apps such as Google Calendar, Apple Calendar and Outlook open or subscribe to, and the store has a schedule of all its listed events. Each session also has links that add it to Google Calendar or Outlook in one step. On the store, **Add to calendar** on an event's page and its cards offers these, Apple Calendar, which subscribes to the event's file, and the file itself for any other calendar app. When the seller keeps an event's location to ticket holders, these leave it out.

A ticket holder can get a private calendar feed of the event, an address of their own that always carries the location and follows every change to the sessions. It works like any private feed: it stops when their ticket ends, a seller can turn private feeds off on the event, and sharing it moves it to a new address as below. On the store, sign in and choose **Calendar feed** on the event's card in your library, then **Get my private feed** the first time and **Copy**. From the same place you can get a **New address** or **Turn off** the feed. To subscribe to an address:

- **Google Calendar** on the web: next to **Other calendars**, choose **+**, then **From URL**.
- **Apple Calendar** on a Mac: choose **File**, then **New Calendar Subscription**. On iPhone and iPad, open **Settings**, **Calendar**, **Accounts**, **Add Account**, **Other**, then **Add Subscribed Calendar**.
- **Outlook** on the web: choose **Add calendar**, then **Subscribe from web**.

To build these into your own front end, see [Events](/customer-api/feeds#events) in the customer API.

## When a private feed is shared

A private feed is for one person and their own devices. Each time it's read, the readers are counted: a feed reader or podcast app on one network counts once, so a phone moving across its carrier's addresses stays one reader, while the same phone on home Wi-Fi counts as another. A service that reads feeds for many people at once, such as Feedly or Inoreader, counts for the subscribers it reports.

When a feed serves more readers in 30 days than one person uses:

1. Its address stops working and the feed moves to a new one.
2. The customer gets an email with the new address, to add to their app in place of the old one. Whoever they shared the old address with can't follow it anymore.

If a feed keeps being shared after moving several times, it's turned off:

- The customer gets one email saying their private feed was turned off.
- On the store, their feed says it was turned off because its address was shared again and again. They can still read every post or listen to every episode there, but they can't get a new feed until the seller turns it back on.

No email is sent when a customer turns their own feed off, when the seller revokes it or turns private feeds off for the product, or when the customer's access ends.

As a seller, you decide how many readers a feed may serve: it moves once it serves more readers in 30 days than its limit, 5 unless you change it, and it's turned off when it's shared again after 3 new addresses in 30 days. You see each customer's private feeds on their page, under **Access**: whether each one is live, has **Moved after too many readers** or is **Off for sharing**, and how many readers it served in the last 30 days against its limit. From there you can **Change limit**, **Revoke** a feed, or **Turn back on** one that's off for sharing, which counts sharing afresh. See [A customer's page](/merchant-app/customers#a-customers-page).

Source: https://docs.sherpo.io/overview/feeds/index.mdx
