How revisions help editors, when they become a maintenance concern and how to set sensible limits.
Why this check matters
Revisions provide a valuable recovery history, but a busy site can accumulate many rows. The right answer is usually a retention policy rather than disabling revisions completely.
How to review it
- Measure revision volume and identify the post types creating it.
- Keep enough history for the editorial workflow.
- Prune old revisions with a tested maintenance tool if needed.
- Back up before database cleanup and verify restore options.
Keep the change safe
Do not remove revisions while an editor is relying on them for recovery. Agree on retention before deleting history.
How WPVitals uses this signal
WPVitals checks this setting locally and reports the result in the WordPress dashboard. The check is a maintenance signal, so review the site context before changing a setting and test the visitor experience afterwards.