{"canonical_url":"https://engineer.company/glossary/feed/","content_markdown":"# Feed\n\n## What it is\n\nA feed is a file at a fixed address that lists a site's latest items in a form\nsoftware can read, each with a title, a date, an identifier that does not change\nand usually the text itself, so that a program can fetch it on a schedule and\nshow a person only what is new. It also goes by web feed or syndication feed,\nand many people say “RSS feed” for any of them, whatever format sits underneath.\n\nWhat sets it apart is the direction of travel. A newsletter is pushed: the\npublisher keeps a list of addresses and sends to every one. A feed is pulled:\nthe publisher leaves one file on the server, and each subscriber’s feed reader\nfetches it, compares it with the copy it saw last time and keeps the items it\nhas not met before. The publisher never learns who subscribed, the subscriber\nnever hands over an email address, and leaving is a matter of deleting one line\nin a reader.\n\nThree formats carry nearly all feeds on the web. RSS 2.0 is XML, dates its items\nin the style of RFC 822 (`Sat, 07 Sep 2002 00:00:01 GMT`) and is declared frozen\nby its own specification. Atom, published by the IETF as RFC 4287 in December\n2005, is also XML and stricter: every feed and every entry carries a permanent\n`id` and an `updated` timestamp in RFC 3339 form, and an author must be named\nsomewhere. JSON Feed, at version 1.1 since August 2020, says the same things in\nJSON for developers who would rather not parse XML.\n\nA page tells software where its feeds live with `\u003clink rel=\"alternate\"\u003e`\nelements in its head, each naming a media type: `application/rss+xml`,\n`application/atom+xml` or `application/feed+json`. That is how a reader finds\nthe feed from nothing more than the site’s ordinary address.\n\n## Why it matters\n\nThe first decision is whether to publish one at all. A feed is one more output\nto template, validate and keep stable for years, for an audience smaller than a\nsocial network’s. Against that, it is the only subscription channel that needs\nno platform, no account and no mailing list, and no ranking algorithm sits\nbetween a post and the people who asked to see it.\n\nThe second decision is which formats. Some readers take only RSS and some only\nAtom, and there is no telling in advance which one a given subscriber’s reader\nwants. Publishing both covers the gap for the price of a second template, and\nJSON Feed adds a third for software written by people who would rather handle\nJSON. Each extra format is another file to keep in step: same items, same\nidentifiers, same dates.\n\nThe third is how much text to put in each item. A full-text feed lets people\nread the whole piece in their reader, which is much of the point of a reader,\nand costs the publisher page views. A summary-only feed sends every reader to\nthe site for each item. Neither is wrong; the choice is between how far the\nwriting travels and how often the page itself is visited.\n\nWhatever the answers, the address is a commitment. Readers poll the URL they\nwere given, on a schedule each reader picks for itself (RSS lets a feed suggest\none in minutes with `ttl`, and a reader may ignore it), and many keep polling\nfor years. Once a feed address is out, it stays.\n\n## What it looks like in practice\n\nThis site publishes all three formats from its home page, at\n`/index.xml` (RSS), `/atom.xml` (Atom) and `/feed.json` (JSON Feed). The\n[credits page lists them and the services that check them](/credits/): all three\ncarry the full text, and there are two XML feeds rather than one because some\nreaders take only one of the two and neither is reliably the one. The\n[W3C Feed Validator](https://validator.w3.org/feed/) checks the Atom and RSS\nfeeds, and the [JSON Feed Validator](https://validator.jsonfeed.org/) checks the\nthird, which the W3C service does not cover because it predates the format. The\nW3C service warns that most entries share a modification date. The page keeps\nthat warning rather than hide it: the dates come from git history, and most of\nthe pages were written in the same few commits.\n\nThe\n[contact page offers the feeds as a way to follow the company without an account](/contact/),\nnext to its social profiles, and repeats that all three carry the full text of\neverything published.\n\nNone of the three is written by hand or produced on request. In\n[the project that built the site](/portfolio/built-a-multilingual-hugo-site-in-3-languages/),\nthe site is generated entirely at build time with no runtime backend, every page\nis published in several representations from one content tree, and the home page\nadds three syndication feeds and an installable application manifest on top.\n\n## Where it goes wrong\n\n**Every old item turns up again as new.** After a redesign, a domain move or a\ntemplate change, subscribers see dozens of items they read months ago. Readers\nrecognise an item by its identifier, Atom’s `id`, RSS’s `guid` or JSON Feed’s\n`id`, and when that string changes, the item is new to them. RFC 4287 is\nexplicit that an entry’s `id` must survive relocation, migration and\nrepublishing. A permalink makes a good identifier only while the site promises\nto keep the old string after a move. In RSS, also say what the `guid` is: the\nspecification defaults `isPermaLink` to true, and this site’s RSS template\nwrites `isPermaLink=\"true\"` anyway, because a reader that guesses the other way\nre-imports every item as a duplicate.\n\n**The feed claims to have changed on every build.** The feed-level date moves\neach time the site is rebuilt, whether or not anything was published, so\nsoftware that watches that date for news fires on nothing. The cause is a\ntemplate that stamps the clock at build time. RSS defines `lastBuildDate` as the\n“last time the content of the channel changed”, and Atom’s feed-level `updated`\nmeans the same, so the date should come from the newest item instead. This\nsite’s Atom template takes it from the newest entry for exactly that reason.\n\n**The feed stops parsing after a typography change.** Readers report the feed as\nbroken, and a validator points at an undefined entity in the first article with\na curly quote. XML predefines five named entities, `lt`, `gt`, `amp`, `apos` and\n`quot`, while HTML defines hundreds more. A Markdown renderer that writes quotes\nand dashes as HTML’s named entities produces markup that is fine in a page and\nfatal inside an XML element. Escape the HTML before it goes in, which is what\nAtom’s `type=\"html\"` content expects, or wrap it in a CDATA section, which the\nRSS Best Practices Profile allows for `content:encoded`. This site’s Atom\ntemplate escapes its content, and the comment beside it records that, written\nraw, the feed did not parse at all.\n\n**Subscribers drift away after a move, and nobody hears about it.** A feed has\nno unsubscribe button and no list that shrinks, so the only sign is silence. The\nfeed’s address changed, or its file was removed, and every reader polling the\nold URL now gets an error. Keep the old address answering, either with the feed\nitself or with a permanent redirect. This site keeps its RSS at `/index.xml`,\nthe default path of the generator it is built with, because that is the address\nexisting readers poll; and in a language it does not announce, it still writes\nwell-formed feeds carrying zero items, so a reader gets a valid document rather\nthan a 404.\n\n**Two feeds collapse into one in a subscribe dialog.** A browser extension or a\nreader offers a single feed where the page declares two. Two alternate links\nwith the same type and the same title look to such a tool like one feed, and it\nlists whichever it saw last. Give each its own title; this site’s pages name\ntheirs with the site’s name followed by “(RSS)”, “(Atom)” or “(JSON Feed)”.\n\n## Further reading\n\n- [RFC 4287: The Atom Syndication Format](https://www.rfc-editor.org/rfc/rfc4287)\n  — the IETF standard, with its required elements, permanent identifiers and RFC\n  3339 dates.\n- [RSS 2.0 Specification](https://www.rssboard.org/rss-specification) — the RSS\n  Advisory Board’s text of the frozen format, element by element.\n- [JSON Feed Version 1.1](https://www.jsonfeed.org/version/1.1/) — the same idea\n  expressed in JSON, and what changed from version 1.0.\n- [HTML Standard: link type “alternate”](https://html.spec.whatwg.org/multipage/links.html#link-type-alternate)\n  — how a page points software at its feeds.\n- [W3C Feed Validation Service](https://validator.w3.org/feed/) — checks an RSS\n  or Atom feed by its address and explains each warning.\n\n\u003chttps://engineer.company/glossary/feed/\u003e\n","date_modified":"2026-11-08T05:31:18Z","description":"How a web feed works, why a site might publish RSS, Atom and JSON Feed side by side, and the mistakes that make readers duplicate or lose items.","formats":{"gemtext":"https://engineer.company/glossary/feed/index.gmi","gopher":"https://engineer.company/glossary/feed/gophermap","html":"https://engineer.company/glossary/feed/","json":"https://engineer.company/glossary/feed/index.json","markdown":"https://engineer.company/glossary/feed/index.md","pdf":"https://engineer.company/glossary/feed/index.pdf"},"kind":"page","language":"en","title":"What is a feed?","url":"https://engineer.company/glossary/feed/","version":1}