Research Guides
The Article Is Live. Did the RSS Feed Publish the Same Story?
A publishing checklist often stops when the article opens in a browser. A subscriber may receive something different: yesterday’s summary, a duplicate entry, or a headline that leads to the wrong page. Treat the feed as a second delivery surface, not a receipt proving that publication succeeded.
This acceptance worksheet is for a small editorial site publishing an RSS 2.0 feed. It checks delivery consistency, not search rankings or subscriber growth.
Start with a publication receipt
Before testing the feed, record the intended article title, public URL, publication time and time zone, and the summary approved for distribution. Keep a copy of the release being checked. This gives an editor something definite to compare with the feed response.
Choose three cases: the new article, an older unchanged article, and a recently corrected article. A check of only the newest headline can miss a change that accidentally republishes the archive.
Compare an entry with its destination
Open the public feed address, then locate the new item. Follow its article link. Compare the headline, destination, and summary with your receipt. Read the summary as a standalone introduction: does it omit an important limitation or imply a stronger result than the article supports?
For example, a fictional article explaining a ten-page manual accessibility sample should not reach subscribers as “We audited the whole website.” Fix that discrepancy even if every XML field is technically valid.
RSS 2.0 requires channel title, link and description fields. An item must contain at least a title or description; its link can point to the full story. These are format requirements, not an editorial accuracy check. RSS 2.0 specification
Keep identity separate from edits
Record each sampled item’s identifier before and after a routine correction. RSS readers may use the guid value to decide whether an item is new. A GUID marked as a permalink must identify a URL readers can open; a non-URL identifier needs the appropriate isPermaLink setting. RSS identifier guidance
Our recommended acceptance rule is simple: correcting a typo in an existing article should not silently give it a fresh identity. Document deliberate republication separately. Test the actual feed reader your team uses rather than assuming all readers handle updates identically.
Test dates and difficult text
RSS publication dates describe publication, while the channel’s lastBuildDate describes when channel content changed. The specification notes that a future item date can cause an aggregator to delay displaying it. RSS date definitions
Compare the recorded timestamp with the intended release, including its offset. Then examine a title or summary containing an ampersand, quotation mark or non-English character. Does the XML parse, and does the reader show the intended words rather than broken markup? Validate the public feed with the W3C Feed Validation Service, then perform the reader check too. Passing validation alone does not establish that the correct article was distributed.
Save a compact acceptance record
- Feed URL and retrieval time:
- Article URL and expected headline:
- Summary matches the article’s scope: yes / no / unresolved
- Identifier unchanged for an ordinary correction: yes / no / not applicable
- Publication timestamp checked with time zone: yes / no
- XML validation result and any warnings:
- Feed-reader result and reader used:
- Older sample still present as expected:
- Owner and next action:
If the feed deliberately contains only recent entries, record that window rather than labeling every omitted older article a failure. Preserve the existing window during unrelated publishing work.
Close the task without overstating it
A useful completion note is: “The new article appears in the live feed; its title, summary and destination match, and the corrected sample retained its identifier.” If the reader has not refreshed, record that observation separately from what the server returned.
For the wider publication check, use the deployment, cache and search evidence worksheet. A healthy feed helps deliver content consistently. It does not prove readership, search indexing or earned backlinks.