What it is
RSS and Atom are decades-old syndication formats. For agents building fresh-content pipelines (news summarisers, topic monitors), a feed is radically cheaper than scraping listing pages.
Remediation Prompt
I want to improve my site's agent readiness. Please implement the following fix for RSS / Atom Feeds across our codebase. Instructions: Please fix the RSS / Atom Feeds issue on my site so it is agent-ready.
How we test it
GET /— parse HTML head for<link rel="alternate" type="application/rss+xml">and<link rel="alternate" type="application/atom+xml">- Also check Link headers
- Fetch the first advertised feed and validate minimum structure
Pass Warn Fail Matrix
| Condition | Status | Score |
|---|---|---|
| Link present + feed fetches + parses as RSS 2.0 / Atom 1.0 / RSS 1.0 with ≥1 item | pass | 1.0 |
| Link present but feed 404/malformed | warn | 0.4 |
| No link at all | not_applicable (most sites aren't content feeds) | — |
Remediation Prompt
If your site publishes content (blog, news, changelog, releases), add an RSS or Atom feed.
1. Generate an Atom 1.0 feed at /feed.xml or /atom.xml including at least the 20 most recent items.
2. Each entry needs: <title>, <id>, <updated>, <link rel="alternate" href="..." />, and <summary> or <content>.
3. Announce the feed in your HTML head:
<link rel="alternate" type="application/atom+xml" title="Example Blog" href="https://example.com/feed.xml">
4. Also add an HTTP Link header on the homepage:
Link: </feed.xml>; rel="alternate"; type="application/atom+xml"
Atom is preferred over RSS for new sites (cleaner spec, better internationalisation), but RSS 2.0 is equally acceptable.
Test Fixtures
pass-atom.xmlpass-rss.xmlwarn-dead-link.jsonna-none.json