Ensure your RSS crawler is identifiable
It is important to indicate to a server where its traffic is coming from. It helps podcast hosting companies understand who is consuming their RSS feeds, and can also help podcasters know where their podcast is being consumed.
- If you run a central RSS crawler, please ensure this is identified with a user-agent.
- Consider reporting back subscriber counts, like this example from Overcast:
Overcast/1.0 Podcast Sync (123 subscribers; feed-id=456789; +http://overcast.fm/
Consider saving your bandwidth, and that of podcast hosts, by using the accept-encoding header to request that RSS feeds are GZIPped. RSS feeds are highly compressible.
Consider using PodPing or WebSub to be alerted when a new episode of a podcast is published. This will help your server infrastructure avoid unnecessary feed polling, and ensure that podcasts are promptly updated with new episodes.
Page authors: jamescridland