How to Combine Multiple RSS Feeds in One Newsletter

You can combine multiple RSS feeds in one newsletter in four main ways: run a separate campaign for each feed, add several feeds to a Mailchimp template, merge the sources into one combined feed, or use a multi-feed platform that selects content for each subscriber.

The right method depends on whether everyone should receive the same content, whether sections must remain separate and whether subscribers can choose their interests. Simply merging everything together solves the input problem but does not decide who should receive each item.

This guide covers that platform-neutral planning process. For the broader commercial overview, see RSS-to-email automation. If Mailchimp is your delivery platform, use the separate multiple RSS feeds in Mailchimp setup guide.

What is a multi-feed automated newsletter?

A multi-feed automated newsletter uses content from two or more RSS or Atom feeds. A system checks those feeds, selects eligible items and passes the result to an email platform on a schedule.

The workflow has four layers:

1. Sources: the websites or applications publishing new content.
2. Feeds: the structured URLs exposing that content.
3. Selection rules: the logic controlling which items and subscribers match.
4. Delivery: the email platform, template, audience and sending schedule.

Keeping these layers separate makes the automation easier to test and maintain. If an email is missing an article, you can determine whether the source failed to publish it, the feed omitted it, a selection rule excluded it or the email platform did not send it.

When multiple feeds are useful

Common multi-feed newsletters include:

• university newsletters combining research, departmental news and events;
• non-profit updates combining campaigns, impact stories and volunteering opportunities;
• association digests combining policy, training and member news;
• publisher newsletters drawing from several topics or regional editions;
• recruitment emails combining vacancies from several departments or locations; and
• internal communications combining posts from several teams.

Multiple feeds are only worthwhile when the sources represent genuinely useful distinctions. Splitting one small blog into many feeds adds complexity without improving the subscriber experience.

Choose the right multiple-feed method

If you only need to place several sources into the same message, start with the native or aggregation options. Use preference-based automation when the important requirement is not merely combining feeds, but deciding which feeds each subscriber receives.

Four ways to handle several feeds

Send one campaign for each feed

Each source powers a separate email automation. This is easy to understand but can create several emails for subscribers interested in more than one subject. It also means maintaining multiple templates, schedules and reports.

Use this approach when the audiences and sending schedules are completely separate.

Add several feeds to a Mailchimp template

Mailchimp supports its own RSS automation and documents the FEED merge tag as a way to add content from more than one feed to an automation. Each feed is referenced in the email template, so this can preserve distinct sections without first creating a combined feed.

This is a sensible native option when every recipient should receive the same sections and someone is comfortable maintaining the template markup. It does not, by itself, make a different selection of feeds for every subscriber.

Review Mailchimp’s current RSS automation guidance before implementation because its campaign interface and sending rules can change.

Merge feeds into one combined feed

A feed merger or aggregator combines items from several sources into one URL, normally ordered by publication date. The email platform then treats the result as a standard single feed.

This works when every subscriber should receive the same combined content. It is less suitable when one high-volume source can dominate the result or when subscribers have different interests.

Aggregation is the quickest answer to “my email platform accepts only one feed URL”. It does not normally preserve the reason each source was separate, such as topic, department or audience preference.

Filter feeds by subscriber preference

A multi-feed automation platform can map sources to audience preferences. One subscriber might receive research and events; another might receive news and vacancies. The campaign remains automated, but the selected content differs by audience segment.

This is the model FlipRSS uses with Mailchimp. It solves both the multiple-source problem and the relevance problem.

Native Mailchimp, an aggregator or FlipRSS?

Mailchimp’s native tools are sufficient for many simple campaigns. A combined feed is appropriate when the only requirement is one mixed stream. FlipRSS is designed for the narrower case where several feeds must remain controllable and their inclusion can depend on a subscriber’s Mailchimp Group membership.

For the implementation details, see the FlipRSS Mailchimp integration and the step-by-step multi-feed Mailchimp guide.

Audit the content sources

Create a simple inventory before configuring any software:

For each feed, confirm:

• it is publicly accessible without a login or cookie;
• the newest items appear promptly;
• every item has a stable title, URL and publication date;
• descriptions and images are usable in email; and
• the feed does not unintentionally repeat items from another source.

If a URL is difficult to locate, follow how to find a website’s RSS feed. Test each source with the W3C Feed Validation Service before connecting it to an automation.

