Caching & Optimization Plugins

Full-page caching plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache, and similar) save finished HTML and serve it to visitors. That’s great for speed, but it can serve a copy that was cached before your translations existed — so visitors see old or untranslated pages.

Clear the cache after translating

After a translation run, or after editing in the Visual Editor, clear your caching plugin’s cache. Then hard-reload (Cmd/Ctrl + Shift + R) to bypass your browser cache. This resolves most cases.

Stale translations after an edit

When you change the original text, the translation updates (automatically with Auto Translate, or when you re-translate the page). If visitors still see the old version, your page cache is serving a pre-edit copy — clear it.

Make caching language-aware

If translated URLs keep serving the wrong language, configure your caching plugin to either:

• Exclude language-prefixed URLs from the cache (for example, don’t cache /fr/*), or
• Segment the cache by language, so each language gets its own cached version.

The exact setting name varies by plugin — check its documentation, or ask support.

Dynamic content

Translations for dynamic content (cart updates, mini-cart, AJAX) are delivered through a separate JavaScript file, which caching and optimization plugins can also cache or minify. If dynamic bits lag behind, clear the cache so the latest translation data is served.

Tip

To confirm caching is the culprit, temporarily deactivate the caching plugin and reload the page. If translations appear, the fix is in the cache configuration above.