RSS Feeds: Problem of no Persistent RSS Feed Settings (CRUD), Manual Refresh, Timed Refresh & Keyword Management Improvements#2593
I’m using Publer RSS feeds heavily for automated product and ecommerce posting. The current RSS workflow requires recreating feeds for basic changes, which causes configuration loss and slows iteration.
Below are specific, actionable improvements that would significantly improve usability, reliability, and scalability for power users.
Feature Requests
1) Manual RSS Refresh Button
Problem:
There is no way to immediately re-fetch an RSS feed after updates or fixes.
Expected behavior:
Each RSS feed has a “Refresh Now” button
Clicking it immediately re-fetches the feed and processes new items
Useful for testing, feed fixes, and content updates
Current workaround:
Users must delete and recreate feeds, losing configuration.
2) Configurable RSS Refresh Interval
Expected behavior:
Allow users to configure refresh frequency per feed:
15 min
30 min
1 hour
4 hours
Daily
Existing feeds can keep the current default interval
Why this matters:
Ecommerce and affiliate feeds update frequently
Posting delays directly impact revenue and engagement
3) Persistent RSS Feed Settings (CRUD)
Problem:
RSS feed settings are lost unless the feed is recreated.
Expected behavior:
Full CRUD (Create, Read, Update, Delete) support for:
Feed name
Feed URL
Include keywords
Exclude keywords
Refresh interval
Users should be able to edit these fields without deleting and recreating the RSS feed.
4) Comma-Delimited Keyword Input
Expected behavior:
Keyword fields accept comma-separated input
Multi-word keywords are preserved as a single token
Example input:
grill, smoker, bbq, barbecue, pellet, charcoal, steak seasoning, jerky
(Note: “steak seasoning” contains a space and should remain a single keyword.)
UI behavior:
Parse input
Render as individual keyword chips after entry
Benefits:
Faster setup
Fewer UI interactions
Much better experience for power users managing multiple feeds
Why This Matters
These changes would:
Reduce user friction
Prevent configuration loss
Improve RSS feature adoption
Support high-volume workflows (ecommerce, affiliate marketing, media publishing)
Happy to provide examples or walk through real-world usage if helpful.
Thank you for considering!