Limit and prune post revisions with AI
Clear out thousands of old post revisions bloating your database, keeping the recent ones per post.
Prerequisites
A connected site and a recent database backup (pruning revisions is permanent). Capping future revisions is a one-line wp-config.php edit you make yourself.
Take stock of the post revisions on my site. First, count how many revisions exist in total and show me the posts holding the most, but do not delete anything yet. After I have looked, prune the old revisions while keeping the [3] most recent on every post, and never touch the published content itself, only the older saved copies. Ask for my approval before the deletion and tell me how many rows you removed. Finally, give me the exact single line to add to my wp-config.php to cap revisions at [5] going forward, and explain that I add that line myself.
Already connected to WPVibe?
Skip the copy-paste. Just ask your AI for the “Limit and prune post revisions with AI” recipe, or describe the task, and WPVibe runs these steps on your own site.
Every time you save a post, WordPress quietly stores a full copy of it as a revision. On a site that has been around a few years, that adds up to thousands of hidden rows padding your database, and by default WordPress keeps every one of them forever. You never see them in the admin, but they can leave your posts table several times larger than the content actually justifies, which slows backups and queries.
Ask your AI assistant and it counts how many revisions are stacked up across your site and which posts hold the most, then prunes the old ones while keeping the few most recent per post, so you never lose edit history you might genuinely want back. Each deletion runs through WPVibe’s approval step, so you see exactly how many rows are going before they go. Your published content is never touched, only the older saved copies behind it.
Take a backup first, since deleting revisions is permanent. Paste the prompt, review the count, and approve the prune. To stop the pile from rebuilding, cap revisions going forward by adding one line to your wp-config.php file (the assistant gives you the exact line). That single edit is a manual step you make yourself, because changing wp-config from the outside is intentionally locked down for security.
Outcome
Old post revisions cleared down to the few most recent per post, published content untouched, plus the exact wp-config line to cap revisions from here on.