RSS and Atom Feeds: Why Your Blog Still Needs One
RSS never died, it just stopped being fashionable. Here is what a feed gives you that no algorithm does, how RSS and Atom differ, and how to check yours actually works.
An RSS or Atom feed is a machine-readable list of your recent posts that lets readers subscribe in a feed reader and be notified of new writing, with no algorithm deciding what they see. RSS 2.0 and Atom 1.0 do the same job; Atom is the stricter specification, and publishing either is enough.
RSS has been declared dead roughly once a year since Google Reader closed, and it keeps not dying. It remains the only widely-supported way for someone to say "tell me when this person writes something" without an account, an algorithm, or a company in between. For a blog you own, that is the whole point.
What a feed actually buys you
A feed is a small XML file listing your recent posts with titles, links, dates and summaries. A reader subscribes once and sees everything you publish afterwards, in order, with nothing filtered out. Compare that with the alternatives: social platforms show a fraction of your followers whatever suits them that week, and email lands in a promotions tab.
The audience is smaller than it was, and more valuable than it looks. Feed subscribers are disproportionately the people who link to you, quote you, and come back. Several aggregators, newsletter tools and link-blogs also consume feeds automatically, so a missing feed quietly removes you from a distribution layer you never see.
RSS or Atom? It barely matters
Both formats do the same job. The practical differences:
- RSS 2.0 is older and more widely recognised by name. Dates use the RFC 822 format, and the specification leaves more open to interpretation.
- Atom 1.0 is a stricter IETF standard. Dates use RFC 3339, every entry needs a stable unique id, and content types are explicit.
- Every feed reader supports both. No reader has refused RSS for years, and none has refused Atom.
Publishing one is fine. Publishing both costs almost nothing if your platform generates them, and removes the question entirely. What matters far more than the format is that the file is valid and that people can find it.
Autodiscovery: the step most sites miss
A feed nobody can find is not doing any work. Most readers never type a feed URL; they paste your homepage and expect the reader to work it out. That only happens if your pages advertise the feed in the head:
<link rel="alternate" type="application/rss+xml" title="Blog (RSS)" href="/rss.xml">
<link rel="alternate" type="application/atom+xml" title="Blog (Atom)" href="/atom.xml">Serve the feed at a conventional path as well. Readers and crawlers probe /rss.xml, /feed and /atom.xml, and answering on more than one of those costs nothing but a route.
How to check yours actually works
Feeds fail quietly, because nothing on the page breaks when they do. Four checks catch nearly everything:
- It returns 200 and a feed content type, not
text/html. Fetch it with curl rather than a browser, which will happily render a broken file. - It is well-formed XML. One unescaped ampersand in a post title breaks the whole document for every subscriber at once.
- Dates are right. A wrong or missing timestamp puts your newest post at the bottom of somebody's reader, or hides it entirely.
- Links are absolute. Relative URLs resolve against the reader, not your site, so they lead nowhere.
A feed is the one distribution channel you own outright. No ranking, no reach, no rules change.
Generate it, do not maintain it
The one rule worth insisting on is that the feed should be generated from the same source as the posts. A hand-maintained feed goes stale the first busy week, and a stale feed is worse than none, because subscribers conclude you stopped writing.
Inkwell publishes an RSS feed per site, generated from your published posts, so it stays current as you write with nothing to remember. The details are in the documentation. If you are weighing up how much of your distribution you actually control, that argument runs through owning your content, and pairs naturally with running your own newsletter.
Frequently asked questions
Is RSS still relevant in 2026?
Yes, though the audience is smaller than its peak. It remains the only widely-supported way to follow a site without an account or an algorithm, and feed subscribers tend to be the readers who link to and quote your work. Aggregators and newsletter tools also consume feeds automatically.
What is the difference between RSS and Atom?
They do the same job. RSS 2.0 is older and looser, using RFC 822 dates. Atom 1.0 is a stricter standard with RFC 3339 dates and a required unique id per entry. Every modern reader supports both, so the choice rarely matters in practice.
How do readers find my feed?
Through autodiscovery. Add a link rel="alternate" tag for the feed in your pages head, and most readers will find it when someone pastes your homepage URL. Also serve it at a conventional path such as /rss.xml or /feed, which readers and crawlers probe directly.
Why is my RSS feed not updating in readers?
Usually a date problem or a caching one. Check that each item has a correct publication date and that the feed itself is not served with a long cache lifetime. Also validate the XML: a single unescaped ampersand from a post title breaks the whole document for every subscriber.
Ready to host your own blog?
Inkwell is free, open-source, and self-hosted — your content, your server, your rules. Deploy in minutes on .NET 10.