Skip to content
SeoFreshUp Docs

Compatibility issues

SeoFreshUp is built to be plugin-friendly, but some conflicts arise. Here’s how to diagnose and fix them.

SEO plugin conflicts

SeoFreshUp auto-detects active SEO plugins (Yoast, Rank Math, SEOPress) and writes the rewritten meta description into the right field. If you have multiple SEO plugins active simultaneously (anti-pattern), SeoFreshUp picks the first one detected, which may not be the one you actually use.

Fix

Deactivate all but one SEO plugin. Multiple SEO plugins also create duplicate meta tags in <head>, which is a real SEO problem regardless of SeoFreshUp.

Cache plugin conflicts

WP Rocket, W3 Total Cache, LiteSpeed Cache, etc. cache the admin area sometimes. If the audit table doesn’t refresh after an analysis:

Fix

  1. Add the SeoFreshUp admin URL to the exclude from cache list:
    • Pattern: /wp-admin/admin.php?page=wp-seo-pruner*
  2. Or temporarily disable caching for admin requests

REST API plugin conflicts

If a plugin like Disable REST API blocks /wp-json/, SeoFreshUp’s AJAX endpoints fail.

Fix

Whitelist wp-admin/admin-ajax.php (which is what the plugin uses, not REST). Most “Disable REST API” plugins only affect /wp-json/, but some over-eager security plugins block both. Check iThemes Security, WP Cerber, All In One WP Security for any “block AJAX” rules.

Memory limit errors

Allowed memory size of 134217728 bytes exhausted

Means: PHP ran out of RAM during the audit (typical at 50+ articles with big content).

Fix

In wp-config.php:

define('WP_MEMORY_LIMIT', '512M');
define('WP_MAX_MEMORY_LIMIT', '512M');

Or in php.ini:

memory_limit = 512M

For very large blogs (5000+ articles), bump to 1024M.

max_execution_time errors

Maximum execution time of 30 seconds exceeded

The plugin already calls set_time_limit(0) to bypass this, but some hosts (php-fpm safe mode) ignore it.

Fix

Ask your host to increase max_execution_time to at least 120s. Or use WP-CLI for long jobs (see below).

WP-CLI fallback for huge blogs

For blogs with 5000+ articles where browser-based audit times out:

Terminal window
# Run a full audit via WP-CLI (no browser timeout)
wp seofreshup audit --all

(Note: WP-CLI command is on the roadmap, not yet shipped at v3.0)

Theme conflicts

The plugin only adds an admin menu — no public-facing changes. Theme conflicts are rare. If you see broken admin styling:

Fix

  1. Switch temporarily to a default theme (Twenty Twenty-Four)
  2. If the issue disappears, your theme is overriding admin CSS — contact the theme author

Multisite (Network)

Currently not officially supported. The plugin works on a single site of a network but won’t network-activate. License model is also per-domain, so each site of the network needs its own license.

Multisite support is on the roadmap — email if you have a use case.

Custom post types

The plugin only audits post_type = 'post'. Custom post types (products, pages, courses) are out of scope. The plugin is content-pruning-focused for blog articles specifically.

If you want to audit pages or products, this is on the roadmap behind multisite support.

Object cache (Redis, Memcached)

The plugin uses standard wp_options, wp_postmeta and transients — fully compatible with object caches. No special config needed.

CDN considerations

If you serve wp-admin/ through a CDN (rare but possible), AJAX endpoints might cache. Don’t CDN the admin — it should always be direct-to-origin.

What’s next?