What is pubDate?
The pubDate element specifies when an RSS item (episode) was published. Podcast apps use this timestamp to sort episodes chronologically, determine which episodes are new, and trigger new episode notifications for subscribers.
pubDate Format
RSS requires dates in RFC 822 format:
<pubDate>Mon, 15 Jan 2024 08:00:00 GMT</pubDate>
Format breakdown:
- Day name:
Mon,Tue,Wed, etc. - Date:
15 Jan 2024 - Time:
08:00:00(24-hour format) - Timezone:
GMT,EST,-0500, etc.
Timezone considerations: Using GMT/UTC is recommended for consistency. Local timezones work but can cause confusion when daylight saving time changes.
How Apps Use pubDate
| App Behavior | How pubDate Affects It |
|---|---|
| Episode ordering | Sorted newest to oldest by pubDate |
| "New" indicators | Episodes with recent pubDates marked as new |
| Auto-download | New pubDates trigger automatic downloads |
| Notification timing | Push notifications based on pubDate |
| Feed polling | Apps check for pubDates newer than last check |
Scheduling Episodes
Setting a future pubDate creates a scheduled episode:
<!-- Published immediately -->
<pubDate>Mon, 15 Jan 2024 08:00:00 GMT</pubDate>
<!-- Scheduled for next week -->
<pubDate>Mon, 22 Jan 2024 08:00:00 GMT</pubDate>
Most hosting platforms support scheduling through their interface rather than manual pubDate editing.
Common pubDate Issues
| Issue | Consequence |
|---|---|
| Future date on live episode | Won't appear in some apps until that date |
| Date in wrong timezone | Episode might appear early/late |
| Invalid format | Feed validation fails |
| Very old date on new episode | Episode might not trigger "new" notifications |
Why It Matters
The pubDate is more than just a timestamp—it controls when and how your episodes reach listeners. Getting it wrong can mean episodes that don't show up, appear out of order, or fail to notify subscribers.
Why pubDate accuracy matters:
-
Episode ordering: Apps sort by pubDate. Wrong dates mean episodes appear in wrong positions, confusing listeners.
-
New episode detection: Podcast apps poll feeds and look for pubDates newer than their last check. An incorrect date might prevent notifications.
-
Subscriber experience: When you publish "Episode 42" but it appears before "Episode 41" due to date issues, listeners get confused.
-
Analytics timing: Download analytics often segment by publication date. Wrong dates skew your reporting.
Strategic pubDate considerations:
| Decision | Impact |
|---|---|
| Publishing time of day | Affects when subscribers get notifications |
| Consistent schedule | Trains audience expectations |
| Timezone choice | Matters for international audiences |
| Back-dating corrections | Can help fix ordering issues |
The scheduling advantage: Using future pubDates to schedule episodes lets you batch-produce content while maintaining consistent release timing. Episodes stay in your feed but don't appear in apps until the scheduled date.
How to Use This in Dispatch
Publication dates are handled automatically with full scheduling support:
Immediate publishing: When you click "Publish," the pubDate is set to the current timestamp and the episode immediately appears in your feed.
Scheduled publishing:
- Set your desired publish date and time in the episode editor
- Save the episode as scheduled
- The episode goes live automatically at the specified time
- Subscribers receive notifications based on their app settings
Timezone handling:
- Set your preferred timezone in show settings
- Schedule times display in your local timezone
- Feed pubDates are converted to proper RFC 822 format automatically
Editing published episodes: Changing the publication date of a published episode updates the feed but won't trigger re-downloads (the GUID remains unchanged). This can help fix episode ordering issues.