How to Fix: Revisions limited

Revisions limited is an important SEO check in the WordPress Specific category. This is a medium-priority issue. While not urgent, fixing it will improve your overall SEO health.

What is This Check About?

This check verifies that WordPress is capping the number of post revisions it keeps, rather than storing an unbounded history for every post and page. By default WordPress saves a new revision every time you update content, plus periodic autosaves, and it keeps all of them forever. On a site that has been publishing for a few years, that means your database is quietly carrying dozens of copies of every article you have ever touched. When this check fails, it means no limit is set and that back-catalogue of old drafts is accumulating without a ceiling.

Let me be straight about the SEO framing, because I would rather you understand the real mechanism than accept a hand-wave. Revisions are not an SEO factor in the sense that Google reads them — it does not, they are never public. This matters for SEO one step removed: an over-stuffed wp_posts table makes queries slower, backups heavier, and the whole site more sluggish, and site speed is a ranking and user-experience factor. So this is a database-hygiene fix wearing an SEO badge. It is worth doing anyway.

Why Does This Matter for SEO?

Search engines like Google evaluate hundreds of factors when ranking websites. Revisions limited is one of these important factors because:

• It affects how search engines crawl and understand your content
• It impacts user experience, which is a key ranking factor
• It can influence your site’s visibility in search results
• Ignoring it may cause your competitors to outrank you

The chain of cause and effect is worth spelling out. Every revision is a full row in wp_posts holding a complete copy of the post content. A prolific editorial site can easily carry ten to fifty revisions per article, which means the table WordPress hits on nearly every query is several times larger than the content you actually publish. Larger table, slower queries, slower page generation, and heavier, longer backups that are more likely to time out. None of that is catastrophic on its own, but it is pure dead weight, and dead weight in the one table that touches everything is exactly the kind of thing you clear out before it becomes a problem you notice.

How to Check This Issue

You can identify this issue by:

1. Running an SEO audit using the SEO Roadmap tool
2. Manually inspecting your website’s source code and settings
3. Using browser developer tools (F12) to analyze page elements
4. Checking Google Search Console for related warnings or errors

The direct check is to look at wp-config.php for a WP_POST_REVISIONS line. If it is absent, you have no limit. To see how much this is actually costing you, count them — in wp-cli, wp post list --post_type=revision --format=count tells you exactly how many revision rows are sitting in your database right now. On sites I inherit, that number is routinely in the tens of thousands, and it always surprises the owner.

How to Fix This in WordPress

Difficulty Level: EASY – This fix is straightforward and can typically be completed by anyone with basic WordPress knowledge.

Estimated Time: 5 min

Follow these steps to fix this issue:

Step 1: Identify Affected Pages

First, run a complete SEO audit to identify all pages affected by this issue. The SEO Roadmap tool will show you exactly which URLs need attention. This one is site-wide rather than per-page — the setting governs every post type at once — so the real inventory is “how many old revisions do I already have,” which the count command above answers.

Step 2: Access WordPress Settings

Log into your WordPress admin dashboard. Depending on the specific issue, you may need to navigate to:

• Settings → General for site-wide configurations
• Settings → Reading for indexing and visibility settings
• Settings → Permalinks for URL structure issues
• Appearance → Theme Editor for template-level fixes
• Plugins → Installed Plugins to configure SEO plugins

This particular fix is not in the admin UI — it lives in wp-config.php. You will edit that file over SFTP or your host’s file manager. Take a backup of it first; it is the one file that can take a site fully offline if you fat-finger it.

Step 3: Apply the Fix

Make the necessary changes based on the specific issue. If you’re using an SEO plugin like Yoast SEO or Rank Math, many of these settings can be configured through the plugin’s interface. For revisions specifically, add one line to wp-config.php, above the “That’s all, stop editing” comment:

define( 'WP_POST_REVISIONS', 5 );

That caps every post at its five most recent revisions and silently drops older ones going forward. If you prefer a no-code route, cleanup plugins like WP-Optimize can both set the cap and purge the existing backlog in one pass. Whichever you choose, purge the old revisions once after setting the limit — the cap only governs new saves, so the historical pile stays until you clear it.

Step 4: Verify the Fix

After making changes:

1. Clear your WordPress cache if you’re using a caching plugin
2. Re-run the SEO Roadmap audit to confirm the issue is resolved
3. Check Google Search Console after a few days to ensure Google has recognized the fix

The number I actually use, and why it is not zero

Here is where I part ways with the “smaller is always better” instinct. The temptation, once you learn revisions cost you, is to set the value to 0 or false and turn the whole system off. I would not. Revisions are your undo button. The day a writer overwrites two hours of work, or an auto-updating plugin mangles a page, or you simply need to see what a post said last Tuesday, that history is the thing that saves the afternoon. Disabling it to reclaim a few megabytes is trading a genuinely useful safety net for a rounding error of disk space.

My default on client sites is a cap somewhere between 5 and 10. That is enough depth to recover from any realistic editing accident and shallow enough that the table never balloons. I reserve the low end for high-volume publishers pushing hundreds of posts a month, and lean toward 10 for smaller sites where the storage never matters but the recovery might. One more setting worth knowing while you are in there: the AUTOSAVE_INTERVAL constant controls how often WordPress autosaves in the background, and widening it from the default 60 seconds is a gentler way to reduce revision churn on a busy site without giving up the history you actually want.

Recommended Tools & Plugins

These tools can help you fix and prevent this issue:

• Yoast SEO – Comprehensive SEO plugin with built-in checks
• Rank Math – Feature-rich SEO plugin with detailed analysis
• Google Search Console – Free tool to monitor your site’s search presence
• SEO Roadmap – Complete SEO audit and action plan tool

Common Mistakes to Avoid

• Making changes without testing in a staging environment first
• Ignoring the issue because it seems minor
• Applying fixes to production without proper backup
• Not verifying the fix was successful after implementation

The revision-specific trap: editing wp-config.php without a backup, or pasting the define() line below the “stop editing” comment where it will not take effect. And do not run a mass revision purge on a live production database at peak traffic without a fresh backup — deleting tens of thousands of rows locks the table briefly, and you want a restore point if anything hiccups mid-delete.

Need More Help?

If you’re still having trouble fixing this issue, consider:

• Consulting with a WordPress developer or SEO specialist
• Checking the WordPress support forums for similar issues
• Reviewing your theme and plugin documentation
• Running a complete site audit with SEO Roadmap for a prioritized action plan

This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.