🔍 What This Error Means

When OTTO's diagnostics display a "WordPress plugin is currently disabled" warning, it does not always mean the plugin is actually deactivated inside WordPress. In most cases, the plugin is active — but a cached response is preventing OTTO from reading its current status correctly.

This mismatch happens because WordPress and hosting providers aggressively cache API responses. OTTO checks a specific endpoint to confirm the plugin is running, and if that endpoint returns a stale or empty cached response, OTTO flags the plugin as disabled even though it is working fine.

⚙️ Step 1 — Confirm the Plugin Is Active in WordPress

1. Log in to your WordPress admin dashboard.
2. Navigate to Plugins → Installed Plugins.
3. Locate the Search Atlas plugin.
4. Confirm the plugin status shows Active. If it is deactivated, click Activate before continuing.

🗑️ Step 2 — Clear All Caches on Your Site

This is the most important step. You need to clear every layer of caching that could be serving a stale response to OTTO.

• WordPress caching plugin — If you use WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, or a similar plugin, open its settings and click Clear All Cache or Purge Everything.
• Hosting-level cache — Log in to your hosting control panel (e.g., Kinsta, WP Engine, SiteGround, Cloudways) and purge the server cache from your hosting dashboard.
• Cloudflare or CDN cache — If your site runs behind Cloudflare or another CDN, log in and click Purge Everything under the Caching settings.
• Object cache — If your site uses Redis or Memcached, flush the object cache from your hosting dashboard or via your cache plugin's settings.

🔄 Step 3 — Re-run the OTTO Diagnostic Check

1. In Search Atlas, go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3).
2. Open the OTTO panel for your site.
3. Locate the WordPress Plugin status card in the diagnostics section.
4. Click Refresh or re-run the site check to let OTTO re-read the plugin status.
5. The status should now show as Active or Connected.

💡 Why This Happens and How to Prevent It

OTTO communicates with your WordPress site through a REST API endpoint that the Search Atlas plugin registers. If a caching layer returns an old response — or blocks the endpoint entirely — OTTO receives no valid signal and defaults to reporting the plugin as disabled.

• Exclude the plugin's REST API endpoint from caching — In your caching plugin settings, add an exclusion rule for URLs containing /wp-json/search-atlas/. This prevents future caching conflicts.
• Check for security plugins blocking REST API access — Plugins like Wordfence, iThemes Security, or All In One WP Security can restrict REST API access. Ensure the Search Atlas endpoint is whitelisted.
• Avoid full page caching on admin-ajax requests — Confirm your caching rules are not caching authenticated or admin-level requests.

🚨 Still Showing as Disabled After Clearing Cache?

If the diagnostic still shows the plugin as disabled after completing all the steps above, try the following:

1. Deactivate the Search Atlas plugin in WordPress, wait 30 seconds, then reactivate it.
2. Clear all caches again following Step 2.
3. Re-run the OTTO diagnostic check following Step 3.

If the problem persists after these steps, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.