FeedWeaver – RSS, Atom, JSON Feed & XML Builder

By Streetcar Productions

0+ active installationsVersion 1.1.0

Build RSS, Atom, JSON Feed, XML, Media RSS and CSV feeds from your WordPress content, with full text, templates and optional token protection.

Description

Many services (news aggregators, partner platforms, mobile apps, internal tools) read a “feed”: a web address that returns your latest content in a fixed structure. WordPress has a built-in RSS feed, but its structure is fixed. FeedWeaver lets you decide which fields are included, what each one is called and how the document is organized, then gives you a permanent address for the result.

What you can do

  • Create any number of feeds, each with its own address of the form /feedweaver/your-feed-name/.
  • Choose one or more public content types and narrow a feed by category, tag or other taxonomy terms, authors, terms to leave out, featured image, a custom field value, or how old an item is. Sort by date, title, menu order, comments or a custom field.
  • Map WordPress fields (title, permalink, excerpt, the full article as cleaned HTML or plain text, dates, authors, featured image and its alt text, caption and credit, images and video in the article, categories, custom fields, taxonomy terms) to the names and nesting you need, such as media/thumbnail.
  • Build values from text and fields with templates, for example {{ title | truncate:60 }} or {{ permalink | utm:"utm_source=newsletter" }}, and skip items that have no value for a field.
  • Output RSS 2.0, Atom 1.0, JSON Feed 1.1, Media RSS, custom XML, JSON or CSV/TSV.
  • For XML and RSS, declare namespaces (such as Dublin Core or Media RSS), set attributes on elements, repeat elements for lists, and control the order of elements.
  • Include the whole article: HTML is cleaned (scripts, styles, frames, forms and event handlers are removed, links and images get full web addresses, lazy-loaded images are repaired) and written as content:encoded in RSS, content in Atom and content_html in JSON Feed.
  • Serve long feeds in pages (up to 500 items per page) with next and previous links.
  • Exclude any post from all feeds, or give it its own feed headline and description, from a box on its edit screen.
  • Preview the exact output in the editor before publishing. The preview explains if any items were left out or adjusted.
  • Keep a feed public, or protect it with a secret token sent in the URL or as a Bearer header (or in the header only, which lets the feed state its own address). Only a one-way fingerprint of the token is stored, and the token is shown once when you create it.
  • Developers can add their own formats, template filters, checks and recipes through documented registries and hooks.

Safe by design

  • Only published, public, non-password-protected content is ever included, whether or not a feed is protected.
  • Custom fields whose names start with an underscore, or look like passwords, keys or tokens, cannot be mapped.
  • Article HTML goes through an allow-list sanitiser. Templates read fields and run filters; they cannot run code. CSV output neutralises spreadsheet formulas.
  • Output is checked before it is sent: invalid XML, Atom or JSON Feed is never published.
  • FeedWeaver makes no requests to outside services and does not collect or send any data.

Good to know before you install

  • A feed returns at most 500 items per request, newest first by default. Turn on paging to serve more.
  • RSS enclosure sizes are read from files in your own uploads folder. If media is stored elsewhere, keep the size in a custom field.
  • Protected feeds state their own address (atom:link rel="self") only when they accept the token in a header only (see the FAQ).
  • The feed is generated by WordPress, so a caching layer outside WordPress that ignores cache headers can still affect it. FeedWeaver reuses a built feed for five minutes by default and rebuilds it sooner when content of a type the feed uses changes. See the Help page in the plugin for details.

FeedWeaver includes a Help page (FeedWeaver > Help & Documentation) with step-by-step guidance, examples and troubleshooting.

Installation

  1. In your WordPress admin, go to Plugins > Add New, search for FeedWeaver and click Install Now, then Activate. Alternatively, upload the plugin folder to /wp-content/plugins/ and activate it from the Plugins screen.
  2. Go to FeedWeaver > Add New.
  3. Name the feed, choose the content to include, choose the output format (RSS 2.0, Atom, JSON Feed, Media RSS, custom XML, JSON or CSV), and map the fields you want.
  4. Click Preview output to check the result.
  5. Tick Enabled and click Save. A new feed is switched off until you do, and its address shows a “not found” page. The feed’s address then appears at the top of the editor, with a Copy button, and in the feeds list.

FAQ

Where is my feed?

At https://your-site.example/feedweaver/your-feed-name/. The editor shows the exact address with Copy and Open buttons, and the feeds list shows it with a Copy button. If your site uses Plain permalinks, the address looks like https://your-site.example/?feedweaver_feed=your-feed-name instead.

My new feed shows “not found”.

A new feed is switched off until you tick Enabled under Preview & Publish and save. Also check that the address is exactly the one shown in the editor.

Does FeedWeaver replace my site’s normal RSS feed?

No. The built-in WordPress feeds are left alone. FeedWeaver feeds are separate addresses.

Can I make a feed private?

