To merge multiple RSS feeds into one in WordPress, you add each feed as a source in an aggregator plugin, group the sources in a folder, and publish that folder on a page as a display. One stream, every source, refreshing on its own schedule. Setup runs about fifteen minutes, and most of that is pasting URLs.
Following several sites without a merge usually means a row of browser tabs and links copied over to your site by hand. A combined stream replaces that routine. This walkthrough builds one in Aggregator using three real feeds, with a screenshot of every screen involved, and the same steps apply to whichever feeds you follow.
Online RSS Combiner or WordPress: Which Should You Use?
An RSS combiner is a tool that takes several feed URLs and produces one feed URL. RSS.app, Feedspot’s RSS Combiner, and rssrssrssrss.com (yes, that’s a real URL) all work the same way: paste in a list of feeds, copy the merged link they return. The whole exchange takes about two minutes.
Where that link is headed settles the choice. Feeding a feed reader or a newsletter app? A web combiner is enough. Building something visitors read on your own site? A combiner can’t take you there. Its URL sits on servers you don’t control, capped by item limits you didn’t choose, and it stops working if the service shuts down or paywalls its free tier. Even a working merged URL is still raw XML, not a page a visitor can read.
Laid out side by side:
| The question | Online combiner | Merged in WordPress |
|---|---|---|
| How long to set up | Two minutes | Fifteen minutes |
| Who hosts it | Their servers | Your own site |
| Choosing what gets in | Barely any control | Keyword rules per source |
| A page visitors can read | You solve that yourself | Included |
| When the service shuts down | Your feed dies with it | Nothing changes |
The URL itself is the one thing you don’t give up by choosing WordPress. Aggregator republishes everything it imports as a combined feed on your own domain, at /feed/wprss/ by default, so a feed reader can subscribe to your merge the same way it would to a combiner’s link, minus the third party that can disappear. The rest of this article is the WordPress build: three sources, one folder, one page.
Before You Start: One Plugin and Your Feed URLs
You need two things: Aggregator on your site, and the feed URL of every site going into the merge. Folders, displays, and filtering, the three features this build relies on, come with the Basic plan and up.
Installing the plugin works like any other: Plugins → Add New, search, activate. Finding feed URLs is the harder half, since most sites never link to theirs. Instead of digging through page source, type each site’s address into the Feed Finder below. It returns the feed URL plus a preview of the items currently in it, which doubles as proof the feed is alive. The three URLs in this tutorial all came from it.
The three sources here are WP Tavern, the WordPress.org news blog, and Post Status. Yours can be any public feeds: industry news, niche blogs, your own network of sites. And because the finished page shows headlines and excerpts that link back to each publisher, the format works with feeds you don't own without shortchanging anyone. A rights section near the end covers where that line sits.
Step 1: Add Your Feeds as Sources
From the admin, open Aggregator → Sources and hit Add New. Name the source something you'll recognize in a list, paste the feed URL, save. The plugin checks the feed the moment you save, so a broken or mistyped URL shows up as an error immediately instead of importing nothing for a week.
Do the same for the rest. With the URLs already on your clipboard, each source takes under a minute.
Technically the merge already exists: the plugin is now pulling items from all three feeds on a schedule and storing them in one place. What's left is handling the sources as a single unit, and giving the combined stream somewhere visitors can see it.
Step 2: Put the Sources in One Folder
A folder is the plugin's way of treating several sources as one thing. Head to Aggregator → Folders, create one (this build's is "WordPress News"), and tick the three sources that belong to it.
The payoff comes in the next step, where the display points at the folder rather than at individual sources. It keeps paying after that, too. When a fourth feed joins next month, dropping it into the folder is the entire job. Every display built on the folder picks it up on its own, with no settings touched.
Step 3: Put the Merged Feed on a Page
Now the visible part. Go to Aggregator → Displays and create a new display. When it asks what to show, choose the folder. Pick a template, decide how many items belong on the page, save.
Every display comes with a shortcode and a block. Place either on any page and load it: items from all three sources in one list, ordered by date, each headline linking out to the original article.
That's the core of the merge working. The remaining step controls what gets into it.
Step 4: Keep the Stream On-Topic with Filters
Three active feeds can push dozens of items a day into your stream, and not all of them deserve the spot. Filtering is where WordPress pulls decisively ahead of the online combiners, which mostly pass along whatever the sources publish.
Open a source, switch to its Automations tab, and add a keyword rule. A rule either allows only items containing certain words or blocks the items that do. In this setup Post Status is the busiest source, so its rule reads Contains any: "acquisition", "release"; those are the stories worth passing through from that particular site. The other two sources import everything.
A rule runs on every import from then on. The judgment gets written down once and applied to every new item, with nobody reading three feeds' worth of posts by hand to enforce it.
Past a handful of sources, per-source rules start repeating themselves. Global Automations, on the Pro plan and up, runs if/then logic across every source at once. A three-feed setup doesn't need it; a fifteen-feed one will.
Feed to Post: When a Display Isn't Enough
A display is a stream on a page; the imported items stay in the plugin, not among your posts. Some sites need the other shape. When each incoming item should become an actual WordPress post, one you can edit, categorize, and publish with attribution to its source, that's Feed to Post. Same sources, same folders, posts instead of a stream. It fits news hubs running on your own feeds, licensed content, and sources that have given you permission to republish. The Feed to Post feature page covers it properly; it's too big a topic to bolt onto this one.
For a merged reading stream like the one above, stay with the display. It's lighter, and it keeps aggregated items and your own writing visibly separate.
Test the Merge Before You Trust It
Three quick checks catch nearly everything that goes wrong with a new merge.
First, fetching. The Sources list shows each source's last update time and item count. A source stuck at zero items almost always means the feed URL is wrong or the feed itself is broken; run it through Feed Finder again and see what comes back.
Second, freshness. Sources fetch on an interval, and each one can have its own. A fast-moving site that looks stale on your page needs a shorter interval, not a new feed.
Third, duplicates, which can take a week to show up. When two sources deliver the same item under the same feed ID, Aggregator spots the match and keeps a single copy. Syndicated stories traveling under different IDs slip past that check, so for those, switch on the site-wide option that skips items with duplicate titles and let a keyword rule on the noisier source handle the stragglers.
Merging Doesn't Make the Content Yours
A display deals in headlines and excerpts, and every click delivers the reader to the publisher. Most publishers are fine with that arrangement, since their name stays on each item and the traffic lands on their site. If a source publishes terms for how its feed may be used, follow them.
Feed to Post asks for more care, because the full content lands in your database. Merging transfers no rights to the underlying articles, so keep that workflow to your own feeds, licensed content, or sources that gave permission, and be deliberate about how much you republish. One default helps in both modes: Aggregator attaches a canonical tag to everything it imports, pointing search engines at the original article. That isn't a substitute for permission. It is how honest aggregation stays honest.
One Page Instead of Three Tabs
The finished build is three feeds, one folder, one display, and no more tab rotation. Combining ten sources or fifty works exactly the same way; the folder is what keeps growth cheap.
Merging is one instance of what Aggregator is for: letting content from around the web flow into your site on your rules. A good first project is the set of feeds you already check by hand every day. Put them in a folder, build the display, and give it a week. If the page replaces the old tabs, keep it.
Put your feeds in one place
Add the sources you follow, group them once, and publish a clean stream on your WordPress site. Aggregator gives you the folders, displays, and filters from this walkthrough.
See plans and pricing
