Feed publishing checklist
Use this checklist on the URL your subscribers will actually use. Save the response and run it through the workbench before testing in a reader.
Check the published response
- Open the URL in a signed-out browser. It should return the feed without a login, an interstitial, or a branded error page. If the URL redirects, check that the final address is the published feed.
- Use a suitable response type. Common choices are
application/rss+xml,application/atom+xml, andapplication/feed+json. Serve UTF-8 consistently. - Add a feed discovery link to the
<head>of the publication’s homepage and link visibly to the feed from the site.
<link rel="alternate" type="application/rss+xml"
title="Field Notes RSS" href="/feed.xml">
Read at least three entries
- Check the feed title and homepage link. Each entry should have the headline or content a reader needs to recognize it.
- Check that each identifier is unique in the feed and remains stable when an existing article is updated. Use explicit HTTP or HTTPS article links that resolve from a fresh reader.
- Use RFC 3339 dates for Atom and JSON Feed and an RFC 822-style date for RSS. For example, the same publication time can be
2026-11-12T13:00:00Zin JSON Feed andThu, 12 Nov 2026 13:00:00 GMTin RSS. - Open sample articles and any enclosures in a reader. Check that the attachment remains accessible when signed out and that its MIME type matches the media.
Repeat after publishing
Subscribe to your own feed in a reader and publish a new entry. Verify that the new one appears once and an older one keeps its identity. FourthWeb checks a local copy for common issues. Testing a reader confirms delivery, rendering, and update behavior at the published address.
Format references include the RSS 2.0 specification, Atom specification, and JSON Feed 1.1 specification.
Check a feed file →