Scan
It reads what you have published and records the state of each page, rather than guessing from titles.
WPCWP20 — until 31 October 2026
Home / Content refresh for WordPress
Scan, rank, propose, approve, undo. The archive you have already built is usually worth more than the next article, and it is the part most tools ignore.
It reads what you have published and records the state of each page, rather than guessing from titles.
Pages are ordered by where an update is most likely to matter, using the search data you have imported.
You get a list of what it would change on which pages, with the reasoning, and nothing has happened yet.
You choose. Only then does any work queue, and it runs in the background rather than tying up a page load.
Before a post is touched, its state is recorded against the run. If the snapshot cannot be taken, the edit does not happen.
The refresh path does not write a post's status in either direction. A draft cannot be pushed live and a live article cannot be taken down.
One post, a ticked selection, or everything. A selection is checked against what that run actually touched.
Existing content stays published and exports keep working. Only the making of new work stops.
It scans what you have published, ranks it against the search data you have imported, and proposes the pages where an update is most likely to matter. You see the ranking and the reasoning before anything runs.
SEO metadata, schema, FAQ blocks, the featured image, and the body text through a humanising pass. It never changes a post's status, so it cannot publish a draft or take a live article down.
Undo it. The previous version of each post is saved before it is touched, and you can restore one post, a selection, or the whole run. Restoring is itself reversible, so both versions stay in the history.
No. There is no path in the plugin that deletes a post, a page, an image or a topic.
Every change is recorded against a run, and every run can be put back.