Search Atlas Help Center

🔄 OTTO Deployment Changes Blocked by Cache Plugins

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧩 Why Your OTTO Changes May Not Be Showing

After deploying changes through OTTO (found in the left sidebar under OTTO SEO → All Sites (SEO Automation)), you may notice that updates do not appear on your live website — even after waiting 24–48 hours. In most cases, the culprit is not OTTO itself but a cache plugin installed on your WordPress site. Cache plugins store a static snapshot of your pages to speed up load times. When OTTO pushes changes to your site, the cache plugin can serve the old cached version to visitors instead of the updated content.

This issue has been confirmed with Airlift and can also occur with other popular cache plugins, including WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and Cloudflare's caching layer.

🔍 How to Confirm Cache Is the Problem

Before clearing your cache, verify that cache interference is the actual cause:

  1. Open your website in a private or incognito browser window.
  2. Check whether the OTTO-deployed changes (meta titles, descriptions, schema, headings, or other on-page updates) are visible.
  3. If the changes still do not appear, log in to your WordPress admin dashboard and check whether a cache plugin is active under Plugins → Installed Plugins.
  4. If a cache plugin is listed and active, proceed with the steps below to clear it.

🛠️ How to Fix It — Airlift Cache

If you are using the Airlift plugin, follow these steps:

  1. Log in to your WordPress admin dashboard.
  2. In the left sidebar, click Airlift.
  3. Navigate to the Cache tab or section.
  4. Click Purge All Cache (the exact button label may vary slightly by version).
  5. Wait 1–2 minutes, then reload your website in a private browser window to confirm the OTTO changes are now visible.

🛠️ How to Fix It — Other Common Cache Plugins

The process is similar for other cache plugins. Use the guide below for your specific plugin:

  • WP Rocket: Go to Settings → WP Rocket and click Clear Cache in the dashboard panel.
  • W3 Total Cache: Click Performance in the WordPress sidebar, then select Purge All Caches.
  • WP Super Cache: Go to Settings → WP Super Cache and click Delete Cache.
  • LiteSpeed Cache: Click the LiteSpeed Cache icon in the WordPress admin toolbar and select Purge All.
  • Cloudflare: Log in to your Cloudflare dashboard, go to Caching → Configuration, and click Purge Everything. Note that this clears the CDN cache, not the WordPress cache — you may need to do both.

✅ After Clearing the Cache

Once you have purged your cache, take these steps to confirm everything is working correctly:

  1. Open your website in a private or incognito browser window (this prevents your own browser cache from interfering).
  2. Navigate to the specific pages where OTTO deployed changes.
  3. Verify that the updates — such as revised meta titles, descriptions, or structured data — are now reflected on the live page.
  4. If you use a CDN (such as Cloudflare, BunnyCDN, or KeyCDN), purge the CDN cache as well, since CDN-level caching can cause the same issue independently of your WordPress cache plugin.

🚫 How to Prevent This in the Future

To avoid deployment visibility delays after future OTTO sessions, consider building cache purging into your standard workflow:

  • Purge your cache immediately after every OTTO deployment before checking whether changes appear on the live site.
  • If your cache plugin supports it, configure automatic cache expiration so cached pages refresh after a set interval (for example, every 12–24 hours).
  • Some cache plugins offer selective purging — you can purge only the URLs that OTTO modified rather than clearing your entire cache, which reduces the performance impact.
  • If you use Cloudflare with the Automatic Platform Optimization (APO) feature enabled, remember that APO caches pages aggressively and must be purged separately after any on-page changes.

💬 Still Not Seeing Your Changes?

If you have cleared both your WordPress cache and your CDN cache and the OTTO-deployed changes are still not visible after 30 minutes, there may be a secondary issue such as a server-level cache, a reverse proxy, or a conflict with another plugin. 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.