You run a site that publishes coffee content. Every week you import the supplier announcements, roaster guides and partner updates you’re cleared to republish, and until now you’ve shown a snippet of each one and sent the reader off to the original for the rest. Last week that changed. The same imports now arrive as full posts written in your own voice, with your own headlines, and you didn’t write a word of them by hand. Your reader gets the whole story from you, in language that sounds like your site.
That’s what an AI content rewriter does once it lives inside the place you already publish. WP RSS Aggregator pulls from the sources you’re cleared to use, and AI Rewriting turns each import into an original post in your site’s voice. If you’ve ever pasted an article into a separate rewriting tool and copied the result back out by hand, this is that job done where your content already flows, on every item you bring in. It arrived in Aggregator v5.2.0 on the Elite plan, and it’s the biggest change to what the plugin can do since full-text import.
Does Aggregator rewrite content with AI?
Yes. On the Elite plan, you point Aggregator at a source you’re allowed to republish, switch on AI Rewriting, and every item comes through rewritten into a new post in your own voice. It rewrites the title, the body and the excerpt, and it keeps the source’s language, so a feed you bring in in Spanish stays in Spanish. The original article stays untouched where it came from. What lands on your site is fresh writing in the voice you set, ready for you to review and publish as your own.
It runs on AI credits that come with your plan, so there’s no separate AI account to open and no API key to paste in anywhere. The writing happens inside Aggregator, in the same import you already use to bring feeds into WordPress.
Why publish a full post instead of a snippet?
Because a full post in your voice is a better experience for your reader than a teaser. The old way of curating, showing a snippet and linking out, gives them a taste and then sends them elsewhere to finish. A rewritten post gives them the whole thing on your site, in language that sounds like you, so the piece reads as part of your publication rather than a quote from somewhere else. That only holds when the source is yours to use, which is the next thing to get right.
It also gives you back the hours that curation usually eats. Finding good source material is the slow part of running a content site, and most people who do it well still end up rewriting by hand to make it sound like them. Aggregator does the rewriting for you on every item it imports, so the steady stream of posts you’d normally grind out becomes something closer to editing than writing.
You spend your time on the judgement calls, not the keyboard.
What you need before you rewrite a feed
One thing matters before any of this: the source has to be yours to use. There’s more of that around than people assume, and it’s worth being clear about where the line sits.
Rewrite sources you have the right to republish and adapt: your own posts from another site you run, content you license or syndicate, announcements from partners and suppliers who want the coverage, or updates from your own organisation.
If you have that right, you’re on solid ground turning a source into a post of your own. If you don’t, this isn’t the tool for it, and no rewrite changes that. It’s a way to do faster what you were already free to do, not a way to reuse work that isn’t yours.
That’s also who it’s built for. A content marketer or agency keeping several sites fed. Someone who runs a tutorials site and a product blog, importing the tutorials that fit the product’s audience and having them rewritten automatically in the product’s brand voice. An organisation pulling updates from its own field and reworking them into a tone its members actually understand. In each case the source is theirs to use, and the rewrite turns it into a post that reads like them.
How to rewrite imported articles in WordPress
Setting it up on a source takes about a minute:
- Open the source you’re importing from, go to its Advanced settings, and find the AI section. On the Elite plan, AI Rewriting sits in its own tab there.
- Set the intensity, which controls how far the rewrite moves from the source, and the tone, which sets the voice it writes in. Set them once and every item that imports follows the same direction.
- Run a Test Rewrite on a real item to see the original and the rewritten version side by side, and adjust until it sounds like you.
- Let the source import. Set it to import as a draft, so each rewrite lands in your editor for a quick check before it goes live.
That Test Rewrite step is the one that saves the most time. Instead of rewriting a piece by hand just to find out whether the voice is right, you read the result in seconds and adjust until it sounds like you.
AI Rewriting works on sources that bring items in as posts, the same Feed to Post import that powers most of what people do with Aggregator. If you can already turn a feed into WordPress posts, you’re set up for this.
When to use Rewriting, Summaries, or TL;DR
Rewriting is one of three AI tools in Aggregator, and they answer different needs. Summaries and TL;DRs add a layer to an imported post without replacing it, which is what you want when you’re pointing readers toward the full source. Rewriting replaces the writing entirely with a fresh version in your own voice, which is what you want when the post should read as yours. They share the same credit pool, so you can run whichever fits each source.
| What you want | Reach for | What lands on the post |
|---|---|---|
| A one-line gist at the top of an imported article | AI TL;DR | A short bullet summary, source intact |
| A short paragraph that frames the article for your reader | AI Summaries | A paragraph summary, source intact |
| An original post in your own voice, from a source you’re cleared to use | AI Rewriting | A new title, body and excerpt, fully rewritten |
Summaries and TL;DRs are available on Pro and Elite. Rewriting is the Elite tool, because it’s the one that gives you a finished post in your own voice rather than a layer on top of the imported article. You can see what each plan includes on the pricing page.
Should you publish AI rewrites automatically?
Keep yourself in the loop, especially while you’re dialling in a new source.
Import as draft. Every rewrite lands in your editor instead of going live, so you can check the rights and the facts, make the call, and publish when it’s right. The tool does the heavy lifting of turning a source into a finished draft in your voice; you add the human touch where it matters. That review step is what keeps a rewrite honest, so it’s worth keeping even once you trust how a source comes out.
That review is also where you catch the things any AI gets wrong. A rewrite can drift on a detail or miss the point of a quote, and a quick read before publishing keeps your site accurate and yours. It’s the difference between a tool that writes for you and a tool that writes instead of you, and the first one is the one you want.
Where this fits in your content workflow
If you already curate, this slots into what you do. You’re choosing sources and bringing them into WordPress, and now the writing step you used to do by hand, or skip by linking out, happens on the way in. It pairs naturally with the rest of the content curation workflow, and if you’ve been repurposing content from your feeds with summaries, rewriting is the step that turns a curated import into a post that reads like you wrote it.
And it’s just the start of where Aggregator is going. The plugin still does the one thing it’s always done, getting content from anywhere into WordPress, and that isn’t changing. AI Rewriting builds on top of it, turning the sources you’re cleared to use into posts that sound like your publication. Pick one source you have the rights to, run a Test Rewrite, and see how it reads in your voice.
