Echo RSS Feed Post Generator Plugin for WordPress is a WordPress plugin that pulls content from external RSS feeds and publishes it on a site as ordinary blog posts. It also works in the opposite direction, turning a site’s own posts into custom RSS feeds that other tools can consume. It is built for site owners who want to run an autoblogging operation, populate a niche news site, or keep a network of blogs stocked without writing every article by hand.
The plugin comes from CodeRevolution, a developer with a track record on CodeCanyon, and it has been on sale long enough to accumulate 1,977 purchases and a 4.86 out of 5 average across 132 reviews. That volume matters: it means the code has been tested against a wide range of hosting setups and feed formats by real buyers, not just a demo environment.
What the plugin actually does with feeds and posts
At its core, the plugin reads a feed and writes a post. The interesting part is how much control sits between those two steps. Feed sources are managed from a single admin screen, and each source can be switched on or off independently. If the exact feed address is unknown, entering the site’s homepage lets the plugin look for the feed itself, which saves time when a publisher has buried the link or renamed the endpoint.
Format support is broader than the average aggregator. The plugin reads RSS 0.9 through 2.0 and Atom 0.3 and 1.0, and it understands a long list of optional RSS modules, including Media RSS for attached media, Dublin Core for metadata, and GeoRSS for location data. In practice, this means feeds from podcast hosts, news wires and niche publishers that use non-standard extensions will still import with their extra fields intact rather than arriving as bare text.
Filtering and rewriting before anything goes live
The filtering layer is where this product separates itself from simpler feed-to-post tools. Editors can blacklist words so that posts containing them are skipped entirely, or require certain words before a post is accepted. Duplicate checking runs on title, URL, or both, which prevents the same story being republished when several feeds pick it up. Search-and-replace rules using regular expressions let a site owner rewrite URLs, strip broken markup, or swap in their own affiliate identifiers. There is also a title-length filter for feeds that publish unwieldy headlines.
Content enrichment and post templates
Many feeds only expose a short summary. The plugin can follow the original article link and extract the full body text using its own readability engine, a feature aimed squarely at sites that need substantial content rather than teasers. Templates then decide how that content is assembled. Each feed can have its own template, with variables drawn from the post, the source feed, or values defined by the site owner. A random sentence generator adds variation so that repeated imports do not read identically, and custom HTML blocks allow nofollow attributes, embedded video players, or WordPress shortcodes inside generated posts.
Categories and tags are handled with similar care. A feed can be mapped to one or more existing categories, or the plugin can create new ones automatically. It can also scan imported text for category names already on the site and attach them, and it can add a list of tags at random to broaden keyword coverage. Authorship is configurable too: posts can be credited to a fixed user, a random user, or the original writer.
Scheduling and the reverse direction
Automation runs on a built-in pseudo-cron system, so no external scheduler needs to be configured on the server. Individual feeds can be set to process on every run or only after a set number of runs, and update intervals can be randomised within a range so that publishing patterns look less mechanical. The plugin also supports XML-RPC pings, letting an external service notify the site when a source has updated. On the output side, the same rule engine can build unlimited custom feeds from the site’s own posts, which is useful for syndication, app feeds, or newsletter pipelines.
Where this fits and where it does not
The clearest fit is a content site in a niche where authoritative sources publish frequently: trade news, sports, entertainment, or finance. An editor curates a set of feeds, writes filtering rules to exclude off-topic items, assigns categories, and lets the queue fill. The result is a site that stays current without a writing budget for every item.
A second fit is the agency or operator running several sites. Because sources, templates and schedules are all per-feed, one installation can serve very different publications, and the import can be set to publish as draft or pending so a human reviews before anything appears publicly.
A third fit is syndication rather than aggregation. A publisher who wants to expose its archive as clean, filtered feeds for partners or apps can use the reverse feature without touching theme code.
The wrong choice is a small brochure site or a company blog with a handful of posts a year. Feed automation adds administrative overhead and duplicate-content risk for no benefit when there is nothing to aggregate. Nor is it a substitute for editorial judgement on a site where accuracy is the product: the plugin can filter words and follow links, but it cannot verify a claim, and running it unattended on a high-trust publication is a reputational risk rather than a shortcut.
Strengths and limitations
Strengths
- Genuinely deep filtering: banned words, required words, phrase matching, duplicate detection and regex replacement all coexist, which covers most of the cleanup work that aggregators usually need.
- Per-feed templates and per-feed scheduling mean a single install can host several distinct publications without conflicts.
- Full-text extraction from the source URL solves the most common complaint about feed imports, namely that the feed only carries a teaser.
- Broad format and module support, including Atom, Media RSS and Dublin Core, reduces the number of feeds that fail to import cleanly.
- Built-in cron removes a common shared-hosting obstacle, since many budget hosts limit or disable real system cron.
- Source files in PHP, JavaScript and CSS are included, so agencies can extend behaviour rather than work around it.
- Works alongside the block editor and major page builders, with shortcodes and Gutenberg blocks for displaying imported content.
Limitations
- The feature set is large enough that configuration is a project in itself. Getting a clean result requires understanding how filtering, templates and scheduling interact, and the vendor’s documentation page is the main reference.
- Copyright and licensing sit entirely with the site owner. The plugin will happily republish full articles from sources that never granted permission, and nothing in the tool prevents that.
- Full-content extraction depends on the structure of the source page. Sites that render articles with heavy JavaScript or aggressive paywalls will not always yield usable text, and the vendor does not publish a success rate.
- Pseudo-cron only fires when the site receives traffic. On a low-traffic site, scheduled imports can drift well behind the configured interval.
- The declared browser compatibility list includes Internet Explorer 6 through 11, which is implausible for a current WordPress plugin and suggests that field has not been maintained. It should not be read as a meaningful signal either way.
- Randomised sentences and random tag lists improve variety but can produce awkward phrasing, so output still benefits from a review pass.
How it compares with the wider category
Feed-to-post tools sit on a spectrum. At one end are lightweight plugins that map a feed to a category and publish on a schedule; they take minutes to set up and offer almost no control. At the other end are hosted autoblogging services that charge monthly and keep the processing on their own servers.
Echo sits firmly in the self-hosted, high-control segment. Compared with the simple plugins, it offers materially more: regex rewriting, full-text extraction, per-feed templates and reverse feed generation are features those tools simply do not have. The trade-off is setup time and a steeper learning curve.
Compared with hosted services, the advantage is cost and data ownership. A one-time $49 purchase with no per-post or per-site fees is cheaper than most subscriptions within a few months, and the content never passes through a third party. The disadvantage is that processing load, cron reliability and updates become the site owner’s responsibility rather than the vendor’s.
Compared with writing original content or hiring writers, the plugin is not really a competitor. It is a distribution and curation tool. The sites that get value from it treat it as an editorial assistant that sources and formats material, not as a replacement for having a point of view.
Frequently Asked Questions
Does Echo RSS Feed Post Generator Plugin for WordPress create duplicate content?
It can, if configured carelessly, but the plugin includes tools to prevent it. Duplicate checking compares titles and URLs so the same story is not imported twice, and templates, random sentences and tag variation alter how posts render. Search engines still see republished text as duplicate unless it is rewritten, so most users combine the plugin with partial-content imports or original commentary.
Can it import the full article when the RSS feed only shows a summary?
Yes, in most cases. The plugin can visit the original article URL and extract the full body text using its own readability engine, which is designed for exactly this situation. Results depend on how the source site is built; pages that load content via JavaScript or sit behind a paywall may not extract reliably, and the vendor does not state a success rate.
Does the plugin need a real cron job on the server?
No. It ships with a pseudo-cron system that triggers feed processing when the site receives visits, so no external scheduler has to be configured. The catch is that a site with very little traffic will process feeds less often than scheduled, and cron operations can be disabled separately without switching off the rest of the plugin.
Can it generate RSS feeds from an existing WordPress site?
Yes. The same rule engine that imports feeds can build an unlimited number of custom feeds from the site’s own published posts. That makes it useful for syndication partners, mobile apps or newsletter systems that need a filtered feed rather than the default WordPress one, and the rules can limit which posts are included.
Verdict
Buy this if the goal is to run one or more content sites fed by external sources and the operator is willing to spend time on filtering, templates and scheduling. The depth of control, the full-text extraction and the reverse feed generation justify the one-time price, and the review history suggests the code holds up in production. Do not buy it for a small site with no aggregation needs, and do not buy it expecting to skip editorial review, because the plugin handles mechanics rather than judgement. Anyone uneasy about republishing material they do not own should resolve that question before installing anything.
