How Feed Control Expands Partial or Truncated RSS Feeds into Full-Text Feeds

Feed Control turns a truncated feed into a full-text feed by fetching the article content behind each item and replacing the short summary with that content. You point it at an existing feed, it pulls in the full article for every item, and it outputs the result as RSS or JSON that you can read in a feed reader or consume in another application. This is the option to use when a publisher only exposes excerpts and you need the complete text; it is not needed for feeds that already carry full content.

What the expansion feature does

According to Feed Control's own description, the feature works like this:

• It takes a feed whose items are truncated (partial content only).
• For each item, it pulls in the article content from the source page.
• It produces a transformed feed where items carry the full article text.
• The output can be enabled as RSS or JSON, so the results can be consumed in your own applications.

The practical effect is that a feed reader subscribed to the expanded feed shows the whole article instead of a teaser, and downstream systems receive complete text rather than a fragment.

When to use it — and when not to

The last row matters: expansion depends on being able to retrieve the article content. If the full text is gated, there is nothing for the tool to pull in.

How to set it up

Feed Control's site describes the capability but does not publish a step-by-step walkthrough of the interface. The general sequence, based on what the product states it does, is:

1. Start with the truncated feed. Identify the feed URL whose items are partial. This is your input.
2. Create a feed in Feed Control based on that source. Feed Control monitors existing feeds as well as web pages and Google News, so an existing feed is a valid starting point.
3. Enable full-text expansion. Turn on the option that pulls article content in for each item. The expected result is that each item's content is replaced with the full article.
4. Choose your output format. Enable RSS if you want to read it in a feed reader; enable JSON if you are feeding another system.
5. Verify. Open the generated feed and compare an item against the original page. The item should now contain the article body rather than the truncated summary.

Verifying it worked

Check three things on the output feed:

• Item count matches the source feed — expansion should not drop items.
• Content length per item is substantially longer than the original summary.
• Format is what you selected (RSS or JSON) and parses cleanly in your reader or application.

Common sticking points

• Assuming every feed can be expanded. If the article body is not retrievable, expansion cannot produce full text.
• Forgetting the output format choice. Expansion alone does not decide whether you get RSS or JSON; you enable the format you need for your reader or app.
• Skipping verification. Compare at least one expanded item against the live page to confirm the full body, not just a longer excerpt, was captured.
• Overlooking republication terms. The tool can produce full-text output, but whether you may republish that content is a separate question governed by the publisher.

Related capabilities that pair with expansion

Feed Control's other features are relevant if expansion is part of a larger workflow:

• Filters can automatically exclude items containing specific words, phrases, or URL segments — useful for trimming an expanded feed before it reaches a reader or app.
• Alerts via email, Slack, or Discord notify you when new items appear; email summaries can be daily, weekly, or monthly.
• Webhooks deliver each new item with content in the original HTML, a stripped-down sanitized version, and plain text — handy when an application needs the expanded content pushed to it.
• Embedding lets you place feeds on a website using customizable widgets.

For help with custom feed creation or content syndication, the site directs users to get in touch.