Yes. Under Access Control choose Protected and generate a token. Readers must send it either as ?access_key=TOKEN on the address or as an Authorization: Bearer TOKEN header. The token is shown once; if you lose it, generate a new one, which immediately stops the old one working. A feed has one token at a time.

Is a token in the URL safe?

It is less private than a header, because web addresses are often written to server logs and browser history. Use the Bearer header when the receiving service allows it. Protected feeds also require HTTPS, except on a local development site, because a token sent over plain HTTP can be read on the network.

Does a token change what is in the feed?

No. It only controls who can read the feed. Drafts, private, scheduled and password-protected content is left out for everyone.

Why do protected RSS feeds have no atom:link self element?

The self link is the address a feed reader may use to replace the address it was given. If a protected feed accepted its token in the address, publishing that address would publish the key, and leaving the key out would break the subscription. Tick “Accept the token only in the Authorization header” and the address carries no secret, so the element is written.

Why is an item missing from my RSS feed?

An RSS item must have a title or a description. Items with neither are left out, and values that are not valid (a link that is not a full http or https address, an invalid date or an empty GUID) are removed from the item. The editor’s preview lists what was left out or adjusted, by post ID.

What is the RSS GUID?

By default it is the post’s WordPress GUID, a unique identifier WordPress assigns when the post is created. It does not change when the post is edited or its address changes, which keeps feed readers from showing old items as new. You can map the permalink or another field to the guid instead.

Can I use custom fields, including those from ACF?

Yes. Fields saved as ordinary custom fields can be mapped by their key. FeedWeaver lists fields found on recent posts and lets you type a key for others. It does not know a field’s type or read field-group labels, so values are used as saved.

Can a feed include HTML or the full post content?

Yes. Map “Full Content (HTML)” to content:encoded (RSS), content (Atom) or content_html (JSON Feed). The HTML is cleaned first, and you choose how strict the cleaning is and whether shortcodes are removed or run. “Full Content (plain text)” gives the article without markup.

Which formats are supported?

RSS 2.0, Atom 1.0, JSON Feed 1.1, Media RSS, custom XML, JSON and CSV/TSV.

Can a feed have more than a few items?

Yes. A feed returns up to 500 items per request. Tick “Split the feed into pages” and readers can ask for ?fw_page=2 and so on; RSS, Atom and JSON Feed list the next and previous pages in the document.

Can I keep one post out of every feed?

Yes. Every post has a FeedWeaver box with “Exclude from all feeds”. The same box lets you write a different headline and description just for feeds.

Does it work on multisite?

Each site has its own feeds. The plugin’s automated tests also run in WordPress multisite mode, and its uninstall routine cleans every site on a network.

Does it add anything to my front end or slow my site down?

It adds no front-end scripts or styles. The admin scripts load only on FeedWeaver screens. Feeds are generated on request and cached for five minutes.

What happens to my data if I uninstall it?

Deleting the plugin from the Plugins screen removes every feed, its settings, the token fingerprints and FeedWeaver’s cached data. Deactivating keeps everything.

Does FeedWeaver contact other services?

No. It does not make requests to other sites, and it does not look up file sizes or video details on the web: it only reads what is stored in WordPress.

Screenshots

Changelog

1.1.0

  • New formats: Atom 1.0, JSON Feed 1.1, Media RSS and CSV/TSV.
  • Full article text as cleaned HTML (content:encoded, Atom content, JSON Feed content_html) or plain text; excerpt length, source and custom field options.
  • Templates with filters (truncate, date, UTM parameters, duration, replace, default and more) and “skip the item if empty”.
  • A FeedWeaver box on each post: exclude from all feeds, feed headline, feed description.
  • Sorting, author, term, featured image, sticky and custom field filters, hold-back and age windows, duplicate removal.
  • Up to 500 items per request, with optional paging and next/previous links.
  • New fields: featured image alt text, caption and credit, images in the article, video address, all authors (Co-Authors Plus aware).
  • Conditional requests with Last-Modified, feeds refresh when content of a type they use changes, a per-feed cache time, and a random feed address button.
  • Protected feeds can accept the token only in a header, which lets them state their own address.
  • Extension registries and hooks for developers.
  • Existing feeds keep producing exactly the same output.

1.0.0

  • First public release.
  • Custom XML, JSON and RSS 2.0 feeds with visual field mapping.
  • Multiple content types and taxonomy filtering, custom field mapping, advanced XML (namespaces, attributes, repeated elements, ordering).
  • RSS: stable default GUID from the WordPress GUID, RFC 822 dates, enclosures, and an atom:link rel="self" element on public feeds.
  • Public or token-protected feeds, with a one-time token display, URL key and Bearer header support, and token replacement.
  • Feed addresses can be copied and opened from the feeds list and the editor.
  • Validation errors name the field, highlight it and move focus to it.
  • The preview explains which items were left out or adjusted.
  • Uninstall removes all plugin data, on single sites and on multisite networks.