Ingestics vs WP RSS Aggregator — curator-first vs. ingester-first
WP RSS Aggregator’s core model is curation and display — pulling feed items into a list/grid for visitors to browse, often linking back to the original source rather than republishing full native posts. Ingestics’s core model is ingestion and publishing — items become real WordPress posts (with duplicate detection, optional AI rewrite, and full editorial control), and it also handles REST API sources that WP RSS Aggregator doesn’t touch.
What does WP RSS Aggregator do better?
Purpose-built curation UI (feed merging, item filtering, “read more” linking) is more polished for pure aggregation/curation use cases where you don’t want to republish full content as native posts; simpler mental model if display-only aggregation is genuinely all you need.
Side by side
| Criteria | Ingestics | WP RSS Aggregator |
|---|---|---|
| Output model | Native WordPress posts | Curated feed-item list |
| REST API support | Yes | No |
| Content transformation | AI rewrite, field mapping | None — items typically shown as-is |
| Duplicate detection | Title + URL post matching | Feed-level dedup |
| Authentication | Full range including OAuth2/SigV4 | None — feeds are typically public |
Decision guide
Choose WP RSS Aggregator if: Want a curated links/headlines widget pointing back to sources, RSS-only.
Choose Ingestics if: Want incoming items to become real, editable, SEO-indexable WordPress posts, and need API sources too.
Four Ingestics editions
One install, license-gated. Start free on WordPress.org, upgrade by entering a key — no reinstall, no reconfiguration, no data loss.
Switching questions
Does Ingestics create real posts, or just display feed items like WP RSS Aggregator?
Ingestics publishes native, editable WordPress posts (with title, content, featured image, taxonomy, and attribution) — not just a display-layer list of feed items linking back to the source.
Can I keep using WP RSS Aggregator’s curated widget alongside Ingestics?
Yes, they can coexist since they serve different output models — but most users switching to Ingestics do so because they want the RSS content to become indexable posts rather than a linked-out widget.
Does Ingestics require authentication for public RSS feeds?
No — like WP RSS Aggregator, public RSS/Atom feeds require no authentication in Ingestics. Authentication options (OAuth2, AWS SigV4, etc.) only apply when connecting to authenticated REST API sources.
Comparisons based on each plugin’s public documentation and WordPress.org listing as of the page’s last-updated date. Feature sets change — verify current capabilities directly with each plugin before deciding.