Nourishment in hand: reading a feed as it really looks
Publishing a feed is one thing; seeing what it really says is another. The Feed reader was built for that: paste the body of a feed and read, in your own browser, the shape, the number of entries and what each entry carries.
The tool is the reading hand behind the Feed finder: that one found the address and measured whether it came back as a feed; this one shows what the feed really holds — entry by entry, with title, date and address from the document itself.
And your own feed first: if you publish regularly, paste your own feed body once and count what stands. A feed that is formally sound yet shows no entries is a measured fact — not a judgement of taste.
1. Open the body, not the page
A feed address is not a web page: open it in a browser and it shows the raw text — RSS and Atom as an XML tree, JSON Feed as JSON. Copy that text and paste it into the Feed lezer, and the tool reads out what stands: the shape, the number of repeated blocks and, per block, title, date and address.
If a feed address returns a page instead — HTML instead of nourishment — you are measuring the catch-all trap from the article before: the Feed reader says honestly that HTML was pasted rather than the feed, and the Feed finder points at the address the head does promise.
2. Entries are blocks: what can be read out of them
RSS repeats item: title, link and pubDate, often with a guid as internal name. Atom repeats entry: title, a link as href attribute, and updated as the truth with published as birth date. JSON Feed drops the XML and repeats array elements with title, url and date_published or date_modified. The Feed reader counts those blocks as they stand in the document — no estimate — and lays title, date and address on the table per entry.
What is missing gets named: an entry without a date has no place in time, an entry without an address points nowhere, and a JSON Feed without a version field leaves readers guessing which version they are reading. Those are measured shortfalls, not verdicts: the tool counts them and leaves the decision to you.
3. Reading is not validating
The reader knows the shapes, not the schemas: a feed that looks neat here may still deviate from a stricter validation, and a feed with a sloppiness may read fine here. Conformance is a different question with different instruments; this tool says what stands in the document, not whether the document passes a validator.
And the border of the paste: what you did not paste is not read. What you did paste does not leave your browser — not one byte went to our server, and the addresses in the entries were named but not visited.