The Challenge
Rewriting content on a WordPress site normally means leaving WordPress. Copy the post out, paste it into a chat window, write the same instruction for the hundredth time, paste the result back, fix the formatting. It works, and it falls apart the moment there is more than a handful of posts to get through.
The existing plugins that solve this mostly solve something else. They generate new articles, or they sit inside a page builder, or they lock rewriting to blog posts only. A site running products, listings, portfolio entries or any other custom post type is left doing it by hand, which is exactly the situation on most of the sites we build.
This one was built for our own use first, on the automated publishing projects where rewriting is the step that decides whether the content is worth anything.
What We Built
A WordPress plugin that rewrites content in place, with its own dashboard inside the admin rather than a settings tab buried under another plugin. The rewriting runs through the OpenAI API, and the site owner supplies their own key, so usage is billed at cost with no subscription sitting between the site and the model.
It works on any post type. Posts, pages, products, custom types registered by a theme or by ACF, all of it. That was the main decision behind the build. Most content that actually needs rewriting on a real site is not a blog post, and a tool that only handles blog posts is useless on two thirds of the projects we work on.
Instructions are written by the user rather than chosen from presets. Whatever the rewrite needs to do, tighten a supplier description, change tone, strip promotional language, rework a feed article into the site’s own voice, is expressed in plain instruction in the dashboard. Presets are faster to build and they only ever fit the site they were designed for.
Keeping it inside WordPress rather than running it as an external service was deliberate. The content never leaves the site, there is no sync step to break, no second platform to log into, and it works the same way whether someone is editing one post or working through an archive.
Why We Built It
Several of the automated publishing systems we run depend on rewriting quality. A feed pipeline without a good rewrite step produces duplicate content that does not rank, and the difference between a content site that works and one that never gets indexed often comes down to that single stage.
Building the tool rather than renting one meant the rewriting could be tuned to what those projects actually needed, and it now runs on our own sites as well as on client builds.
