Features Pricing Docs Download
Support
Log in Sign up

Refreshing stale posts (Free; 3 credits a refresh)

What it does: Finds posts older than 12 months, builds freshness signals (dates, statistics, year references) and proposes a rewrite of the post, with a cooldown (a setting of the Pro add-on, 30 days by default) so the same post is not rewritten every month. How to access: Draft Forge > Topics > Scan stale posts, then Refresh now on a row (the proposed rewrite waits in Draft Forge > Queue), or wp draftforge refresh [--apply]. Free/PRO: Refreshing by hand is Free. Refreshing on a schedule is Pro. Notes:
  • A rewrite replaces a whole live article, so since 1.2.0 it is not applied unread (the one exception is hands-off publishing in the Pro add-on, which applies a rewrite that passes the gate): Review changes puts the proposed text beside the original, block by block and word by word, with a Words / Links / Images / Headings / Blocks strip for what prose cannot show. Accept publishes the text you read; Reject discards the rewrite and writes nothing at all to the post.
  • The body the model was handed is stored beside the proposal, so the comparison is against what the model actually saw. If somebody edited the post in between, the screen says so before you accept.
  • The lint’s findings for the proposed rewrite are shown on that same screen. Until 1.3.0 the person who had come there to read the rewrite carefully was the only one who could not see why the gate had held it.
  • Accepting part of a rewrite and leaving the rest is deliberately not offered: it would need a way to identify one block across two versions of a post, which the comparison does not carry. Accept and reject are whole-document.
Forge AI Assistant Online

Hi! I'm the Draft Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs