How to move an RSS feed
Save the current feed before your platform or domain changes. The copy gives you something concrete to compare with the replacement while you can still fix it.
1. Capture a meaningful overlap
Download the old and proposed feeds as XML or JSON. Include enough recent entries for you to see posts in both samples. If your old feed shows 20 items and your new one shows 10, several old items will be absent by design. Run the comparison with files exported around the same time.
2. Preserve the identifier readers know
Some feed readers use an entry ID to recognize an article they have seen. A new ID for the same article can make it appear unread again. Reuse the original RSS guid, Atom id, or JSON Feed item id when the platform allows it.
<guid isPermaLink="false">dispatch-042</guid> <link>https://dispatch.example/library/42</link>
If the URL moved, keep the old ID and test a permanent redirect from the old article URL to its new destination. If the ID changed and the URL stayed put, find out whether the new platform can import or override IDs. If both changed, check unmatched entries by hand against the titles and publication dates.
3. Redirect the old feed URL
When you control the old address, redirect it permanently to the new feed URL with HTTP 301 or 308 and keep it working. Test the exact old URL from outside your hosting account. The destination should respond successfully with the feed itself. Update the feed discovery link in your site’s HTML and any subscription buttons. Add the new feed address directly in the readers your audience uses and verify that recent entries open correctly.
4. Keep a rollback copy
Save the comparison and the old feed address. Keep control of the old domain and hosting route during the transition. If an entry floods subscribers or a feed stops updating, the saved copy helps distinguish a publishing problem from an ID or redirect change.
See the RSS Best Practices Profile and Atom specification for the underlying ID rules.
Compare your feeds →