Decide who should receive each feed

Start with subscriber needs rather than your internal website structure. Department names, CMS categories and editorial labels are not always meaningful to readers.

Build a feed-to-preference map:

Preference labels should be clear enough for a subscriber to choose without explanation. Decide whether each feed is:

• universal: suitable for everyone;
• optional: included only when a preference matches; or
• fallback: used when no new preferred content is available.

Do not infer sensitive interests without an appropriate basis. Use information subscribers have supplied and provide a clear way to update their choices.

Balance feeds with different publishing frequencies

A feed publishing ten items per week will overwhelm one publishing monthly if all items are merged by date. Set a maximum item count for each source and decide how sections should be ordered.

Possible balancing rules include:

• show no more than three items from any one feed;
• give a priority feed the first position;
• suppress a section when it has no new content;
• use the newest item from each selected source; or
• cap the total newsletter length after applying per-feed limits.

Test the rules with realistic high- and low-volume weeks. A balanced test containing one item per source will not expose what happens after a burst of publishing.

Prevent duplicated content

The same article can appear in a site-wide feed and a category feed, or in several category feeds. Combining them without a duplicate rule can place the same link in an email more than once.

Choose a stable way to identify duplicates. The permanent article URL is usually more reliable than the title because titles can change. Normalise harmless URL variations such as tracking parameters or trailing slashes before comparing items.

Where possible:

1. remove overlapping sources from the workflow;
2. nominate one feed as the owner of shared items;
3. deduplicate by canonical article URL; and
4. test posts assigned to several categories.

The detailed RSS feed deduplication guide covers this problem separately.

Plan the sending rules

The automation needs an explicit answer for each of these situations:

• What counts as a new item?
• How often are feeds checked?
• What happens when there is no new content?
• What happens when only one optional section has content?
• Can an updated article be sent again?
• How old can an item be before it is ignored?
• What happens when one feed is temporarily unavailable?

A weekly newsletter does not necessarily need a weekly feed check. The system may check more frequently while holding eligible items for the scheduled send. Document the intended behaviour so a skipped campaign can be distinguished from a fault.

Build an email template that tolerates variation

Feed content is inconsistent by nature. Some items have images, some have long descriptions and others provide only a title and link.

The template should:

• remain readable when an image is absent;
• constrain image dimensions without stretching them;
• limit or safely trim long descriptions;
• use descriptive article links;
• avoid relying on scripts or website CSS; and
• hide empty feed sections cleanly.

Test the design with long titles, special characters, missing images, several sources and the maximum permitted number of items. Our guide to presenting several RSS feeds in an email focuses on layout and rendering.

Test the complete workflow

Feed validation alone does not prove the newsletter works. Run an end-to-end test with a non-production audience.

Include cases where:

• two feeds contain the same article;
• one feed is unavailable;
• one subscriber selects every preference;
• another selects only one preference;
• a selected feed contains no new items;
• an article has no image; and
• more items are published than the configured limit.

Check both the content selected and the final rendered email. Record the expected result for each case so future changes can be tested consistently.

Monitor after launch

Automation reduces production work, but it still needs ownership. Review:

• failed or delayed feed checks;
• empty or unusually long campaigns;
• duplicate items;
• declining engagement by preference group;
• broken images and links; and
• feeds or categories that have stopped publishing.

Assign someone to review the workflow after website migrations, permalink changes, CMS upgrades and email-template changes. These events can alter feeds without an obvious error on the website itself.

Multi-feed automation checklist

Before launch, confirm that you have:

• inventoried and validated every feed;
• assigned a clear audience to each source;
• set per-feed and total item limits;
• defined duplicate handling;
• documented new-item and no-content behaviour;
• tested missing images and unavailable feeds;
• tested several subscriber preference combinations;
• provided a way to update preferences; and
• assigned an owner for ongoing monitoring.

Put the plan into practice

If every subscriber needs the same combination, a well-maintained merged feed may be sufficient. If people need different content from the same automated campaign, FlipRSS can match several feeds to subscriber preferences and deliver the result through Mailchimp.

If you are still choosing between a merged feed, separate campaigns and subscriber-level matching, use the RSS feed aggregator comparison.

Continue with the Mailchimp multi-feed setup guide, explore the FlipRSS Mailchimp integration or start a 30-day free trial.