FeedwrappedBot

feedwrapped downloads podcast RSS feeds so it can show what they contain. This page is what its User-Agent points at. If you run a feed and want to know what this traffic is, you are in the right place.

How it identifies itself

Every request feedwrapped makes carries this header, without exception:

User-Agent: FeedwrappedBot/0.1 (+https://feedwrapped.com/bot)

The version is major and minor only, so a patch release will not change what you see in your logs. The bot does not pretend to be a browser and does not vary its User-Agent between requests.

What it does

It is not a spider. It fetches one URL, because a visitor typed or clicked it. It never follows links out of a feed, never discovers feeds on its own, and never walks a site. If nobody asks for your feed, feedwrapped never contacts you.

A single lookup makes at most these requests:

HEAD on the feed URL, to read ETag and Last-Modified. Skipped the very first time, when there is nothing to compare against.
GET on the feed URL, sent with If-None-Match and If-Modified-Since — and only when the HEAD suggested something changed. A 304 costs no body.
GET on the cover art, once, when drawing the shareable card. This is the only request that goes anywhere other than the feed URL.

How it caches

Each feed is downloaded once. The body is stored, along with whichever validators you sent, and reused from then on.

Inside a 60 minute window the stored copy is served and nothing at all is sent to your server.
After that, the next visitor triggers one HEAD. If your validators match what we hold, the copy is marked current and no download happens.
Only a feed that genuinely changed is fetched again.

In practice a popular feed costs you one small HEAD per hour, however many people look at it.

Limits it holds itself to

Feed size	stops reading at 16.0 MB
Feed timeout	20 seconds
Revalidation timeout	8 seconds
Cover art timeout	6 seconds
Redirects followed	at most 5
Schemes	http and https only
Compression	gzip and deflate accepted
Concurrency	visitors arriving together share one lookup

If you would rather it stayed away

It does not read robots.txt, because it acts on a specific request from a person rather than crawling on its own schedule — the same reasoning a browser applies. That said, it identifies itself plainly so you can decide. Refusing requests whose User-Agent contains FeedwrappedBot is enough to block it completely, and it will report the refusal to whoever asked.

Any 4xx or 5xx is passed straight back to the visitor and nothing is stored, so a block is not retried in a loop.

Back to feedwrapped